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 : 30-05-2017

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

  • ora-15017 : diskgroup "string" cannot be mounted
  • ora-30941 : Cannot specify empty URI for non-default namespace 'string'
  • ora-38445 : TOP clause not allowed with no statistics
  • ora-08454 : more than one S symbol specified in picture mask
  • ora-01684 : max # extents (string) reached in table string.string partition string
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-07234 : slemcw: fseek error.
  • ora-24062 : Subscriber table string inconsistent with queue table string
  • ora-12716 : Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
  • ora-09283 : sllfsk: error skipping records
  • ora-24330 : internal OCI error
  • ora-07804 : slpdtb: number too large for supplied buffer
  • ora-21604 : property [string] is not a property of transient or value instances
  • ora-16253 : Logical Standby cannot start due to incomplete terminal apply
  • ora-00115 : connection refused; dispatcher connection table is full
  • ora-19206 : Invalid value for query or REF CURSOR parameter
  • ora-02783 : Both post and wait functions were not specified
  • ora-29521 : referenced name string could not be found
  • ora-07498 : spstp: Unable to open /dev/resched.
  • ora-29813 : non-supported object type with associate statement
  • ora-06805 : TLI Driver: could not send datagram SAP packet for SPX
  • ora-28554 : pass-through SQL: out of cursors
  • ora-00088 : command cannot be executed by shared server
  • ora-04044 : procedure, function, package, or type is not allowed here
  • ora-03287 : invalid FREELIST GROUP specified
  • ora-01909 : REUSE keyword expected
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-03261 : the tablespace string has only one file
  • ora-07680 : sou2os: another call to Oracle currently executing
  • ora-01059 : parse expected before a bind or execute
  • 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.