ORA-15065: hash collision for diskgroup names 'string' and 'string'

Cause : There was a collision in the group name used for the diskgroup. The diskgroup(s) cannot be mounted using colliding names.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Use a different diskgroup name and also report to Oracle Support Services the two diskgroup names which collided.

update : 24-06-2017

ORA-15065 - hash collision for diskgroup names 'string' and 'string'
ORA-15065 - hash collision for diskgroup names 'string' and 'string'

  • ora-12079 : materialized view options require COMPATIBLE parameter to be string or greater
  • ora-12911 : permanent tablespace cannot be temporary tablespace
  • ora-12927 : RETENTION option already specified
  • ora-39775 : direct path API commit not allowed due to previous fatal error
  • ora-27037 : unable to obtain file status
  • ora-08311 : sllfop: bad value for maxrecsize
  • ora-32607 : invalid ITERATE value in MODEL clause
  • ora-29966 : The only binding of an operator cannot be dropped
  • ora-30040 : Undo tablespace is offline
  • ora-14032 : partition bound of partition number string is too high
  • ora-06102 : NETTCP: cannot allocate context area
  • ora-06252 : NETNTT: cannot open address file
  • ora-06029 : NETASY: port assignment failure
  • ora-34897 : (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES option.
  • ora-33262 : (DBERR01) Analytic workspace string does not exist.
  • ora-12842 : Cursor invalidated during parallel execution
  • ora-00721 : changes by release string cannot be used by release string
  • ora-07268 : szguns: getpwuid error.
  • ora-31423 : change table string does not contain column string
  • ora-38952 : Source database not compatible
  • ora-24023 : Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]
  • ora-19160 : XP0003 - syntax error: invalid variable name string
  • ora-06954 : Illegal file name
  • ora-22896 : cannot have both scope and referential constraint on REF column "string"
  • ora-09217 : sfsfs: failed to resize file
  • ora-15024 : discovered duplicately numbered ASM disk string
  • ora-28368 : cannot auto-create wallet
  • ora-29251 : Index1 is greater than Index2 in call to dbms_sql.bind_array
  • ora-00343 : too many errors, log member closed
  • ora-12097 : changes in the master tables during refresh, try refresh again
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.