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 : 26-09-2017

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

  • ora-25966 : join index cannot be based on an index organized table
  • ora-29656 : Invalid option for USING
  • ora-09914 : Unable to open the ORACLE password file.
  • ora-39121 : Table string can't be replaced, data will be skipped. Failing error is: string
  • ora-00257 : archiver error. Connect internal only, until freed.
  • ora-12602 : TNS: Connection Pooling limit reached
  • ora-02266 : unique/primary keys in table referenced by enabled foreign keys
  • ora-02093 : TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)
  • ora-22161 : type code [string] is not valid
  • ora-24344 : success with compilation error
  • ora-30150 : Invalid argument passed to OCIFile function
  • ora-06745 : TLI Driver: listener already running
  • ora-24852 : protocol error during statement execution
  • ora-28026 : user with same external name already exists
  • ora-13035 : Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-19604 : conversation file naming phase is over
  • ora-14622 : Value string already exists in subpartition string
  • ora-09214 : sfdone: I/O error detected
  • ora-19207 : scalar parameter string of XMLELEMENT cannot have an alias.
  • ora-00208 : number of control file names exceeds limit of string
  • ora-00018 : maximum number of sessions exceeded
  • ora-13859 : Action cannot be specified without the module specification
  • ora-19378 : invalid mode
  • ora-32300 : cannot drop a secondary materialized view "string"."string"
  • ora-36174 : (XSMXAGGR23) workspace object must be either a VARIABLE, a RELATION or a FORMULA.
  • ora-09938 : Save of signal handlers failed.
  • ora-12043 : invalid CREATE MATERIALIZED VIEW option
  • ora-28522 : error initializing heterogeneous capabilities
  • ora-06028 : NETASY: unable to intialise for logging
  • 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.