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 : 30-04-2017
ORA-15065

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

  • ora-22868 : table with LOBs contains segments in different tablespaces
  • ora-00264 : no recovery required
  • ora-28275 : Multiple mappings for user nickname to LDAP distinguished name exist.
  • ora-33447 : (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.
  • ora-29312 : changes by release string cannot be used by release string, type: string
  • ora-30570 : SEGMENT SPACE MANAGEMENT option already specified
  • ora-16064 : remote archival is disabled by another instance
  • ora-16140 : standby online logs have not been recovered
  • ora-12489 : default label not within clearance range
  • ora-27039 : create file failed, file size limit reached
  • ora-27025 : skgfqsbi: invalid media manager context area size
  • ora-36174 : (XSMXAGGR23) workspace object must be either a VARIABLE, a RELATION or a FORMULA.
  • ora-10265 : Keep random system generated output out of error messages
  • ora-19566 : exceeded limit of string corrupt blocks for file string
  • ora-03234 : unable to extend index string.string subpartition string by string in tablespace string
  • ora-02225 : only EXECUTE and DEBUG privileges are valid for procedures
  • ora-01106 : database must be closed before dismounting
  • ora-06440 : ssaio: the asynchronous read returned incorrect number of bytes
  • ora-26005 : Invalid handle for direct path load
  • ora-07665 : ssrexhd: recursive exception encountered string string string string string string
  • ora-26057 : Conversion is not necessary for this direct path stream.
  • ora-00701 : object necessary for warmstarting database cannot be altered
  • ora-39309 : schema sync operation failed
  • ora-39957 : invalid warning category
  • ora-01557 : rollback segment extents must be at least string blocks
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-31102 : Already locked in exclusive mode. Cannot add lock.
  • ora-26740 : cannot downgrade because there are file groups
  • ora-23336 : priority group string does not exist
  • ora-19117 : invalid redefinition of predefined namespace prefix 'string'
  • 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.