ORA-16516: the current state is invalid for the attempted operation

Cause : The broker may return this error for switchover operations and for database state change operations. If this error is returned for a switchover operation, the broker has determined that either: - The databases changing roles are offline. - The primary database is not shipping log files. - The standby database that will become the primary database is not applying log files. The broker returns this error for database state change operations if the database state specified is invalid.

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

If this error is returned when attempting a switchover operation, make sure that: - The databases changing roles are online. - The primary database is shipping log files. - The standby database is applying log files. If this error is returned when attempting a database state change operation, make sure you specify a valid state.

update : 23-07-2017

ORA-16516 - the current state is invalid for the attempted operation
ORA-16516 - the current state is invalid for the attempted operation

  • ora-15013 : diskgroup "string" is already mounted
  • ora-00284 : recovery session still in progress
  • ora-18003 : an outline already exists with this signature
  • ora-00710 : new tablespace name is the same as the old tablespace name
  • ora-39093 : FLASHBACK automatically enabled to preserve database integrity.
  • ora-02373 : Error parsing insert statement for table string.
  • ora-01779 : cannot modify a column which maps to a non key-preserved table
  • ora-29888 : cannot create domain index on a table with row movement enabled
  • ora-32314 : REFRESH FAST of "string"."string" unsupported after deletes/updates
  • ora-27481 : "string.string" has an invalid schedule
  • ora-00206 : error in writing (block string, # blocks string) of control file
  • ora-01099 : cannot mount database in SHARED mode if started in single process mode
  • ora-22897 : no scope clause specified for user-defined REF column "string"
  • ora-07460 : cannot set the RESOURCE_MANAGER_PLAN parameter
  • ora-37084 : Output valueset string must match string's dimensionality
  • ora-07588 : spdcr: $GETJPIW get image name failure
  • ora-16659 : failover operation in progress
  • ora-29314 : tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
  • ora-31025 : Invalid document element
  • ora-19330 : Type 'string'.'string' not installed. Please install the type before using the CREATE_DBURI operator
  • ora-02822 : Invalid block offset
  • ora-12326 : database string is closing immediately; no operations are permitted
  • ora-38727 : FLASHBACK DATABASE requires a current control file.
  • ora-38783 : Instance recovery required.
  • ora-30161 : A system error occurred during the OCIFile function call
  • ora-29502 : NAMED keyword required in CREATE JAVA RESOURCE
  • ora-29518 : name string resolved to an object in schema string that is not a Java class
  • ora-01337 : log file has a different compatibility version
  • ora-14261 : partition bound may not be specified when adding this Hash partition
  • ora-12596 : TNS:internal inconsistency
  • 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.