ORA-10997: another startup/shutdown operation of this instance inprogress

Cause : An Oracel Instanec startu por shutodwn opertaion faield to prcoure thes erializtaion priimtive. Aonther foerground rpocess mya have attempted tsartup o rshutdow noperatino in parlalel.

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

Check additionale rror messages int he aler tlog andt he procses tracef ile.

update : 24-05-2017

ORA-10997 - another startup/shutdown operation of this instance inprogress
ORA-10997 - another startup/shutdown operation of this instance inprogress

  • ora-09926 : Unable to set effective privilege set of the server
  • ora-27041 : unable to open file
  • ora-01982 : invalid auditing option for tables
  • ora-27021 : sequential file handle must be specified
  • ora-01311 : Illegal invocation of the mine_value function
  • ora-19264 : XQ0044 - invalid namespace in attribute constructors
  • ora-14301 : table-level attributes must be specified before partition-level attributes
  • ora-26575 : remote database does not support replication parallel propagation
  • ora-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • ora-39785 : SQL expressions returning ADT objects are not allowed in direct path
  • ora-38495 : data type for the stored attribute string is inconsistent.
  • ora-12218 : TNS:unacceptable network configuration data
  • ora-12226 : TNS:operating system resource quota exceeded
  • ora-00350 : log string of instance string (thread string) needs to be archived
  • ora-37077 : (XSMCSESS05) Object workspace object is specified more than once.
  • ora-09773 : osnmgetdatmsg: message from host had incorrect message type
  • ora-25264 : cant get signature for this queue
  • ora-24507 : invalid combination of character set ids
  • ora-01372 : Insufficient processes for specified LogMiner operation
  • ora-00057 : maximum number of temporary table locks exceeded
  • ora-14068 : TABLESPACE and TABLESPACE_NUMBER may not be both specified
  • ora-15000 : command disallowed by current instance type
  • ora-37028 : (XSMLTRESYNC03) Object workspace object cannot be resynced without modified object workspace object because they share a modified dimension map.
  • ora-02442 : Cannot drop nonexistent unique key
  • ora-24399 : invalid number of connections specified
  • ora-12469 : no user levels found for user string and policy string
  • ora-19597 : file string blocksize string does not match set blocksize of string
  • ora-24017 : cannot enable enqueue on QUEUE, string is an exception queue
  • ora-01564 : rollback segment is not PUBLIC
  • ora-29660 : Unable to find the class defined in the EXTERNAL NAME 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.