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 : 25-09-2017

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

  • ora-16412 : ONDEMAND archival requires active SQL apply operation
  • ora-31012 : Given XPATH expression not supported
  • ora-10863 : Control behavior of buffered background operations
  • ora-19595 : archivelog string already included in backup conversation
  • ora-01313 : LogMiner dictionary column type different from specified type
  • ora-28263 : Insufficient memory in global context pool
  • ora-10944 : trace name context forever
  • ora-31639 : unexpected data found
  • ora-31487 : cannot support begin dates or end dates in this configuration
  • ora-02294 : cannot enable (string.string) - constraint changed during validation
  • ora-23397 : global name "string" does not match database link name "string"
  • ora-01299 : dictionary string corresponds to a different database incarnation
  • ora-07713 : sksamtd: could not mount archival device (SYS$MOUNT failure)
  • ora-24853 : failed to connect thread to shared subsystem
  • ora-32401 : materialized view log on "string"."string" does not have new values
  • ora-01146 : cannot start online backup - file string is already in backup
  • ora-25212 : invalid PRIORITY specified when using sequence deviation
  • ora-36908 : (XSAGDNGL46) In AGGMAP workspace object, MODEL workspace object has the repeating dimension with the previous model.
  • ora-12427 : invalid input value for string parameter
  • ora-09769 : osnmbr: cannot send break message
  • ora-07670 : $IDTOASC failed translating a secrecy category
  • ora-13128 : current tiling level exceeds user specified tiling level
  • ora-03262 : the file is non-empty
  • ora-15127 : ASM file name 'string' cannot use templates
  • ora-29809 : cannot drop an operator with dependent objects
  • ora-31206 : DBMS_LDAP: PL/SQL - Invalid LDAP search scope.
  • ora-31698 : Error stack buffer size must be specified and must be greater than 0.
  • ora-15054 : disk "string" does not exist in diskgroup "string"
  • ora-07491 : scgrcl: cannot cancel lock request.
  • ora-12527 : TNS:listener: all instances are in restricted mode or blocking new connections
  • 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.