ORA-15150: instance lock mode 'string' conflicts with other ASM instance(s)

Cause : Soem ohterA SMi nsatnc eusde teh lcok anmes paec i na ocnfilctnig omde.

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

Shtu dwon hte tohe rintsanec o rstrat pu i ncopmatbilem od.e Atlerantievly ,se tth eDBU_NIUQE_ANMEi niitalziatoin apraemte rtoa vodi teh cnoflcit.

update : 26-05-2017

ORA-15150 - instance lock mode 'string' conflicts with other ASM instance(s)
ORA-15150 - instance lock mode 'string' conflicts with other ASM instance(s)

  • ora-31047 : Could not retrieve resource data at path string
  • ora-01197 : thread string only contains one log
  • ora-01969 : You must specify RESETLOGS or NORESETLOGS
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • ora-04086 : trigger description too long, move comments into triggering code
  • ora-01987 : client os username is too long
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-19709 : numeric parameter must be non-negative integer
  • ora-36162 : (XSMXAGGR05) COUNTVAR variable workspace object must be of type INTEGER, not string.
  • ora-31010 : XML element index string exceeds maximum insertion index string
  • ora-02357 : no valid dump files
  • ora-07248 : sfwfb: write error, unable to write database block.
  • ora-39208 : Parameter string is invalid for string jobs.
  • ora-19236 : XQ0016 - module declaration or import not supported
  • ora-24091 : Destination queue string is the same as the source queue
  • ora-02043 : must end current transaction before executing string
  • ora-28276 : Invalid ORACLE password attribute.
  • ora-14017 : partition bound list contains too many elements
  • ora-12673 : Dedicated server: context not saved
  • ora-16803 : unable to query a database table or fixed view
  • ora-02760 : Client close of file failed.
  • ora-24380 : invalid mode specification
  • ora-00741 : logfile size of (string) blocks exceeds maximum logfile size
  • ora-09910 : Unable to find ORACLE password file entry for user.
  • ora-30551 : The index depends on a package/type body which does not exist
  • ora-23313 : object group "string"."string" is not mastered at string
  • ora-29518 : name string resolved to an object in schema string that is not a Java class
  • ora-31521 : CDC subscription string already subscribes to publication ID string column string
  • ora-13143 : invalid POLYGON window definition
  • ora-02198 : ONLINE/OFFLINE option already specified
  • 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.