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 : 19-08-2017
ORA-15065

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

  • ora-31155 : attribute string not in XDB namespace
  • ora-29951 : warning in the execution of ODCIINDEXSPLITPARTITION routine
  • ora-22336 : table contained 8.0 image format, must specify INCLUDING DATA
  • ora-12921 : database is not in force logging mode
  • ora-19118 : duplicate default namespace definition - string
  • ora-01523 : cannot rename data file to 'string' - file already part of database
  • ora-19252 : XQ0032 - too many declarations for base URI
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-01921 : role name 'string' conflicts with another user or role name
  • ora-03131 : an invalid buffer was provided for the next piece
  • ora-01355 : logminer tablespace change in progress
  • ora-35020 : (QFCHECK02) The analytic workspace and EIF file definitions of workspace object have mismatched dimensioning.
  • ora-01075 : you are currently logged on
  • ora-08274 : Out of memory for environment variable
  • ora-32517 : cannot issue ORADEBUG command (waited number ms for process string); total wait time exceeds number ms
  • ora-19707 : invalid record block number - string
  • ora-06900 : CMX: cannot read tns directory
  • ora-26726 : logical standby and DOWNSTREAM_REAL_TIME_MINE are incompatible
  • ora-37082 : Invalid percent
  • ora-14055 : keyword REBUILD in ALTER INDEX REBUILD must immediately follow
  • ora-02486 : Error in writing trace file string
  • ora-17610 : file 'string' does not exist and no size specified
  • ora-26051 : internal error parsing packed decimal format string
  • ora-14312 : Value string already exists in partition string
  • ora-29250 : Invalid index specifed in call to dbms_sql.bind_array
  • ora-27075 : SSTMOFRC constant too large
  • ora-33284 : (DBERR12) Analytic workspace string cannot be opened in MULTI mode before converting it by the latest version of string.
  • ora-25955 : all tables must be joined in the where clause
  • ora-24804 : Lob read/write functions called while another OCI LOB read/write streaming is in progress
  • ora-16656 : higher DRC UID sequence number detected
  • 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.