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 : 29-04-2017

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

  • ora-26022 : index string.string was made unusable due to:
  • ora-29254 : Invalid lower_bound argument passed to procedure dbms_sql.define_array
  • ora-19284 : Encoding specification in version declaration not supported
  • ora-34350 : (MXDSS06) string is an open analytic workspace.
  • ora-28592 : agent control utility: agent SID not set
  • ora-24086 : cannot create a 8.0 compatible string queue
  • ora-06130 : NETTCP: host access denied
  • ora-36667 : (XSDPART05) string is not a legal CONCAT partition.
  • ora-01292 : no log file has been specified for the current LogMiner session
  • ora-39002 : invalid operation
  • ora-32304 : materialized views with user-defined types cannot use prebuilt table
  • ora-13527 : invalid baseline name
  • ora-22856 : cannot add columns to object tables
  • ora-19870 : error reading backup piece string
  • ora-25150 : ALTERING of extent parameters not permitted
  • ora-07280 : slsget: unable to get process information.
  • ora-39168 : Object path string was not found.
  • ora-33292 : (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode.
  • ora-38772 : cannot add datafile 'string' - file could not be created
  • ora-28577 : argument string of external procedure string has unsupported datatype string
  • ora-29918 : cannot create domain indexes on temporary tables
  • ora-31115 : XDB configuration error: string
  • ora-29342 : user string does not exist in the database
  • ora-24167 : incompatible rule engine objects, cannot downgrade
  • ora-30439 : refresh of 'string.string' failed because of string
  • ora-13005 : recursive HHCODE function error
  • ora-30118 : syntax error at 'string' at the end of input
  • ora-36872 : (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
  • ora-19698 : %s is from different database: id=string, db_name=string
  • ora-39109 : Unprivileged users may not operate upon other users' schemas
  • 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.