Oracle Database Errors or Warnings from Error ORA-16659 to ORA-16700

SQLServerF1

ORA-16659: failover operation in progress
Cause: A primary database that restarted contacted a standby database that is being failed over to.
Action: Shut down the primary database and wait for failover to complete on the standby database. Once failover is complete, restart the old primary database. If the failover occurred due to fast-start failover, restarting the primary database after failover is complete allows it to be automatically reinstated as a standby database to the new primary database.
ORA-16660: fast-start failover operation attempted in absence of a broker configuration
Cause: An attempt was made to enable or disable fast-start failover when connected to a standby database for which broker configuration details are currently unavailable. For instance, the standby database may currently require re-creation (or flashback reinstantiation) before it may respond to broker client commands.
Action: 1) An attempt to enable or disable (non-FORCE) fast-start failover at this standby database will be rejected until such time that the broker configuration details have been made available to that standby database from the primary database. This normally occurs when the standby database is successfully re-created or flashed back, and then reenabled at the primary database. 2) Use the FORCE option to override fast-start failover that has been enabled at the standby database even when the broker configuration details are currently unavailable to the standby database. In this case, this status message is only a warning. Note that fast-start failover is not formally disabled in the broker configuration. The effect of this command issued under these circumstances may or may not be permanent, depending upon when the primary and standby databases regain full communication between each other and if the state of fast-start failover has been altered at the primary database in the meantime.
ORA-16661: the standby database needs to be reinstated
Cause: A switchover or failover operation has caused this database to require reinstatement.
Action: Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. If the target database has flashback enabled and it has sufficient flashback logs, the database will be reinstated as a standby database for the current primary database.

ORA-16662: network timeout when contacting a database
Cause: In response to the issued command, the Data Guard broker attempted to contact a database in the Data Guard configuration. That attempt failed because there was no response from that database after the period of time specified by the NetTimeout property for that database.
Action: Check the Data Guard broker log for the details of the failure. Fix the problem and try the command again.
ORA-16664: unable to receive the result from a database
Cause: During execution of a command, a database in the Data Guard broker configuration failed to return a result.
Action: Check Data Guard broker logs for the details of the failure. Fix any possible network problems and try the command again.
ORA-16665: timeout waiting for the result from a database
Cause: The Data Guard broker was forced to time out a network connection
Action: Check Data Guard broker logs for the details of the failure. Fix any possible network problems and reissue the command.

ORA-16666: unable to initiate fast-start failover on a standby database
Cause: The request to initiate a fast-start failover using DBMS_DG.INITIATE_FS_FAILOVER was made to a standby database. An application may only request that fast-start failover be initiated by calling DBMS_DG.INITIATE_FS_FAILOVER on a primary database.
Action: Call DBMS_DG.INITIATE_FS_FAILOVER on the primary database.
ORA-16667: request Data Guard broker client to reissue command
Cause: The Data Guard broker operation required the same command be issued again from the client.
Action: If DGMGRL or Enterprise Manager has not already done so, reissue the same command to the Data Guard broker manually.
ORA-16668: operation invalid on fast-start failover target database
Cause: The attempted command was not allowed on the fast-start failover target standby database when fast-start failover is currently enabled.
Action: Retry the attempted command on a database other than the fast-start failover target standby database. Alternatively, disable fast-start failover and reissue the same command to the fast-start failover target standby database.
ORA-16700: the standby database has diverged from the primary database
Cause: The primary database may have been flashed back or restored from a backup set and then reopened with the RESETLOGS option.
Action: Re-create the standby database from the primary database or flash back the standby database to the same point the primary database had been flashed back to.

Above are list of Oracle Database Errors or Warnings from Error ORA-16659 to ORA-16700 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database.  Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *