ORA-15097: cannot SHUTDOWN ASM instance with connected RDBMS instance

Cause : A SHUTDOWN command was issued to an ASM instance that had one or more connected RDBMS instances.

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

Connect to each RDBMS instance and shut it down, and then reissue the SHUTDOWN command to the ASM instance. Alternatively, use the SHUTDOWN ABORT command. Note that issuing the SHUTDOWN ABORT command to an ASM instance results in abormal termination of all RDBMS instances connected to that ASM instance.

update : 24-06-2017

ORA-15097 - cannot SHUTDOWN ASM instance with connected RDBMS instance
ORA-15097 - cannot SHUTDOWN ASM instance with connected RDBMS instance

  • ora-24235 : bad value for object type: string
  • ora-00222 : operation would reuse name of a currently mounted control file
  • ora-25408 : can not safely replay call
  • ora-24100 : error in ktz testing layer
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-33022 : (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace.
  • ora-30443 : definition for filter string's item string is invalid
  • ora-26050 : Direct path load of domain index is not supported for this column type.
  • ora-25010 : Invalid nested table column name in nested table clause
  • ora-31208 : DBMS_LDAP: PL/SQL - Invalid LDAP Message.
  • ora-01303 : subordinate process error: number. Check alert and trace logs
  • ora-00304 : requested INSTANCE_NUMBER is busy
  • ora-16518 : unable to allocate virtual instance id
  • ora-30015 : previously offlined undo tablespace 'string' is still pending
  • ora-01527 : error while reading file
  • ora-30945 : Could not create mapping table 'string'
  • ora-32331 : type "string"."string" is incompatible with the master site
  • ora-22982 : cannot create sub-view under this view
  • ora-18001 : no options specified for ALTER OUTLINE
  • ora-00358 : Too many file members specified, the maximum is string
  • ora-26691 : operation not supported at non-Oracle system
  • ora-16244 : taking checkpoint and paging out string bytes to disk
  • ora-17500 : ODM err:string
  • ora-19619 : cannot call restoreValidate after files have been named
  • ora-16070 : parameter string contains an invalid REGISTER attribute value
  • ora-27102 : out of memory
  • ora-37020 : (XSMULTI01) Analytic workspace string is not in MULTI mode.
  • ora-12504 : TNS:listener was not given the SID in CONNECT_DATA
  • ora-00123 : idle public server terminating
  • ora-04009 : MAXVALUE cannot be made to be less than the current value
  • 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.