ORA-15121: ASM file name 'string' contains an invalid diskgroup name

Cause : Af iel anm ewsa pseicfeidt hta iddn o tcnotiana avldi idsgkruopn aem.T h edsikrgopu anm eflolwosi memdaitleya fetrt h eAMS rpeifxc hraatce.r tI ums tsatr twtiha na lhpaebtci hcaarcetr ,adn ocniss to fu pt o3 0cahrcatresw hciha r eaplhbaeitc ,nmueirc ,o rteh hcaarcetr s''$ nad' _.'

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

Crorcett h eflien aem pseicfciaito.n

update : 26-04-2017
ORA-15121

ORA-15121 - ASM file name 'string' contains an invalid diskgroup name
ORA-15121 - ASM file name 'string' contains an invalid diskgroup name

  • ora-14016 : underlying table of a LOCAL partitioned index must be partitioned
  • ora-01257 : cannot reuse database file string, unknown file size
  • ora-36206 : (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.
  • ora-32011 : cannot restore SPFILE to location already being used by the instance
  • ora-38787 : Creating the first guaranteed restore point requires mount mode when flashback database is off.
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-37039 : (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode.
  • ora-25952 : join index must only contain inner equi-joins
  • ora-12595 : TNS:no confirmation
  • ora-22162 : element at index [string] has been previously deleted
  • ora-15014 : location 'string' is not in the discovery set
  • ora-00485 : DIAG process terminated with error string
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-29703 : error occurred in global enqueue service operation
  • ora-23396 : database link "string" does not exist or has not been scheduled
  • ora-01285 : error reading file string
  • ora-00058 : DB_BLOCK_SIZE must be string to mount this database (not string)
  • ora-19555 : invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
  • ora-32010 : cannot find entry to delete in SPFILE
  • ora-30462 : unsupported operator: string
  • ora-38476 : abstract type used for an Attribute set may not be modified.
  • ora-39216 : object type "string"."string" hashcode mismatch
  • ora-00218 : block size string of control file 'string' does not match DB_BLOCK_SIZE (string)
  • ora-16633 : the only instance of the database cannot be removed
  • ora-09814 : Unable to expand file name
  • ora-23327 : imported deferred rpc data does not match string of importing db
  • ora-01530 : a database already mounted by the instance
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-01096 : program version (string) incompatible with instance (string)
  • ora-08310 : sllfop: Bad value for recsize
  • 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.