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 : 24-04-2017
ORA-16516

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

  • ora-28666 : option not allowed for an index on UROWID column(s)
  • ora-27200 : skgfpgo: sbtpcstart returned error
  • ora-36740 : A CHILDLOCK was detected in your valueset
  • ora-28506 : parse error in data dictionary translation for string stored in string
  • ora-31427 : publication string already subscribed
  • ora-01543 : tablespace 'string' already exists
  • ora-28182 : cannot acquire Kerberos service ticket for client
  • ora-12916 : Cannot use default permanent tablespace with this release
  • ora-12087 : online redefinition not allowed on tables owned by "string"
  • ora-01490 : invalid ANALYZE command
  • ora-30175 : invalid type given for an argument
  • ora-19658 : cannot inspect string - file is from different resetlogs
  • ora-22600 : encountered 8.0.2 (Beta) VARRAY data that cannot be processed
  • ora-16041 : Remote File Server fatal error
  • ora-02467 : Column referenced in expression not found in cluster definition
  • ora-40109 : inconsistent logical data record
  • ora-13765 : Value "string" is illegal for a result limit.
  • ora-24912 : Listener thread failed. string
  • ora-08308 : sllfop: Cannot open file
  • ora-32129 : cannot get information about this column
  • ora-30352 : inconsistent numeric precision or string length
  • ora-16536 : unknown object type
  • ora-06927 : CMX: T_DATAIN received before all data written
  • ora-31195 : XML node 'string' (type=string) does not support this operation
  • ora-01038 : cannot write database file version string with ORACLE version string
  • ora-29866 : cannot create domain index on a column of index-organized table
  • ora-14126 : only a may follow description(s) of resulting partitions
  • ora-36696 : (XSRELTBL02) QDR dimension workspace object should not be the related dimension of the relation.
  • ora-23398 : user name "string" at database link "string" does not match local user name "string"
  • ora-16191 : Primary log shipping client not logged on standby
  • 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.