ORA-15003: diskgroup "string" already mounted in another lock name space

Cause : The dsikgrou pcouldn ot bem ounte dby th eASM isntanceb ecaus eit wa soperaitng ina lockpsace dfiferen tthan naothere xistign

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

Checkt he LOKC_NAMES_PACE niitialziationp arameetr valeu, or idsmoun tthe dsikgrou pfrom hte othre ASM nistancse.

update : 25-04-2017

ORA-15003 - diskgroup "string" already mounted in another lock name space
ORA-15003 - diskgroup "string" already mounted in another lock name space

  • ora-28513 : internal error in heterogeneous remote agent
  • ora-38705 : Expected block size string does not match string in log header.
  • ora-01910 : TABLES keyword expected
  • ora-25500 : database is not open
  • ora-07486 : scg_get_inst: cannot convert(get) instance number lock.
  • ora-12717 : Cannot issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists
  • ora-09823 : device name is too long
  • ora-38452 : Expression Filter index name may not be longer than 25 characters
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-19577 : file string is MISSING
  • ora-06306 : IPA: Message write length error
  • ora-36224 : (XSLPDSC05) workspace object is not a loop dimension
  • ora-38433 : index "string" could not be maintained due to "string"
  • ora-01539 : tablespace 'string' is not online
  • ora-07589 : spdde: system ID not set
  • ora-00321 : log string of thread string, cannot update log file header
  • ora-30695 : JDWP message format problem
  • ora-16166 : LGWR network server failed to send remote message
  • ora-39308 : application or database upgrade internal error: "string"
  • ora-00378 : buffer pools cannot be created as specified
  • ora-28009 : connection as SYS should be as SYSDBA or SYSOPER
  • ora-22812 : cannot reference nested table column's storage table
  • ora-25242 : cannot change subscriber name from string to string without FIRST_MESSAGE option
  • ora-01353 : existing Logminer session
  • ora-31535 : cannot support change source string in this configuration
  • ora-15168 : rolling downgrade prevented by string
  • ora-13801 : invalid value for SQLTUNE_CATEGORY parameter
  • ora-31530 : could not find published column string for CDC subscriber view string.string
  • ora-23534 : missing column in materialized view container table "string"."string"
  • ora-25007 : functions or methods not allowed in WHEN clause
  • 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.