|
ORA-16649: possible failover to another database prevents this database being opened
Cause: An attempt to open the database was made either when a failover occurred or while fast-start failover was enabled and the fast-start failover status could not be evaluated.
Action: Check if a failover did occur. If fast-start failover is enabled, and a failover did not occur, ensure that connectivity exists between this database and either the observer or the target standby database. Then, try opening the database again.
ORA-16650: command incompatible when fast-start failover is enabled
Cause: An attempt was made to issue a command that is not permitted when fast-start failover is enabled. The command was not issued using the Data Guard broker.
Action: The command must be issued using the Data Guard broker.
ORA-16651: requirements not met for enabling fast-start failover
Cause: The attempt to enable fast-start failover could not be completed because one or more requirements were not met:
– The Data Guard configuration must be in either MaxAvailability or MaxPerformance protection mode.
– The LogXptMode property for both the primary database and the fast-start failover target standby database must be set to SYNC if the configuration protection mode is set to MaxAvailability mode.
– The LogXptMode property for both the primary database and the fast-start failover target standby database must be set to ASYNC if the configuration protection mode is set to MaxPerformance mode.
– The primary database and the fast-start failover target standby database must both have flashback enabled.
– No valid target standby database was specified in the primary database FastStartFailoverTarget property prior to the attempt to enable fast-start failover, and more than one standby database exists in the Data Guard configuration.
Action: Retry the command after correcting the issue:
– Set the Data Guard configuration to either MaxAvailability or MaxPerformance protection mode.
– Ensure that the LogXptMode property for both the primary database and the fast-start failover target standby database are set to SYNC if the configuration protection mode is set to MaxAvailability.
– Ensure that the LogXptMode property for both the primary database and the fast-start failover target standby database are set to ASYNC if the configuration protection mode is set to MaxPerformance.
– Ensure that both the primary database and the fast-start failover target standby database have flashback enabled.
– Set the primary database FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the desired target standby database and the desired target standby database FastStartFailoverTarget property to the DB_UNIQUE_NAME value of the primary database.
ORA-16652: fast-start failover target standby database is disabled
Cause: The command to enable or disable fast-start failover could not be completed because Data Guard broker management of the fast-start failover target standby database is currently disabled.
Action: Enable broker management of the target standby database and reissue the command. If an attempt was made to disable fast-start failover when this error was reported, disable fast-start failover forcibly using the DGMGRL DISABLE FAST_START FAILOVER FORCE command. Consult the documentation for more information.
ORA-16653: failed to reinstate database
Cause: The Data Guard broker failed to reinstate the specified database because the REINSTATE command failed or because the database is already enabled.
Action: Additional information about this failure is recorded in the primary database or the specified database Data Guard broker log files. This information is helpful in determining how to proceed.
ORA-16654: fast-start failover is enabled
Cause: The attempted command was not allowed while fast-start failover was enabled:
– The FastStartFailoverTarget property may not be modified.
– The LogXptMode property for either the primary database or the fast-start failover target standby database may not be modified.
– The configuration’s protection mode may not be modified.
– Neither the broker configuration nor the fast-start failover target standby database may be disabled using the DGMGRL CLI DISABLE command.
– Neither the broker configuration nor the fast-start failover target standby database may be removed using the DGMGRL CLI REMOVE command.
– The FAILOVER IMMEDIATE command is not allowed.
– The DG_BROKER_START initialization parameter may not be set to FALSE.
Action: Disable fast-start failover, using the FORCE option if required. Then retry the attempted command.
ORA-16655: specified target standby database invalid
Cause: The attempted command was not allowed because fast-start failover was enabled for this Data Guard configuration and the target standby database specified in the command differs from the standby database that was indicated by the FastStartFailoverTarget property associated with the current primary database.
Action: Retry the attempted command by specifying the standby database that is indicated by the FastStartFailoverTarget property that is associated with the current primary database. Alternatively, fast-start failover may be disabled. Then retry the command using the originally specified target standby database.
ORA-16656: Data Guard broker detected role change
Cause: The Data Guard broker detected a role during database startup or health check.
Action: Additional information about this failure is recorded in the Data Guard broker log files, one for the primary database and one for each standby database in the Data Guard configuration. This information is helpful in determining how best to proceed from this failure.
ORA-16657: reinstatement of database in progress
Cause: Reinstatement of this database was in progress.
Action: None
ORA-16658: unobserved fast-start failover configuration
Cause: The fast-start failover configuration was currently unobserved so failover was disallowed.
Action: Make sure the observer is running and has connectivity to both the primary and the target standby databases. Otherwise, disable fast-start failover to perform a failover in the absence of the observer process.
Above are list of Oracle Database Errors or Warnings from Error ORA-16649 to ORA-16658 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.
|
