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 : 20-08-2017

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

  • ora-31424 : change table has active subscriptions
  • ora-14320 : DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT
  • ora-01112 : media recovery not started
  • ora-24367 : user handle has not been set in service handle
  • ora-13837 : invalid HASH_VALUE
  • ora-30953 : XML minoccurs value (string) violated
  • ora-38428 : too many attributes selected for indexing
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-14119 : specified partition bound is too long
  • ora-22282 : non-contiguous append to a buffering enabled LOB not allowed
  • ora-12812 : only one PARALLEL or NOPARALLEL clause may be specified
  • ora-38713 : Flashback Database logging is already turned on.
  • ora-08192 : Flashback Table operation is not allowed on fixed tables
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-02337 : not an object type column
  • ora-01577 : cannot add log file 'string' - file already part of database
  • ora-07847 : sllfop: $CONNECT failure
  • ora-26512 : error pushing transaction to def$error
  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-31643 : unable to close dump file "string"
  • ora-07244 : ssfccf: create file failed, file size limit reached.
  • ora-38854 : cannot mark instance string (redo thread string) as disabled
  • ora-13904 : The file has been dropped and recreated during the procedure call.
  • ora-13778 : no new name or owner specified for "SQL Tuning Set"
  • ora-16752 : resource guard could not mount standby database
  • ora-14076 : submitted alter index partition/subpartition operation is not valid for local partitioned index
  • ora-36223 : (XSLPDSC04) object workspace object in IGNORE or DENSE list has illegal type
  • ora-07569 : slspool: $CLOSE failure
  • ora-19281 : XQ0055 - It is a static error if a Prolog contains more than one inherit-namespaces declaration
  • ora-39202 : Data cannot be filtered or selected in string jobs.
  • 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.