ORA-16675: database instance restart required for property value modification to take effect
Cause:
One or more properties that correspond to static initialization parameters were modified, but the database instances were not restarted. Or, a static initialization parameter that corresponds to a broker property was modified using an ALTER SYSTEM SQL*Plus statement.
Action:
Restart the database instances for the modified property values to take effect. If the error persists after having restarted the instance, use the DGMGRL CLI or Enterprise Manager to modify the property the static initialization parameter corresponds to.
ORA-16676: RedoRoutes property for two or more databases contains a circular route
ORA-16676: RedoRoutes property for two or more databases contains a circular route
Cause:
The value of a RedoRoutes property for two or more databases was set such that a database that sends redo also receives redo data data in the same route. For example, A sends to B, B sends to C, and C sends to A.
Action:
Correct the setting of the RedoRoutes propety on one or more databases to eliminate the circular route.
Cause:
The value of a RedoRoutes property for two or more databases was set such that a database that sends redo also receives redo data data in the same route. For example, A sends to B, B sends to C, and C sends to A.
Action:
Correct the setting of the RedoRoutes propety on one or more databases to eliminate the circular route.
ORA-16677: physical standby database cannot be an alternate destination
ORA-16677: physical standby database cannot be an alternate destination
Cause:
A physical standby database was set as an alternate destination for another physical standby, or for a far sync instance and the FALLBACK keyword was not specified.
Action:
Ensure that a physical standby database is not set to be an alternate destination for another physical standby. If the physical standby is to be an alternate destination for a far sync instance, be sure to specify the FALLBACK keyword.
Cause:
A physical standby database was set as an alternate destination for another physical standby, or for a far sync instance and the FALLBACK keyword was not specified.
Action:
Ensure that a physical standby database is not set to be an alternate destination for another physical standby. If the physical standby is to be an alternate destination for a far sync instance, be sure to specify the FALLBACK keyword.
ORA-16678: unrecognized or duplicate attribute specified
ORA-16678: unrecognized or duplicate attribute specified
Cause:
The specified value contained an unrecognized or duplicated attribute.
Action:
Ensure the property string does not contain any undefined or duplicate attributes. See the Data Guard broker documentation for supported attributes.
Cause:
The specified value contained an unrecognized or duplicated attribute.
Action:
Ensure the property string does not contain any undefined or duplicate attributes. See the Data Guard broker documentation for supported attributes.
ORA-16679: one or more illegal keywords found
ORA-16679: one or more illegal keywords found
Cause:
The specified value contains one or more illegal keywords.
Action:
See the Data Guard broker documentation for the supported keywords.
Cause:
The specified value contains one or more illegal keywords.
Action:
See the Data Guard broker documentation for the supported keywords.
ORA-16660: fast-start failover operation attempted in absence of a broker configuration
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.
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
ORA-16661: the standby database needs to be reinstated
Cause:
A role change has caused this database to require reinstatement.
Action:
Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. Reinstate the database as soon as possible, because the database will have to be re-created if another role change occurs while it is in this state.
Cause:
A role change has caused this database to require reinstatement.
Action:
Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. Reinstate the database as soon as possible, because the database will have to be re-created if another role change occurs while it is in this state.
ORA-16662: network timeout when contacting a 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 CommunicationTimeout configuration property.
Action:
Check the Data Guard broker log for the details of the failure. Fix the problem and try the command again.
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 CommunicationTimeout configuration property.
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
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. Ensure network communication is working properly amongst the members of the configuration. Fix any possible network problems and reissue the command.
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. Ensure network communication is working properly amongst the members of the configuration. Fix any possible network problems and reissue the command.
ORA-16665: timeout waiting for the result from a database
ORA-16665: timeout waiting for the result from a database
Cause:
The Data Guard broker was forced to time out a network connection to a remote database because:
- The network call to The remote database did not complete in a timely manner.
- The remote database was unable to execute The command due to an instance failure.
Action:
Check Data Guard broker logs for the details of the failure. If the network call did not complete in a timely manner, increase the CommunicationTimeout configuration property value and reissue the command.
Cause:
The Data Guard broker was forced to time out a network connection to a remote database because:
- The network call to The remote database did not complete in a timely manner.
- The remote database was unable to execute The command due to an instance failure.
Action:
Check Data Guard broker logs for the details of the failure. If the network call did not complete in a timely manner, increase the CommunicationTimeout configuration property value and reissue the command.
ORA-16666: unable to initiate fast-start failover on a bystander standby database
ORA-16666: unable to initiate fast-start failover on a bystander standby database
Cause:
The request to initiate a fast-start failover using DBMS_DG.INITIATE_FS_FAILOVER was made on a bystander standby database. DBMS_DG.INITIATE_FS_FAILOVER can only be called on either the primary or fast-start failover target standby database.
Action:
Call DBMS_DG.INITIATE_FS_FAILOVER on either the primary or fast-start failover target standby database.
Cause:
The request to initiate a fast-start failover using DBMS_DG.INITIATE_FS_FAILOVER was made on a bystander standby database. DBMS_DG.INITIATE_FS_FAILOVER can only be called on either the primary or fast-start failover target standby database.
Action:
Call DBMS_DG.INITIATE_FS_FAILOVER on either the primary or fast-start failover target standby database.
ORA-16667: request Data Guard broker client to reissue command
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.
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 cannot be performed on the fast-start failover target standby database
ORA-16668: operation cannot be performed on the fast-start failover target standby database
Cause:
The database specified for the operation was the fast-start failover target standby database.
Action:
Retry the operation on a different database. Alternatively, disable fast-start failover and retry the operation.
Cause:
The database specified for the operation was the fast-start failover target standby database.
Action:
Retry the operation on a different database. Alternatively, disable fast-start failover and retry the operation.
ORA-16669: instance cannot be opened because the Active Data Guard option is disabled
ORA-16669: instance cannot be opened because the Active Data Guard option is disabled
Cause:
The attempt to open the instance failed because the Active Data Guard option was not enabled and Redo Apply was either running or was about to be started by the Data Guard broker.
Action:
Stop Redo Apply or set the database state to APPLY-OFF and then open the database.
Cause:
The attempt to open the instance failed because the Active Data Guard option was not enabled and Redo Apply was either running or was about to be started by the Data Guard broker.
Action:
Stop Redo Apply or set the database state to APPLY-OFF and then open the database.
ORA-16671: instance-specific property must be set uniquely for instances of an Oracle RAC database
ORA-16671: instance-specific property must be set uniquely for instances of an Oracle RAC database
Cause:
An attempt was made to set an instance-specific property to the same value for all instances of an Oracle RAC database for a property whose value must be unique for each instance.
Action:
Use the EDIT INSTANCE command and specify the SID of each instance whose instance-specific property value is to be changed.
Cause:
An attempt was made to set an instance-specific property to the same value for all instances of an Oracle RAC database for a property whose value must be unique for each instance.
Action:
Use the EDIT INSTANCE command and specify the SID of each instance whose instance-specific property value is to be changed.
ORA-16672: some switchover databases need to be restarted manually
ORA-16672: some switchover databases need to be restarted manually
Cause:
An error occurred during the restart of either the old and the new primary databases or both in a switchover operation.
Action:
Manually restart both the old and new primary databases, including all their Oracle RAC instances if it is an Oracle RAC database.
Cause:
An error occurred during the restart of either the old and the new primary databases or both in a switchover operation.
Action:
Manually restart both the old and new primary databases, including all their Oracle RAC instances if it is an Oracle RAC database.
ORA-16673: standby database running different Oracle version
ORA-16673: standby database running different Oracle version
Cause:
The standby database was running a different version of Oracle than the primary database.
Action:
Ensure the primary and standby databases are running the same versions of Oracle.
Cause:
The standby database was running a different version of Oracle than the primary database.
Action:
Ensure the primary and standby databases are running the same versions of Oracle.
ORA-16674: standby database type has changed
ORA-16674: standby database type has changed
Cause:
An attempt to enable a database whose standby type changed from physical or snapshot to logical (or vice versa) was disallowed.
Action:
If the intention is to retain the database conversion to the new type, the database must be removed and re-added to the configuration in order to obtain correct values for database properties specific to the new standby type.
Cause:
An attempt to enable a database whose standby type changed from physical or snapshot to logical (or vice versa) was disallowed.
Action:
If the intention is to retain the database conversion to the new type, the database must be removed and re-added to the configuration in order to obtain correct values for database properties specific to the new standby type.
ORA-16648: a new observer registered with identifier string
ORA-16648: a new observer registered with identifier string
Cause:
The observer was registered with the Data Guard broker and will begin observing the Data Guard configuration for conditions that warrant doing a fast-start failover.
Action:
None
Cause:
The observer was registered with the Data Guard broker and will begin observing the Data Guard configuration for conditions that warrant doing a fast-start failover.
Action:
None
ORA-16649: possible failover to another database prevents this database from being opened
ORA-16649: possible failover to another database prevents this database from being opened
Cause:
An attempt to open the primary database was made either after a failover occurred, or when it was likely to have occurred as the result of the primary being isolated from the fast-start failover target standby database and from the fast-start failover observer.
Action:
Check if a failover did occur. If fast-start failover is enabled, and a failover did not occur, ensure that connectivity exists between the primary database and either the observer or the target standby database. Then, try opening the database again.
Cause:
An attempt to open the primary database was made either after a failover occurred, or when it was likely to have occurred as the result of the primary being isolated from the fast-start failover target standby database and from the fast-start failover observer.
Action:
Check if a failover did occur. If fast-start failover is enabled, and a failover did not occur, ensure that connectivity exists between the primary database and either the observer or the target standby database. Then, try opening the database again.
ORA-16650: unrecognized object specified
ORA-16650: unrecognized object specified
Cause:
An unrecognized database or far sync instance was specified in the command.
Action:
Try the command again using a valid object name. Use the SHOW CONFIGURATION command to identify the members in the configuration.
Cause:
An unrecognized database or far sync instance was specified in the command.
Action:
Try the command again using a valid object name. Use the SHOW CONFIGURATION command to identify the members in the configuration.
ORA-16651: requirements not met for enabling fast-start failover
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 either SYNC or FASTSYNC 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.
- fast-start failover target standby database did not receive redo data directly from The primary database or from a far SYNC instance.
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 either SYNC or FASTSYNC 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 set The desired target standby database FastStartFailoverTarget property to The DB_UNIQUE_NAME value of The primary database.
- Ensure The RedoSource properties of both The primary and The target standby database are set to either The empty value or The name of a far SYNC instance.
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 either SYNC or FASTSYNC 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.
- fast-start failover target standby database did not receive redo data directly from The primary database or from a far SYNC instance.
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 either SYNC or FASTSYNC 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 set The desired target standby database FastStartFailoverTarget property to The DB_UNIQUE_NAME value of The primary database.
- Ensure The RedoSource properties of both The primary and The target standby database are set to either The empty value or The name of a far SYNC instance.
ORA-16652: fast-start failover target standby database is disabled
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.
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
ORA-16653: failed to reinstate database
Cause:
The Data Guard broker failed to reinstate the specified database because the reinstatement could not be completed or the database was 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.
Cause:
The Data Guard broker failed to reinstate the specified database because the reinstatement could not be completed or the database was 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
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.
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
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.
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
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.
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
ORA-16657: reinstatement of database in progress
Cause:
Reinstatement of this database was in progress.
Action:
None
Cause:
Reinstatement of this database was in progress.
Action:
None
ORA-16658: unobserved fast-start failover configuration
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.
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.
ORA-16659: failover operation in progress
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.
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-16631: operation requires shutdown of database or instance string
ORA-16631: operation requires shutdown of database or instance "string"
Cause:
The Data Guard broker operation required a shutdown of the database or instance.
Action:
If database or instance has not been shutdown by the DGMGRL CLI or Enterprise Manager, shutdown the database or instance manually.
Cause:
The Data Guard broker operation required a shutdown of the database or instance.
Action:
If database or instance has not been shutdown by the DGMGRL CLI or Enterprise Manager, shutdown the database or instance manually.
ORA-16632: instance being added to database profile
ORA-16632: instance being added to database profile
Cause:
The Data Guard broker determined that an instance successfully found its database profile within the broker configuration file, but lacked an instance-specific profile. The broker automatically created an instance-specific profile and associated the instance with its database profile.
Action:
No user action is required. The broker will automatically associate the instance with its database profile and incorporate the instance into broker activity.
Cause:
The Data Guard broker determined that an instance successfully found its database profile within the broker configuration file, but lacked an instance-specific profile. The broker automatically created an instance-specific profile and associated the instance with its database profile.
Action:
No user action is required. The broker will automatically associate the instance with its database profile and incorporate the instance into broker activity.
ORA-16633: the only instance of the database cannot be removed
ORA-16633: the only instance of the database cannot be removed
Cause:
The instance to be removed was the only instance of the corresponding database that was known to the broker.
Action:
Remove the corresponding database object from the broker configuration instead of the individual instance object of the database.
Cause:
The instance to be removed was the only instance of the corresponding database that was known to the broker.
Action:
Remove the corresponding database object from the broker configuration instead of the individual instance object of the database.
ORA-16635: network connection failed during transmission
ORA-16635: network connection failed during transmission
Cause:
The Data Guard broker detected a connection failure to a remote database in the broker configuration. This failure happened in the middle of a transmission session. A transmission session usually requires more than one send operation for sending a large amount of data (for example, the broker configuration file) to the remote database.
Action:
In most cases, no user action is required. The Data Guard broker always tries to resend the data. This error will be reported if the problem persists. This error indicates there are some problems with the network connection between broker managed databases. Further network troubleshooting should be done to identify and correct the actual problem.
Cause:
The Data Guard broker detected a connection failure to a remote database in the broker configuration. This failure happened in the middle of a transmission session. A transmission session usually requires more than one send operation for sending a large amount of data (for example, the broker configuration file) to the remote database.
Action:
In most cases, no user action is required. The Data Guard broker always tries to resend the data. This error will be reported if the problem persists. This error indicates there are some problems with the network connection between broker managed databases. Further network troubleshooting should be done to identify and correct the actual problem.
ORA-16636: fast-start failover target standby in error state, cannot stop observer
ORA-16636: fast-start failover target standby in error state, cannot stop observer
Cause:
A STOP OBSERVER operation could not be completed when fast-start failover was enabled because the target standby database could not participate in the STOP OBSERVER operation.
Action:
Additional information about this failure is recorded in the Data Guard broker log file for the primary database. This information helps to identify the reason why the target standby database was unable to participate in the STOP OBSERVER operation. If the problem can be corrected by the information in the broker log file, retry the operation. Alternatively, fast-start failover may be forcibly disabled by connecting to the primary database and issuing the DISABLE FAST_START FAILOVER FORCE command from the DGMGRL CLI. Once fast-start failover has been forcibly disabled, the observer can be stopped regardless of the current state of the target standby database.
Cause:
A STOP OBSERVER operation could not be completed when fast-start failover was enabled because the target standby database could not participate in the STOP OBSERVER operation.
Action:
Additional information about this failure is recorded in the Data Guard broker log file for the primary database. This information helps to identify the reason why the target standby database was unable to participate in the STOP OBSERVER operation. If the problem can be corrected by the information in the broker log file, retry the operation. Alternatively, fast-start failover may be forcibly disabled by connecting to the primary database and issuing the DISABLE FAST_START FAILOVER FORCE command from the DGMGRL CLI. Once fast-start failover has been forcibly disabled, the observer can be stopped regardless of the current state of the target standby database.
ORA-16637: maximum number of Oracle error numbers for fast-start failover already reached
ORA-16637: maximum number of Oracle error numbers for fast-start failover already reached
Cause:
The broker could not enable any more Oracle error numbers for initiating a fast-start failover.
Action:
Use the DGMGRL CLI SHOW FAST_START FAILOVER command to help identify an Oracle error number that can be disabled before attempting to enable an additional error number for initiating a fast-start failover.
Cause:
The broker could not enable any more Oracle error numbers for initiating a fast-start failover.
Action:
Use the DGMGRL CLI SHOW FAST_START FAILOVER command to help identify an Oracle error number that can be disabled before attempting to enable an additional error number for initiating a fast-start failover.
ORA-16638: could not obtain instance status
ORA-16638: could not obtain instance status
Cause:
The broker could not determine whether the specified instance was running.
Action:
See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Support Services.
Cause:
The broker could not determine whether the specified instance was running.
Action:
See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Support Services.
ORA-16639: specified instance inactive or currently unavailable
ORA-16639: specified instance inactive or currently unavailable
Cause:
An attempt was made to perform an operation on an instance that was not running or was unavailable.
Action:
Ensure that the instance specified in the operation is running and then retry the operation.
Cause:
An attempt was made to perform an operation on an instance that was not running or was unavailable.
Action:
Ensure that the instance specified in the operation is running and then retry the operation.
ORA-16642: DB_UNIQUE_NAME mismatch
ORA-16642: DB_UNIQUE_NAME mismatch
Cause:
The expected DB_UNIQUE_NAME value did not match the actual DB_UNIQUE_NAME value for the database that the broker contacted using the connect identifier that was associated with that database.
Action:
Verify that the connect identifier correctly connects to the intended database. Verify that the name of the database the broker expects to find by that connect identifier matches the actual DB_UNIQUE_NAME for that database.
Cause:
The expected DB_UNIQUE_NAME value did not match the actual DB_UNIQUE_NAME value for the database that the broker contacted using the connect identifier that was associated with that database.
Action:
Verify that the connect identifier correctly connects to the intended database. Verify that the name of the database the broker expects to find by that connect identifier matches the actual DB_UNIQUE_NAME for that database.
ORA-16643: unable to determine location of broker configuration files
ORA-16643: unable to determine location of broker configuration files
Cause:
The Data Guard broker was unable to determine the location of its configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
Action:
Retry the operation and, if the error persists, contact Oracle Support Services.
Cause:
The Data Guard broker was unable to determine the location of its configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
Action:
Retry the operation and, if the error persists, contact Oracle Support Services.
ORA-16644: apply instance not available
ORA-16644: apply instance not available
Cause:
The broker operation could not finish, because it requires a running apply instance for the standby database, and either there was no such instance designated for the standby database or the designated apply instance was not currently available.
Action:
Start the designated apply instance or wait until the broker specifies an instance to be the apply instance and reissue the command.
Cause:
The broker operation could not finish, because it requires a running apply instance for the standby database, and either there was no such instance designated for the standby database or the designated apply instance was not currently available.
Action:
Start the designated apply instance or wait until the broker specifies an instance to be the apply instance and reissue the command.
ORA-16645: startup of an instance interrupted current operation
ORA-16645: startup of an instance interrupted current operation
Cause:
The startup of an instance that is not part of the broker configuration prevented the operation from completing.
Action:
Reissue the operation after the new instance has joined the Data Guard configuration.
Cause:
The startup of an instance that is not part of the broker configuration prevented the operation from completing.
Action:
Reissue the operation after the new instance has joined the Data Guard configuration.
ORA-16646: fast-start failover is disabled
ORA-16646: fast-start failover is disabled
Cause:
The operation was not allowed because fast-start failover was disabled.
Action:
Enable fast-start failover and retry the operation.
Cause:
The operation was not allowed because fast-start failover was disabled.
Action:
Enable fast-start failover and retry the operation.
ORA-16647: could not start more than one observer
ORA-16647: could not start more than one observer
Cause:
The observer could not start because there was another observer already observing the Data Guard configuration for which fast-start failover may have been enabled.
Action:
Stop the running observer. Retry the operation.
Cause:
The observer could not start because there was another observer already observing the Data Guard configuration for which fast-start failover may have been enabled.
Action:
Stop the running observer. Retry the operation.
ORA-16625: cannot reach database string
ORA-16625: cannot reach database "string"
Cause:
The command could not be executed because the database noted in the error text was not reachable from the database where the command was issued.
Action:
See accompanying messages for more information. Check the network connections to the specified database. Alternatively, connect to a different database in the Data Guard broker configuration and retry the command.
Cause:
The command could not be executed because the database noted in the error text was not reachable from the database where the command was issued.
Action:
See accompanying messages for more information. Check the network connections to the specified database. Alternatively, connect to a different database in the Data Guard broker configuration and retry the command.
ORA-16626: failed to enable specified database
ORA-16626: failed to enable specified database
Cause:
This status was returned when attempting to enable a standby database that:
- Could not locate itself in The broker configuration file.
- Failed to distinguish itself from two or more databases in The configuration file.
- Determined it missed a role change within The configuration.
Action:
To correct the problem, try one of these actions:
- Confirm that the host and SID names for the database exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE.
- Confirm that there are not two or more databases with The same connect identifier. that is, multiple databases in The broker configuration should not reach The same database.
- If a failover had been performed and the old primary database has been re-created (or a standby database has been re-created), make sure the Data Guard broker configuration files have been removed for that database. Do NOT remove the configuration files
Cause:
This status was returned when attempting to enable a standby database that:
- Could not locate itself in The broker configuration file.
- Failed to distinguish itself from two or more databases in The configuration file.
- Determined it missed a role change within The configuration.
Action:
To correct the problem, try one of these actions:
- Confirm that the host and SID names for the database exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE.
- Confirm that there are not two or more databases with The same connect identifier. that is, multiple databases in The broker configuration should not reach The same database.
- If a failover had been performed and the old primary database has been re-created (or a standby database has been re-created), make sure the Data Guard broker configuration files have been removed for that database. Do NOT remove the configuration files
ORA-16627: operation disallowed since no standby databases would remain to support protection mode
ORA-16627: operation disallowed since no standby databases would remain to support protection mode
Cause:
This status was returned because of one of the following:
- The broker rejected an attempt to change The overall configuration protection mode since it Could not find any enabled standby databases that supported The proposed protection mode.
- The broker rejected an attempt to enable The configuration If it Determined that there were no enabled standby databases that supported The overall protection mode.
- The broker rejected an attempt to disable or Remove a database that, If disabled or deleted, would result in no remaining standby databases that Could support The overall configuration protection mode.
- The broker rejected an attempt to SWITCHOVER If doing so would violate The overall configuration protection mode.
- Performing automatic health check If The broker Determined that no standby datbases supported The overall protection mode.
Action:
- If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode.
- for enable failures, Confirm that at least one standby database has a LogXptMode configurable property setting that supports The current overall protection mode.
- for delete and disable failures, Confirm that at least one other standby database has a LogXptMode configurable property setting that supports The overall protection mode.
- For switchover failures that occur when the configuration is operating in maximum protection or maximum availability mode, confirm that at least one other standby database has its LogXptMode configurable property set to the value "SYNC". If the configur
- for health check error, Confirm that at least one standby database has a LogXptMode configurable property setting that supports The current
overall protection mode.
Cause:
This status was returned because of one of the following:
- The broker rejected an attempt to change The overall configuration protection mode since it Could not find any enabled standby databases that supported The proposed protection mode.
- The broker rejected an attempt to enable The configuration If it Determined that there were no enabled standby databases that supported The overall protection mode.
- The broker rejected an attempt to disable or Remove a database that, If disabled or deleted, would result in no remaining standby databases that Could support The overall configuration protection mode.
- The broker rejected an attempt to SWITCHOVER If doing so would violate The overall configuration protection mode.
- Performing automatic health check If The broker Determined that no standby datbases supported The overall protection mode.
Action:
- If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode.
- for enable failures, Confirm that at least one standby database has a LogXptMode configurable property setting that supports The current overall protection mode.
- for delete and disable failures, Confirm that at least one other standby database has a LogXptMode configurable property setting that supports The overall protection mode.
- For switchover failures that occur when the configuration is operating in maximum protection or maximum availability mode, confirm that at least one other standby database has its LogXptMode configurable property set to the value "SYNC". If the configur
- for health check error, Confirm that at least one standby database has a LogXptMode configurable property setting that supports The current
overall protection mode.
ORA-16628: broker protection mode inconsistent with the database setting
ORA-16628: broker protection mode inconsistent with the database setting
Cause:
The Data Guard broker protection mode saved in the broker configuration file was inconsistent with the actual database setting.
Action:
Reset the protection mode through the Data Guard broker.
Cause:
The Data Guard broker protection mode saved in the broker configuration file was inconsistent with the actual database setting.
Action:
Reset the protection mode through the Data Guard broker.
ORA-16629: database reports a different protection level from the protection mode
ORA-16629: database reports a different protection level from the protection mode
Cause:
The current database protection level was different from the configured protection mode. This typically was caused by redo transport problems, or the primary database was not open.
Action:
Check the database alert logs and Data Guard broker logs for more details. Also, check the redo transport status. Ensure that one standby database supports the configured protection mode and that the network to that standby database is working properly. Ensure the primary database is open.
Cause:
The current database protection level was different from the configured protection mode. This typically was caused by redo transport problems, or the primary database was not open.
Action:
Check the database alert logs and Data Guard broker logs for more details. Also, check the redo transport status. Ensure that one standby database supports the configured protection mode and that the network to that standby database is working properly. Ensure the primary database is open.
ORA-16630: database property has been deprecated
ORA-16630: database property has been deprecated
Cause:
The property that was specified in the command was deprecated.
Action:
Check the broker documentation to identify a replacement property or SQL command for the deprecated property.
Cause:
The property that was specified in the command was deprecated.
Action:
Check the broker documentation to identify a replacement property or SQL command for the deprecated property.
ORA-16619: condition for fast-start failover is already enabled
ORA-16619: condition for fast-start failover is already enabled
Cause:
The condition specified for fast-start failover was already enabled.
Action:
No action is required. Use the DGMGRL CLI SHOW FAST_START FAILOVER command to see the conditions that are enabled.
Cause:
The condition specified for fast-start failover was already enabled.
Action:
No action is required. Use the DGMGRL CLI SHOW FAST_START FAILOVER command to see the conditions that are enabled.
ORA-16620: one or more databases could not be reached for a delete operation
ORA-16620: one or more databases could not be reached for a delete operation
Cause:
One or more standby databases could not be reached for either a DGMGRL CLI REMOVE DATABASE or a REMOVE CONFIGURATION command.
Action:
This typically indicates a network problem where the standby database is unable to respond to the primary database. In the event of this situation, examine the primary database Data Guard broker log to determine which standby databases could not be reached. For each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, DG_BROKER_START, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database DG_BROKER_CONFIG_FILE[1|2] initialization parameter values and delete them. Then restart the broker by setting DG_BROKER_START to true.
Cause:
One or more standby databases could not be reached for either a DGMGRL CLI REMOVE DATABASE or a REMOVE CONFIGURATION command.
Action:
This typically indicates a network problem where the standby database is unable to respond to the primary database. In the event of this situation, examine the primary database Data Guard broker log to determine which standby databases could not be reached. For each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, DG_BROKER_START, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database DG_BROKER_CONFIG_FILE[1|2] initialization parameter values and delete them. Then restart the broker by setting DG_BROKER_START to true.
ORA-16621: database name for ADD DATABASE must be unique
ORA-16621: database name for ADD DATABASE must be unique
Cause:
An attempt was made to add a database to the broker configuration that already included a database with the specified name. The database names must be unique.
Action:
Verify that a unique name is specified for the new database to be added. Also, the database name must match the DB_UNIQUE_NAME initialization parameter of the database.
Cause:
An attempt was made to add a database to the broker configuration that already included a database with the specified name. The database names must be unique.
Action:
Verify that a unique name is specified for the new database to be added. Also, the database name must match the DB_UNIQUE_NAME initialization parameter of the database.
ORA-16622: two or more broker database objects resolve to the same database
ORA-16622: two or more broker database objects resolve to the same database
Cause:
Multiple database objects referred to the same database.
Action:
Examine the details of all databases in the broker configuration and verify that there are not two or more databases referring to the same database. If two or more database profiles in the broker configuration have the same value for the DGConnectIdentifier database property, either:
- Remove and re-add The erroneously defined database(s) to resolve The ambiguity.
- Ensure that The DGConnectIdentifier database property for each database allows The broker to properly connect to that database.
Cause:
Multiple database objects referred to the same database.
Action:
Examine the details of all databases in the broker configuration and verify that there are not two or more databases referring to the same database. If two or more database profiles in the broker configuration have the same value for the DGConnectIdentifier database property, either:
- Remove and re-add The erroneously defined database(s) to resolve The ambiguity.
- Ensure that The DGConnectIdentifier database property for each database allows The broker to properly connect to that database.
ORA-16623: database detected role change
ORA-16623: database detected role change
Cause:
A successful switchover or failover operation had been completed and was detected during database startup or broker health check. If this database was unavailable during a switchover or failover operation, it may not be a viable standby database for the new primary database and was disabled by the Data Guard broker.
Action:
Connect to the new primary database and examine the broker configuration for databases that were disabled and that may require reinstatement or re-creation.
Cause:
A successful switchover or failover operation had been completed and was detected during database startup or broker health check. If this database was unavailable during a switchover or failover operation, it may not be a viable standby database for the new primary database and was disabled by the Data Guard broker.
Action:
Connect to the new primary database and examine the broker configuration for databases that were disabled and that may require reinstatement or re-creation.
ORA-16624: broker protocol version mismatch detected
ORA-16624: broker protocol version mismatch detected
Cause:
A network protocol version number mismatch was detected. This could happen if the databases in the broker configuration were not running the same version of Oracle. The broker would disable standby databases that were not running the same version of Oracle as the primary database if this situation was detected.
Action:
Examine the version of Oracle installed on all databases in the broker configuration to ensure they are identical. Once all of the databases in the broker configuration are running the same version of Oracle, reenable the standby databases that were disabled.
Cause:
A network protocol version number mismatch was detected. This could happen if the databases in the broker configuration were not running the same version of Oracle. The broker would disable standby databases that were not running the same version of Oracle as the primary database if this situation was detected.
Action:
Examine the version of Oracle installed on all databases in the broker configuration to ensure they are identical. Once all of the databases in the broker configuration are running the same version of Oracle, reenable the standby databases that were disabled.
ORA-16599: Data Guard broker detected a stale configuration
ORA-16599: Data Guard broker detected a stale configuration
Cause:
The Data Guard broker detected a stale configuration during initialization for this database.
Action:
The broker will automatically resolve this situation once the primary database completes its initialization.
Cause:
The Data Guard broker detected a stale configuration during initialization for this database.
Action:
The broker will automatically resolve this situation once the primary database completes its initialization.
ORA-16600: not connected to target standby database for failover
ORA-16600: not connected to target standby database for failover
Cause:
The failover command failed because the client was not connected to the target standby database.
Action:
Explicitly connect to the standby database to be failed over to and retry the failover command.
Cause:
The failover command failed because the client was not connected to the target standby database.
Action:
Explicitly connect to the standby database to be failed over to and retry the failover command.
ORA-16602: database must be disabled to perform this operation
ORA-16602: database must be disabled to perform this operation
Cause:
An attempt was made to edit a database property while the database was enabled.
Action:
Disable the database and retry the command.
Cause:
An attempt was made to edit a database property while the database was enabled.
Action:
Disable the database and retry the command.
ORA-16603: database is part of another Data Guard broker configuration
ORA-16603: database is part of another Data Guard broker configuration
Cause:
The database was part of another Data Guard broker configuration. This could occur if the original configuration was re-created while this database was disconnected from the network or the same database was added to two different Data Guard broker configurations.
Action:
Make sure the database belongs to only one broker configuration. Shut down the broker by setting the DG_BROKER_START initialization parameter to false. Then remove the Data Guard broker configuration files. Finally restart the broker by setting the DG_BROKER_START initialization parameter to true.
Cause:
The database was part of another Data Guard broker configuration. This could occur if the original configuration was re-created while this database was disconnected from the network or the same database was added to two different Data Guard broker configurations.
Action:
Make sure the database belongs to only one broker configuration. Shut down the broker by setting the DG_BROKER_START initialization parameter to false. Then remove the Data Guard broker configuration files. Finally restart the broker by setting the DG_BROKER_START initialization parameter to true.
ORA-16604: operation not allowed on a database that ships redo data
ORA-16604: operation not allowed on a database that ships redo data
Cause:
An attempt was made to delete, disable, or convert a database that ships redo data to another database.
Action:
Ensure that the name of the database to be deleted, disabled, or converted is not specified in another database's RedoSource property.
Cause:
An attempt was made to delete, disable, or convert a database that ships redo data to another database.
Action:
Ensure that the name of the database to be deleted, disabled, or converted is not specified in another database's RedoSource property.
ORA-16606: unable to find property string
ORA-16606: unable to find property "string"
Cause:
The specified property did not exist.
Action:
Specify a valid property name and reissue the request.
Cause:
The specified property did not exist.
Action:
Specify a valid property name and reissue the request.
ORA-16607: one or more databases have failed
ORA-16607: one or more databases have failed
Cause:
A failure was detected for one or more databases in the Data Guard broker configuration.
Action:
Locate the database(s) with a failure status and correct it.
Cause:
A failure was detected for one or more databases in the Data Guard broker configuration.
Action:
Locate the database(s) with a failure status and correct it.
ORA-16608: one or more databases have warnings
ORA-16608: one or more databases have warnings
Cause:
A warning was detected for one or more databases in the Data Guard broker configuration.
Action:
Locate the database(s) with a warning status and correct it.
Cause:
A warning was detected for one or more databases in the Data Guard broker configuration.
Action:
Locate the database(s) with a warning status and correct it.
ORA-16609: database is being disabled
ORA-16609: database is being disabled
Cause:
A command was attempted on a database that was being disabled. For example, attempting to reinstate the old primary database, the database that was the primary database prior to the most recent failover, before it was ready to be reinstated.
Action:
Wait for the Data Guard broker to disable the database and then retry the command.
Cause:
A command was attempted on a database that was being disabled. For example, attempting to reinstate the old primary database, the database that was the primary database prior to the most recent failover, before it was ready to be reinstated.
Action:
Wait for the Data Guard broker to disable the database and then retry the command.
ORA-16610: command string in progress
ORA-16610: command "string" in progress
Cause:
The specified broker command was already running and the command issued could not be completed.
Action:
Wait for the specified command to finish and then retry the command.
Cause:
The specified broker command was already running and the command issued could not be completed.
Action:
Wait for the specified command to finish and then retry the command.
ORA-16611: command aborted at user request
ORA-16611: command aborted at user request
Cause:
The command was aborted at the user's request.
Action:
No action required.
Cause:
The command was aborted at the user's request.
Action:
No action required.
ORA-16612: string value too long for attribute string
ORA-16612: string value too long for attribute "string"
Cause:
The string value for the named attribute was too long.
Action:
Specify a shorter string value.
Cause:
The string value for the named attribute was too long.
Action:
Specify a shorter string value.
ORA-16613: initialization in progress for database
ORA-16613: initialization in progress for database
Cause:
A request was made that required access to the Data Guard broker configuration before the Data Guard broker had completed initialization.
Action:
Wait until the Data Guard broker has completed initialization, then reissue the request.
Cause:
A request was made that required access to the Data Guard broker configuration before the Data Guard broker had completed initialization.
Action:
Wait until the Data Guard broker has completed initialization, then reissue the request.
ORA-16614: Data Guard broker configuration is disabled
ORA-16614: Data Guard broker configuration is disabled
Cause:
An attempt to enable a database failed because the Data Guard broker configuration was disabled.
Action:
Enable the Data Guard broker configuration and issue the DGMGRL CLI SHOW CONFIGURATION command to see if there are any databases that are still disabled. If the database you tried to enable is still disabled, issue the DGMGRL CLI SHOW DATABASE command to check the status of the database. If the database status indicates that the database needs to be reinstated then issue the DGMGRL CLI REINSTATE DATABASE command to reinstate and enable the database. If the database does not require reinstatement then issue the DGMGRL CLI ENABLE DATABASE command to enable the database.
Cause:
An attempt to enable a database failed because the Data Guard broker configuration was disabled.
Action:
Enable the Data Guard broker configuration and issue the DGMGRL CLI SHOW CONFIGURATION command to see if there are any databases that are still disabled. If the database you tried to enable is still disabled, issue the DGMGRL CLI SHOW DATABASE command to check the status of the database. If the database status indicates that the database needs to be reinstated then issue the DGMGRL CLI REINSTATE DATABASE command to reinstate and enable the database. If the database does not require reinstatement then issue the DGMGRL CLI ENABLE DATABASE command to enable the database.
ORA-16617: unknown object identifier specified in request
ORA-16617: unknown object identifier specified in request
Cause:
Object identifier specified in the request was invalid or unknown.
Action:
Verify that a valid object identifier is specified and reissue reissue the request.
Cause:
Object identifier specified in the request was invalid or unknown.
Action:
Verify that a valid object identifier is specified and reissue reissue the request.
ORA-16577: corruption detected in Data Guard configuration file
ORA-16577: corruption detected in Data Guard configuration file
Cause:
The Data Guard broker detected errors while loading the configuration file.
Action:
Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Contact Oracle Support Services.
Cause:
The Data Guard broker detected errors while loading the configuration file.
Action:
Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Contact Oracle Support Services.
ORA-16578: failed to read Data Guard configuration file
ORA-16578: failed to read Data Guard configuration file
Cause:
A failure was encountered while the broker was reading the configuration file on permanent storage.
Action:
Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
Cause:
A failure was encountered while the broker was reading the configuration file on permanent storage.
Action:
Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
ORA-16582: cannot change instance-specific property
ORA-16582: cannot change instance-specific property
Cause:
An attempt was made to change an instance-specific property for a database that had more than one instance.
Action:
Retry the command and identify a specific instance whose property value is to be changed.
Cause:
An attempt was made to change an instance-specific property for a database that had more than one instance.
Action:
Retry the command and identify a specific instance whose property value is to be changed.
ORA-16584: operation cannot be performed on a standby database
ORA-16584: operation cannot be performed on a standby database
Cause:
The database specified for the operation was a standby database, or the operation was attempted on a standby database.
Action:
Check the database type and retry the operation. If the command must be executed on a primary database, connect to the primary database and retry the operation.
Cause:
The database specified for the operation was a standby database, or the operation was attempted on a standby database.
Action:
Check the database type and retry the operation. If the command must be executed on a primary database, connect to the primary database and retry the operation.
ORA-16585: operation cannot be performed on a primary database
ORA-16585: operation cannot be performed on a primary database
Cause:
The database specified for the operation was a primary database, or the operation was attempted on a primary database.
Action:
Check the database type and retry the operation. If the command must be executed on a standby database, connect to a standby database and retry the operation.
Cause:
The database specified for the operation was a primary database, or the operation was attempted on a primary database.
Action:
Check the database type and retry the operation. If the command must be executed on a standby database, connect to a standby database and retry the operation.
ORA-16586: cannot change database property with EDIT INSTANCE command
ORA-16586: cannot change database property with EDIT INSTANCE command
Cause:
An attempt was made to change a database property using an EDIT INSTANCE command instead of an EDIT DATABASE command.
Action:
Use the EDIT DATABASE command to change database properties.
Cause:
An attempt was made to change a database property using an EDIT INSTANCE command instead of an EDIT DATABASE command.
Action:
Use the EDIT DATABASE command to change database properties.
ORA-16587: ambiguous object specified to Data Guard broker
ORA-16587: ambiguous object specified to Data Guard broker
Cause:
An object was specified that the broker could not uniquely distinguish from other objects in the configuration.
Action:
Try to further distinguish the object specified for the operation and reissue the command.
Cause:
An object was specified that the broker could not uniquely distinguish from other objects in the configuration.
Action:
Try to further distinguish the object specified for the operation and reissue the command.
ORA-16589: Data Guard broker detected network transfer error
ORA-16589: Data Guard broker detected network transfer error
Cause:
The Data Guard broker detected an error while transferring data from one database to another. This may happen when:
- The broker detects an inconsistency in The block count of configuration file when The file is transmitted between databases.
- The broker encountered an error when writing The configuration file.
Action:
Contact Oracle Support Services.
Cause:
The Data Guard broker detected an error while transferring data from one database to another. This may happen when:
- The broker detects an inconsistency in The block count of configuration file when The file is transmitted between databases.
- The broker encountered an error when writing The configuration file.
Action:
Contact Oracle Support Services.
ORA-16594: DMON background process is not running
ORA-16594: DMON background process is not running
Cause:
The Data Guard broker background process, DMON, was not running.
Action:
Check the Data Guard broker log and DMON process trace file to determine why the DMON process is not running.
Cause:
The Data Guard broker background process, DMON, was not running.
Action:
Check the Data Guard broker log and DMON process trace file to determine why the DMON process is not running.
ORA-16595: process string failed to terminate
ORA-16595: process string failed to terminate
Cause:
The specified process did not terminate at the request of the Data Guard broker.
Action:
Contact Oracle Support Services.
Cause:
The specified process did not terminate at the request of the Data Guard broker.
Action:
Contact Oracle Support Services.
ORA-16596: database not part of the Data Guard broker configuration
ORA-16596: database not part of the Data Guard broker configuration
Cause:
The specified database is not in the Data Guard broker configuration.
Action:
Retry the command with a database that is in the broker configuration.
Cause:
The specified database is not in the Data Guard broker configuration.
Action:
Retry the command with a database that is in the broker configuration.
ORA-16597: Data Guard broker detects two or more primary databases
ORA-16597: Data Guard broker detects two or more primary databases
Cause:
The Data Guard broker detected two or more primary databases in the broker configuration and could not continue.
Action:
Contact Oracle Support Services.
Cause:
The Data Guard broker detected two or more primary databases in the broker configuration and could not continue.
Action:
Contact Oracle Support Services.
ORA-16598: Data Guard broker detected a mismatch in configuration
ORA-16598: Data Guard broker detected a mismatch in configuration
Cause:
The Data Guard broker detected a significant mismatch while performing configuration membership validation between two or more databases in the broker configuration. This can occur when the primary database has stale broker configuration files.
Action:
Contact Oracle Support Services.
Cause:
The Data Guard broker detected a significant mismatch while performing configuration membership validation between two or more databases in the broker configuration. This can occur when the primary database has stale broker configuration files.
Action:
Contact Oracle Support Services.
ORA-16557: database is already in use
ORA-16557: database is already in use
Cause:
An attempt was made to create a duplicate database in the broker configuration, or to add a duplicate instance (sid) for an existing database in the broker configuration.
Action:
Check the database to be added to ensure there are no duplicates.
Cause:
An attempt was made to create a duplicate database in the broker configuration, or to add a duplicate instance (sid) for an existing database in the broker configuration.
Action:
Check the database to be added to ensure there are no duplicates.
ORA-16558: database specified for switchover is not a standby database
ORA-16558: database specified for switchover is not a standby database
Cause:
An attempt was made to switchover to a database that was not a standby database.
Action:
Locate an enabled standby database and select that database as the target of the switchover.
Cause:
An attempt was made to switchover to a database that was not a standby database.
Action:
Locate an enabled standby database and select that database as the target of the switchover.
ORA-16561: cannot remove an active instance
ORA-16561: cannot remove an active instance
Cause:
The instance to be removed was running.
Action:
Shut down the instance and reissue the REMOVE command.
Cause:
The instance to be removed was running.
Action:
Shut down the instance and reissue the REMOVE command.
ORA-16568: cannot set property string
ORA-16568: cannot set property string
Cause:
The specified property could not be modified because it was either a monitorable property or a property that did not exist.
Action:
Retry the command with a valid configurable property.
Cause:
The specified property could not be modified because it was either a monitorable property or a property that did not exist.
Action:
Retry the command with a valid configurable property.
ORA-16569: Data Guard configuration is not enabled
ORA-16569: Data Guard configuration is not enabled
Cause:
The requested operation required that broker management of the Data Guard configuration must be enabled.
Action:
Enable the Data Guard configuration and reissue the request.
Cause:
The requested operation required that broker management of the Data Guard configuration must be enabled.
Action:
Enable the Data Guard configuration and reissue the request.
ORA-16570: database needs restart
ORA-16570: database needs restart
Cause:
The Data Guard broker operation required this database instance to be shut down and restarted.
Action:
If DGMGRL or Enterprise Manager has not already done so, shut down the Oracle instance and then restart it.
Cause:
The Data Guard broker operation required this database instance to be shut down and restarted.
Action:
If DGMGRL or Enterprise Manager has not already done so, shut down the Oracle instance and then restart it.
ORA-16571: Data Guard configuration file creation failure
ORA-16571: Data Guard configuration file creation failure
Cause:
The Data Guard broker was unable to create the configuration file on permanent storage.
Action:
Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.
Cause:
The Data Guard broker was unable to create the configuration file on permanent storage.
Action:
Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry the operation.
ORA-16572: Data Guard configuration file not found
ORA-16572: Data Guard configuration file not found
Cause:
The Data Guard broker configuration file was either unavailable or did not exist.
Action:
Verify that the configuration file was successfully created. If the DG_BROKER_CONFIG_FILE[1|2] initialization parameters were changed, ensure the file name on disk and the parameter value match, there is space on the device, and the proper permissions are granted. For a RAC database, ensure that these initialization parameters are set to file locations that are shared by all instances of the RAC database.
Cause:
The Data Guard broker configuration file was either unavailable or did not exist.
Action:
Verify that the configuration file was successfully created. If the DG_BROKER_CONFIG_FILE[1|2] initialization parameters were changed, ensure the file name on disk and the parameter value match, there is space on the device, and the proper permissions are granted. For a RAC database, ensure that these initialization parameters are set to file locations that are shared by all instances of the RAC database.
ORA-16573: attempt to change or access configuration file for an enabled broker configuration
ORA-16573: attempt to change or access configuration file for an enabled broker configuration
Cause:
The operation was rejected because the Data Guard broker configuration file was in use. The attempted operation was unsafe while broker management of the configuration was enabled. For example:
- An attempt was made to alter the DG_BROKER_CONFIG_FILE[1|2] initialization parameters while the broker was running.
- Non-broker access (such as DBMS_FILE_TRANSFER) to The configuration files was attempted. See The alert log for additional information.
Action:
Disable the broker configuration and shut down the Data Guard broker, then retry the operation. If the operation includes altering the DG_BROKER_CONFIG_FILE[1|2] initialization parameters, be sure that the new parameter values correctly specify the files at their expected location before reenabling broker management of the configuration.
Cause:
The operation was rejected because the Data Guard broker configuration file was in use. The attempted operation was unsafe while broker management of the configuration was enabled. For example:
- An attempt was made to alter the DG_BROKER_CONFIG_FILE[1|2] initialization parameters while the broker was running.
- Non-broker access (such as DBMS_FILE_TRANSFER) to The configuration files was attempted. See The alert log for additional information.
Action:
Disable the broker configuration and shut down the Data Guard broker, then retry the operation. If the operation includes altering the DG_BROKER_CONFIG_FILE[1|2] initialization parameters, be sure that the new parameter values correctly specify the files at their expected location before reenabling broker management of the configuration.
ORA-16574: switchover disallowed when required databases are shut down
ORA-16574: switchover disallowed when required databases are shut down
Cause:
Switchover failed because either the primary database or the designated standby database were shut down.
Action:
Ensure that the primary and standby databases are running and that primary database is shipping redo data to the designated standby database. Also ensure that that the designated standby database is applying the redo data received from the primary database.
Cause:
Switchover failed because either the primary database or the designated standby database were shut down.
Action:
Ensure that the primary and standby databases are running and that primary database is shipping redo data to the designated standby database. Also ensure that that the designated standby database is applying the redo data received from the primary database.
ORA-16575: request terminated because failover is in progress
ORA-16575: request terminated because failover is in progress
Cause:
This error was returned when the broker terminated a request because it was processing a failover command.
Action:
Wait for failover to complete and then retry the request.
Cause:
This error was returned when the broker terminated a request because it was processing a failover command.
Action:
Wait for failover to complete and then retry the request.
ORA-16576: failed to update Data Guard configuration file
ORA-16576: failed to update Data Guard configuration file
Cause:
A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.
Action:
Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
Cause:
A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.
Action:
Verify space, permissions and file name as indicated by the DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
ORA-16551: short string copied
ORA-16551: short string copied
Cause:
A string property value that did not fill the receive buffer was placed in the receive buffer.
Action:
This is an informational message only.
Cause:
A string property value that did not fill the receive buffer was placed in the receive buffer.
Action:
This is an informational message only.
ORA-16552: error occurred while generating directives for client
ORA-16552: error occurred while generating directives for client
Cause:
The operation could not be completed because the broker required assistance from the client that it was unable to provide because of the accompanying error.
Action:
See the accompanying error message for more information and follow the directions provided in the Action section of that message. Then retry the operation.
Cause:
The operation could not be completed because the broker required assistance from the client that it was unable to provide because of the accompanying error.
Action:
See the accompanying error message for more information and follow the directions provided in the Action section of that message. Then retry the operation.
ORA-16555: database is not active
ORA-16555: database is not active
Cause:
An operation was attempted on a database that was not active. not active.
Action:
Verify that the database is active and retry the operation.
Cause:
An operation was attempted on a database that was not active. not active.
Action:
Verify that the database is active and retry the operation.
ORA-16556: observer version mismatch
ORA-16556: observer version mismatch
Cause:
This version of the observer was incompatible with the version of the specified Oracle database server to which the observer had been connected. This observer client cannot be used to observe the specified Oracle server.
Action:
Use a version of the observer that is compatible with the Oracle database server to be observed.
Cause:
This version of the observer was incompatible with the version of the specified Oracle database server to which the observer had been connected. This observer client cannot be used to observe the specified Oracle server.
Action:
Use a version of the observer that is compatible with the Oracle database server to be observed.
ORA-16534: switchover, failover or convert operation in progress
ORA-16534: switchover, failover or convert operation in progress
Cause:
The Data Guard broker returned this status because a switchover, failover or convert operation was in progress. The broker could not accept new requests until the operation finished.
Action:
Wait until the operation is complete and reissue the request.
Cause:
The Data Guard broker returned this status because a switchover, failover or convert operation was in progress. The broker could not accept new requests until the operation finished.
Action:
Wait until the operation is complete and reissue the request.
ORA-16535: Oracle Restart or Oracle Clusterware prevented completion of broker operation
ORA-16535: Oracle Restart or Oracle Clusterware prevented completion of broker operation
Cause:
The broker could not complete the operation because Oracle Restart (for single instance databases) or Oracle Clusterware (for RAC databases) could not stop services or instances on this database.
Action:
Check the Data Guard broker log file for more information and stop the appropriate services or instances using SRVCTL. Then retry the broker operation.
Cause:
The broker could not complete the operation because Oracle Restart (for single instance databases) or Oracle Clusterware (for RAC databases) could not stop services or instances on this database.
Action:
Check the Data Guard broker log file for more information and stop the appropriate services or instances using SRVCTL. Then retry the broker operation.
ORA-16538: no match on requested item
ORA-16538: no match on requested item
Cause:
The Data Guard broker did not recognize the specified property or state name, or a fast-start failover condition was specified that is not enabled.
Action:
Verify command parameters and reissue the request.
Cause:
The Data Guard broker did not recognize the specified property or state name, or a fast-start failover condition was specified that is not enabled.
Action:
Verify command parameters and reissue the request.
ORA-16540: invalid argument
ORA-16540: invalid argument
Cause:
One of the arguments for the specified request was invalid for the request type.
Action:
Verify arguments and then reissue the request.
Cause:
One of the arguments for the specified request was invalid for the request type.
Action:
Verify arguments and then reissue the request.
ORA-16541: database is not enabled
ORA-16541: database is not enabled
Cause:
The database specified in the request was not enabled.
Action:
Select an enabled database and reissue the request.
Cause:
The database specified in the request was not enabled.
Action:
Select an enabled database and reissue the request.
ORA-16544: modifying DG_BROKER_START requires SID='*' qualifier
ORA-16544: modifying DG_BROKER_START requires SID='*' qualifier
Cause:
The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID='*' qualifier was required in the command.
Action:
Reenter the command using the SID='*' qualifier.
Cause:
The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID='*' qualifier was required in the command.
Action:
Reenter the command using the SID='*' qualifier.
ORA-16547: cannot disable or delete the primary database
ORA-16547: cannot disable or delete the primary database
Cause:
An attempt was made to disable broker management of the primary database or delete the primary database from the broker configuration while the configuration was enabled.
Action:
If you wish to disable broker management of the primary database when the configuration is enabled, you must instead disable broker management of the entire broker configuration. If you wish to delete the primary database from the broker configuration while the configuration is enabled, you must instead delete the entire broker configuration.
Cause:
An attempt was made to disable broker management of the primary database or delete the primary database from the broker configuration while the configuration was enabled.
Action:
If you wish to disable broker management of the primary database when the configuration is enabled, you must instead disable broker management of the entire broker configuration. If you wish to delete the primary database from the broker configuration while the configuration is enabled, you must instead delete the entire broker configuration.
ORA-16548: database not enabled
ORA-16548: database not enabled
Cause:
An attempt was made to modify or query a disabled database. This error is also returned on an attempt to enable, modify, or query a database that the broker has disabled because of a switchover or failover operation. The broker disables its management of a database when it detects that the database needs to be re-created because of a failover or switchover operation.
Action:
If broker management of the database is disabled, enable it and reissue the request.
Cause:
An attempt was made to modify or query a disabled database. This error is also returned on an attempt to enable, modify, or query a database that the broker has disabled because of a switchover or failover operation. The broker disables its management of a database when it detects that the database needs to be re-created because of a failover or switchover operation.
Action:
If broker management of the database is disabled, enable it and reissue the request.
ORA-16549: invalid string
ORA-16549: invalid string
Cause:
An invalid or NULL string value was specified.
Action:
Correct command parameters and retry.
Cause:
An invalid or NULL string value was specified.
Action:
Correct command parameters and retry.
ORA-16550: truncated result
ORA-16550: truncated result
Cause:
A string property value was truncated due to insufficient buffer size.
Action:
Specify a larger receive buffer.
Cause:
A string property value was truncated due to insufficient buffer size.
Action:
Specify a larger receive buffer.
ORA-16513: maximum requests exceeded
ORA-16513: maximum requests exceeded
Cause:
The maximum number of requests that the broker can service on the database instance was exceeded.
Action:
Wait for the broker to complete processing the requests before issuing more requests.
Cause:
The maximum number of requests that the broker can service on the database instance was exceeded.
Action:
Wait for the broker to complete processing the requests before issuing more requests.
ORA-16516: current state is invalid for the attempted operation
ORA-16516: current state is invalid for the attempted operation
Cause:
The broker may have returned this error for either switchover operations or for database state change operations. If this error was returned for a switchover operation, the broker determined that either:
- The databases changing roles are shut down.
- The primary database is not shipping redo data.
- The standby database that will become The primary database is not applying redo data. If this error was returned for database state change operations, The database state specified was invalid.
Action:
If this error is returned when attempting a switchover operation, make sure that:
- The databases changing roles are started.
- The primary database is shipping redo data.
- The standby database is applying redo data. If this error is returned when attempting a database state change operation, make sure a valid database state is specified.
Cause:
The broker may have returned this error for either switchover operations or for database state change operations. If this error was returned for a switchover operation, the broker determined that either:
- The databases changing roles are shut down.
- The primary database is not shipping redo data.
- The standby database that will become The primary database is not applying redo data. If this error was returned for database state change operations, The database state specified was invalid.
Action:
If this error is returned when attempting a switchover operation, make sure that:
- The databases changing roles are started.
- The primary database is shipping redo data.
- The standby database is applying redo data. If this error is returned when attempting a database state change operation, make sure a valid database state is specified.
ORA-16521: operation requires connection to consolidated database root
ORA-16521: operation requires connection to consolidated database root
Cause:
The broker operation required the client to connect to the root of the consolidated database.
Action:
Connect to the root and reissue the broker command.
Cause:
The broker operation required the client to connect to the root of the consolidated database.
Action:
Connect to the root and reissue the broker command.
ORA-16522: configuration is part of GSM pool
ORA-16522: configuration is part of GSM pool
Cause:
The attempted command was not allowed because the configuration was part of a Global Service Management pool.
Action:
Remove the configuration from the GSM pool using GSMCTL. Then, retry the broker command.
Cause:
The attempted command was not allowed because the configuration was part of a Global Service Management pool.
Action:
Remove the configuration from the GSM pool using GSMCTL. Then, retry the broker command.
ORA-16523: operation requires the client to connect to instance string
ORA-16523: operation requires the client to connect to instance "string"
Cause:
The switchover or failover operation required the client to connect to the apply instance of the target database.
Action:
Connect to the indicated instance and reissue the SWITCHOVER or FAILOVER command.
Cause:
The switchover or failover operation required the client to connect to the apply instance of the target database.
Action:
Connect to the indicated instance and reissue the SWITCHOVER or FAILOVER command.
ORA-16524: unsupported command, option, or argument
ORA-16524: unsupported command, option, or argument
Cause:
A command, option, or fast-start failover condition argument was specified that is not supported in this release.
Action:
If trying to enable or disable a fast-start failover condition, try a different Oracle error number. Otherwise, contact Oracle Support Services.
Cause:
A command, option, or fast-start failover condition argument was specified that is not supported in this release.
Action:
If trying to enable or disable a fast-start failover condition, try a different Oracle error number. Otherwise, contact Oracle Support Services.
ORA-16525: the Data Guard broker is not yet available
ORA-16525: the Data Guard broker is not yet available
Cause:
The Data Guard broker process was either not yet started, was initializing, or failed to start.
Action:
If the broker has not been started, set the DG_BROKER_START initialization parameter to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation.
Cause:
The Data Guard broker process was either not yet started, was initializing, or failed to start.
Action:
If the broker has not been started, set the DG_BROKER_START initialization parameter to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation.
ORA-16526: unable to allocate memory to process request
ORA-16526: unable to allocate memory to process request
Cause:
The Data Guard broker was unable to allocate memory for a request.
Action:
Increase the size of the System Global Area (SGA).
Cause:
The Data Guard broker was unable to allocate memory for a request.
Action:
Increase the size of the System Global Area (SGA).
ORA-16527: unable to allocate broker System Global Area (SGA) memory
ORA-16527: unable to allocate broker System Global Area (SGA) memory
Cause:
The Data Guard broker was unable to allocate memory within the System Global Area (SGA).
Action:
Increase the size of the System Global Area (SGA) memory.
Cause:
The Data Guard broker was unable to allocate memory within the System Global Area (SGA).
Action:
Increase the size of the System Global Area (SGA) memory.
ORA-16528: unable to allocate Program Global Area (PGA) memory
ORA-16528: unable to allocate Program Global Area (PGA) memory
Cause:
There was insufficient space in Program Global Area (PGA) to allocate memory.
Action:
Increase process virtual memory.
Cause:
There was insufficient space in Program Global Area (PGA) to allocate memory.
Action:
Increase process virtual memory.
ORA-16530: invalid buffer or length
ORA-16530: invalid buffer or length
Cause:
A NULL buffer or a length of zero was specified.
Action:
Correct the command parameters and retry the command.
Cause:
A NULL buffer or a length of zero was specified.
Action:
Correct the command parameters and retry the command.
ORA-16532: Data Guard broker configuration does not exist
ORA-16532: Data Guard broker configuration does not exist
Cause:
A broker operation was requested that required a broker configuration to already be created.
Action:
Create a Data Guard broker configuration prior to performing other broker operations. If only one instance of a RAC database is reporting this error, ensure that the DG_BROKER_CONFIG_FILE[1|2] initialization parameters are set to file locations that are shared by all instances of the RAC database.
Cause:
A broker operation was requested that required a broker configuration to already be created.
Action:
Create a Data Guard broker configuration prior to performing other broker operations. If only one instance of a RAC database is reporting this error, ensure that the DG_BROKER_CONFIG_FILE[1|2] initialization parameters are set to file locations that are shared by all instances of the RAC database.
ORA-16484: compatibility setting is too low
ORA-16484: compatibility setting is too low
Cause:
The compatibility setting in the redo log transported to this standby database exceeded the current compatibility setting.
Action:
Check the compatibility setting on the primary and standby database, and increase the compatibility setting in the initialization parameter file on the standby database accordingly.
Cause:
The compatibility setting in the redo log transported to this standby database exceeded the current compatibility setting.
Action:
Check the compatibility setting on the primary and standby database, and increase the compatibility setting in the initialization parameter file on the standby database accordingly.
ORA-16485: redo log is already received at destination
ORA-16485: redo log is already received at destination
Cause:
A copy of this redo log was already received at the destination.
Action:
None
Cause:
A copy of this redo log was already received at the destination.
Action:
None
ORA-16486: redo log is rejected by the destination
ORA-16486: redo log is rejected by the destination
Cause:
The destination was not allowed to receive this redo log.
Action:
Ensure the source database is registered at the destination, the destination is up and running, and storage is available.
Cause:
The destination was not allowed to receive this redo log.
Action:
Ensure the source database is registered at the destination, the destination is up and running, and storage is available.
ORA-16487: the destination database is not writable
ORA-16487: the destination database is not writable
Cause:
The destination database was in read-only mode.
Action:
Ensure the destination database is open for write.
Cause:
The destination database was in read-only mode.
Action:
Ensure the destination database is open for write.
ORA-16488: cannot create a bookkeeping entry in database
ORA-16488: cannot create a bookkeeping entry in database
Cause:
The destination database failed to create an entry in the table used to track the redo log.
Action:
Examine the trace file of the Remote File Server (RFS) process. Check and make sure space is available in your database.
Cause:
The destination database failed to create an entry in the table used to track the redo log.
Action:
Examine the trace file of the Remote File Server (RFS) process. Check and make sure space is available in your database.
ORA-16489: cannot register the redo log at the destination database
ORA-16489: cannot register the redo log at the destination database
Cause:
Registering the redo log to the destination database failed.
Action:
Examine the trace file of the Remote File Server (RFS) process. Check and make sure space is available in your database.
Cause:
Registering the redo log to the destination database failed.
Action:
Examine the trace file of the Remote File Server (RFS) process. Check and make sure space is available in your database.
ORA-16501: the Data Guard broker operation failed
ORA-16501: the Data Guard broker operation failed
Cause:
The Data Guard broker operation failed.
Action:
See accompanying messages for details.
Cause:
The Data Guard broker operation failed.
Action:
See accompanying messages for details.
ORA-16502: the Data Guard broker operation succeeded with warnings
ORA-16502: the Data Guard broker operation succeeded with warnings
Cause:
The Data Guard broker operation succeeded with warnings.
Action:
See accompanying messages for details.
Cause:
The Data Guard broker operation succeeded with warnings.
Action:
See accompanying messages for details.
ORA-16503: cannot exceed the maximum number of databases in this configuration
ORA-16503: cannot exceed the maximum number of databases in this configuration
Cause:
The Data Guard broker configuration already contained the maximum number of databases that could be configured and managed by the broker.
Action:
Select and remove an existing database from the broker configuration, then reissue the command to add another database to the configuration. Note that when COMPATIBLE is set lower than 11.2.0.0.0, the broker can configure and manage up to 10 databases. When COMPATIBLE is set to 11.2.0.0.0 or higher, this limit is increased to 31.
Cause:
The Data Guard broker configuration already contained the maximum number of databases that could be configured and managed by the broker.
Action:
Select and remove an existing database from the broker configuration, then reissue the command to add another database to the configuration. Note that when COMPATIBLE is set lower than 11.2.0.0.0, the broker can configure and manage up to 10 databases. When COMPATIBLE is set to 11.2.0.0.0 or higher, this limit is increased to 31.
ORA-16504: the Data Guard configuration already exists
ORA-16504: the Data Guard configuration already exists
Cause:
A request to create a Data Guard configuration was made while connected to a database that is part of an existing configuration.
Action:
To create a new configuration, the existing configuration must be deleted.
Cause:
A request to create a Data Guard configuration was made while connected to a database that is part of an existing configuration.
Action:
To create a new configuration, the existing configuration must be deleted.
ORA-16506: out of memory
ORA-16506: out of memory
Cause:
Process exceeded private or shared memory limits.
Action:
Check for memory leaks, increase system parameters and restart.
Cause:
Process exceeded private or shared memory limits.
Action:
Check for memory leaks, increase system parameters and restart.
ORA-16509: request timed out
ORA-16509: request timed out
Cause:
The Data Guard broker timed out out the request.
Action:
Check the Data Guard broker log file for more information. Ensure that the network connections between the databases are functioning properly and retry the request.
Cause:
The Data Guard broker timed out out the request.
Action:
Check the Data Guard broker log file for more information. Ensure that the network connections between the databases are functioning properly and retry the request.
ORA-16471: cannot convert switchover target string to a primary database
ORA-16471: cannot convert switchover target string to a primary database
Cause:
Switchover failed because the switchover target could not convert to a primary database.
Action:
Check the database role of the switchover target. If the switchover target database role is standby, do one of the following:
- Fix The problem shown in The alert log.
- Issue The remedial ALTER database SWITCHOVER to FORCE command to convert The SWITCHOVER target to a primary database.
- If The problem in The SWITCHOVER target cannot be fixed, Issue The remedial ALTER database SWITCHOVER to FORCE command on The old primary database to convert The old primary database back to a primary database. If The SWITCHOVER target database role is primary, The SWITCHOVER has completed. Open The SWITCHOVER target and startup The old primary database to finish The SWITCHOVER process.
Cause:
Switchover failed because the switchover target could not convert to a primary database.
Action:
Check the database role of the switchover target. If the switchover target database role is standby, do one of the following:
- Fix The problem shown in The alert log.
- Issue The remedial ALTER database SWITCHOVER to
- If The problem in The SWITCHOVER target cannot be fixed, Issue The remedial ALTER database SWITCHOVER to
ORA-16472: failover failed due to data loss
ORA-16472: failover failed due to data loss
Cause:
The database was in MaxAvailability or MaxProtection mode but terminal recovery finished with data loss.
Action:
For a data loss failover, issue ALTER DATABASE ACTIVATE STANDBY DATABASE command.
Cause:
The database was in MaxAvailability or MaxProtection mode but terminal recovery finished with data loss.
Action:
For a data loss failover, issue ALTER DATABASE ACTIVATE STANDBY DATABASE command.
ORA-16473: database is not in limbo
ORA-16473: database is not in limbo
Cause:
The ALTER DATABASE SWITCHOVER TO FORCE command could not proceed because the database was not in limbo state.
Action:
Make sure the SWITCHOVER_STATUS column in V$DATABASE has the value TO PRIMARY or SESSIONS ACTIVE. If needed, start managed standby recovery and reissue the command after the SWITCHOVER_STATUS column value changes to one of the above values.
Cause:
The ALTER DATABASE SWITCHOVER TO
Action:
Make sure the SWITCHOVER_STATUS column in V$DATABASE has the value TO PRIMARY or SESSIONS ACTIVE. If needed, start managed standby recovery and reissue the command after the SWITCHOVER_STATUS column value changes to one of the above values.
ORA-16474: target_db_name not found in the LOG_ARCHIVE_DEST_n parameter
ORA-16474: target_db_name not found in the LOG_ARCHIVE_DEST_n parameter
Cause:
ALTER DATABASE SWITCHOVER TO or ALTER SYSTEM FLUSH REDO TO command failed because the target_db_name was not defined in the LOG_ARCHIVE_DEST_n parameter.
Action:
Make sure the target_db_name is defined in the LOG_ARCHIVE_DEST_n parameter.
Cause:
ALTER DATABASE SWITCHOVER TO
Action:
Make sure the target_db_name is defined in the LOG_ARCHIVE_DEST_n parameter.
ORA-16475: succeeded with warnings, check alert log for more details
ORA-16475: succeeded with warnings, check alert log for more details
Cause:
The ALTER DATABASE SWITCHOVER TO VERIFY command succeeded but with warnings.
Action:
Check alert log for more details.
Cause:
The ALTER DATABASE SWITCHOVER TO
Action:
Check alert log for more details.
ORA-16476: far sync instance does not allow string operation
ORA-16476: far sync instance does not allow string operation
Cause:
The specified operation was invalid on a far sync instance.
Action:
Do not attempt the specified operation on a far sync instance.
Cause:
The specified operation was invalid on a far sync instance.
Action:
Do not attempt the specified operation on a far sync instance.
ORA-16477: destination is being serviced by another viable source
ORA-16477: destination is being serviced by another viable source
Cause:
An attempt was made by a far sync instance to perform gap analysis with a remote destination that already had connectivity with a different viable source of live redo.
Action:
No action is required. This exception code is informational and is used by the far sync instance to remain idle with respect to this destination until it establishes connectivity with the primary database.
Cause:
An attempt was made by a far sync instance to perform gap analysis with a remote destination that already had connectivity with a different viable source of live redo.
Action:
No action is required. This exception code is informational and is used by the far sync instance to remain idle with respect to this destination until it establishes connectivity with the primary database.
ORA-16478: cannot locate far sync instance connect string
ORA-16478: cannot locate far sync instance connect string
Cause:
The connect string for the far sync instance that is flagged as the source of live redo for this database could not be located.
Action:
Define a LOG_ARCHIVE_DEST_n parameter for the far sync instance using the SERVICE attribute to define the connect string for the far sync instance destination. This destination should be set to DEFER using the corresponding LOG_ARCHIVE_DEST_STATE_n parameter. Once the connect string is defined, retry the failover operation. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
Cause:
The connect string for the far sync instance that is flagged as the source of live redo for this database could not be located.
Action:
Define a LOG_ARCHIVE_DEST_n parameter for the far sync instance using the SERVICE attribute to define the connect string for the far sync instance destination. This destination should be set to DEFER using the corresponding LOG_ARCHIVE_DEST_STATE_n parameter. Once the connect string is defined, retry the failover operation. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
ORA-16479: cannot connect to the far sync instance
ORA-16479: cannot connect to the far sync instance
Cause:
An attempt was made to connect to the far sync instance to help facilitate the failover operation but the connection attempt failed.
Action:
Make sure the far sync instance is mounted. Check the alert log and trace files on both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
Cause:
An attempt was made to connect to the far sync instance to help facilitate the failover operation but the connection attempt failed.
Action:
Make sure the far sync instance is mounted. Check the alert log and trace files on both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
ORA-16480: operational error during far sync instance assisted failover
ORA-16480: operational error during far sync instance assisted failover
Cause:
After successfully connecting to the far sync instance, an error was encountered when polling the far sync instance for progress.
Action:
Check the alert log and traces of both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
Cause:
After successfully connecting to the far sync instance, an error was encountered when polling the far sync instance for progress.
Action:
Check the alert log and traces of both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
ORA-16481: destination error during far sync instance assisted failover
ORA-16481: destination error during far sync instance assisted failover
Cause:
After successfully connecting to the far sync instance, an error was encountered when managing the failover target destination on the far sync instance.
Action:
Check the alert log and traces of both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
Cause:
After successfully connecting to the far sync instance, an error was encountered when managing the failover target destination on the far sync instance.
Action:
Check the alert log and traces of both the current database and the far sync instance for further details. Retry the operation if a problem is identified and corrected. Using the FORCE option on the failover command allows the operation to proceed and bypass the far sync instance but bypassing the far sync instance increases the potential for data loss.
ORA-16482: a role transition is in progress
ORA-16482: a role transition is in progress
Cause:
The operation failed because a role transition was in progress.
Action:
None
Cause:
The operation failed because a role transition was in progress.
Action:
None
ORA-16483: unable to set a LOG_ARCHIVE_DEST_n parameter to the switchover target
ORA-16483: unable to set a LOG_ARCHIVE_DEST_n parameter to the switchover target
Cause:
An attempt was made to set a LOG_ARCHIVE_DEST_n parameter to the switchover target failed.
Action:
Manually set a LOG_ARCHIVE_DEST_n parameter to the switchover target.
Cause:
An attempt was made to set a LOG_ARCHIVE_DEST_n parameter to the switchover target failed.
Action:
Manually set a LOG_ARCHIVE_DEST_n parameter to the switchover target.
ORA-16468: error connecting to switchover target string
ORA-16468: error connecting to switchover target string
Cause:
The primary database could not connect to the switchover target.
Action:
Check the alert log for detailed errors.
Cause:
The primary database could not connect to the switchover target.
Action:
Check the alert log for detailed errors.
ORA-16469: switchover target version number is lower than 12
ORA-16469: switchover target version number is lower than 12
Cause:
The switchover target version number was lower than 12.
Action:
Upgrade the switchover target to a higher release.
Cause:
The switchover target version number was lower than 12.
Action:
Upgrade the switchover target to a higher release.
ORA-16470: Redo Apply is not running on switchover target
ORA-16470: Redo Apply is not running on switchover target
Cause:
The switchover target was not running Redo Apply.
Action:
Start Redo Apply on the switchover target and reissue the command.
Cause:
The switchover target was not running Redo Apply.
Action:
Start Redo Apply on the switchover target and reissue the command.
ORA-16459: recovery already beyond standby failover
ORA-16459: recovery already beyond standby failover
Cause:
Redo Apply stopped because it detected that it had proceeded beyond a standby failover operation.
Action:
Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end-of-redo (EOR) logs corresponding to the failover operation from the new primary database and register all these logs at the target database. Restart Redo Apply.
Cause:
Redo Apply stopped because it detected that it had proceeded beyond a standby failover operation.
Action:
Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end-of-redo (EOR) logs corresponding to the failover operation from the new primary database and register all these logs at the target database. Restart Redo Apply.
ORA-16461: database not flashed back or recovered to a consistent point
ORA-16461: database not flashed back or recovered to a consistent point
Cause:
ALTER DATABASE CONVERT TO STANDBY command failed because either the database was not properly flashed back to STANDBY_BECAME_PRIMARY_SCN, or at least one of the online data files was not current.
Action:
Flashback database to STANDBY_BECAME_PRIMARY_SCN and retry the ALTER DATABASE CONVERT TO STANDBY command.
Cause:
ALTER DATABASE CONVERT TO STANDBY command failed because either the database was not properly flashed back to STANDBY_BECAME_PRIMARY_SCN, or at least one of the online data files was not current.
Action:
Flashback database to STANDBY_BECAME_PRIMARY_SCN and retry the ALTER DATABASE CONVERT TO STANDBY command.
ORA-16463: invalid target database name
ORA-16463: invalid target database name
Cause:
ALTER DATABASE FAILOVER TO or ALTER DATABASE SWITCHOVER TO FORCE command failed because the target_db_name was invalid. The target_db_name must be the same as the name of the database on which the SQL command is issued.
Action:
Change the target database name and reissue the command.
Cause:
ALTER DATABASE FAILOVER TO
Action:
Change the target database name and reissue the command.
ORA-16464: operation not allowed
ORA-16464: operation not allowed
Cause:
An attempt was made to issue the ALTER DATABASE FAILOVER TO or the ALTER DATABASE SWITCHOVER TO FORCE command on a database other than a physical standby database.
Action:
Issue the command on a physical standby database.
Cause:
An attempt was made to issue the ALTER DATABASE FAILOVER TO
Action:
Issue the command on a physical standby database.
ORA-16465: operation not allowed
ORA-16465: operation not allowed
Cause:
An attempt was made to issue the ALTER DATABASE SWITCHOVER TO [VERIFY] command on a database other than an open primary database.
Action:
Issue the command on an open primary database.
Cause:
An attempt was made to issue the ALTER DATABASE SWITCHOVER TO
Action:
Issue the command on an open primary database.
ORA-16466: invalid switchover target
ORA-16466: invalid switchover target
Cause:
The switchover target was not a valid, enabled, or active standby database.
Action:
Fix the problem in the switchover target and reissue the command.
Cause:
The switchover target was not a valid, enabled, or active standby database.
Action:
Fix the problem in the switchover target and reissue the command.
ORA-16467: switchover target is not synchronized
ORA-16467: switchover target is not synchronized
Cause:
The switchover target was not synchronized with the primary database.
Action:
Wait until the switchover target is synchronized with the primary database, then reissue the command.
Cause:
The switchover target was not synchronized with the primary database.
Action:
Wait until the switchover target is synchronized with the primary database, then reissue the command.
ORA-16441: Current log string for thread string sequence string is invalid.
ORA-16441: Current log string for thread string sequence string is invalid.
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY failed because the current redo log file was corrupt.
Action:
Restore the current log at the primary database, and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY failed because the current redo log file was corrupt.
Action:
Restore the current log at the primary database, and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
ORA-16442: ALTER SYSTEM FLUSH REDO TO STANDBY succeeded, but some redo has not been applied.
ORA-16442: ALTER SYSTEM FLUSH REDO TO STANDBY succeeded, but some redo has not been applied.
Cause:
The target standby database did not apply all received redo.
Action:
Allow the target standby database to apply all redo and then reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement.
Cause:
The target standby database did not apply all received redo.
Action:
Allow the target standby database to apply all redo and then reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement.
ORA-16443: could not switch out of log string thread string
ORA-16443: could not switch out of log string thread string
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY could not switch out of the current log.
Action:
This can happen if there are one or more errors during archival of the current log at the primary database. Reissue ALTER SYSTEM FLUSH REDO TO STANDBY after resolving the archiving errors.
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY could not switch out of the current log.
Action:
This can happen if there are one or more errors during archival of the current log at the primary database. Reissue ALTER SYSTEM FLUSH REDO TO STANDBY after resolving the archiving errors.
ORA-16444: ALTER SYSTEM FLUSH REDO TO STANDBY failed due to a corrupted control file or online log file.
ORA-16444: ALTER SYSTEM FLUSH REDO TO STANDBY failed due to a corrupted control file or online log file.
Cause:
A flush redo operation discovered SCNs greater than a previously failed flush redo operation.
Action:
This can happen if there are one or more errors that have corrupted the control file or online redo logs. In these cases, flush redo operation is not possible.
Cause:
A flush redo operation discovered SCNs greater than a previously failed flush redo operation.
Action:
This can happen if there are one or more errors that have corrupted the control file or online redo logs. In these cases, flush redo operation is not possible.
ORA-16445: Database has to be mounted and cannot be open
ORA-16445: Database has to be mounted and cannot be open
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY required that the database be mounted, but not opened.
Action:
Mount the database and then reissue the operation.
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY required that the database be mounted, but not opened.
Action:
Mount the database and then reissue the operation.
ORA-16446: Target database was not a standby database
ORA-16446: Target database was not a standby database
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY failed because the target database is not a standby database.
Action:
Reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement and specify a standby database as the target database.
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY failed because the target database is not a standby database.
Action:
Reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement and specify a standby database as the target database.
ORA-16447: Redo apply was not active at the target standby database
ORA-16447: Redo apply was not active at the target standby database
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY failed because redo apply is not active at the target database.
Action:
Start redo apply at the standby database and reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement, or reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement with the NO CONFIRM APPLY clause.
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY failed because redo apply is not active at the target database.
Action:
Start redo apply at the standby database and reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement, or reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement with the NO CONFIRM APPLY clause.
ORA-16448: Primary database corruption has been detected by standby database.
ORA-16448: Primary database corruption has been detected by standby database.
Cause:
The primary database became corrupted.
Action:
Identify the extent of the corruption on both the primary and standby database and take remedial action.
Cause:
The primary database became corrupted.
Action:
Identify the extent of the corruption on both the primary and standby database and take remedial action.
ORA-16449: incomplete redo thread enable operation
ORA-16449: incomplete redo thread enable operation
Cause:
The switchover operation could not continue because it failed to disable a thread that was left in an incomplete thread enable state.
Action:
Check alert log for more details.
Cause:
The switchover operation could not continue because it failed to disable a thread that was left in an incomplete thread enable state.
Action:
Check alert log for more details.
ORA-16451: A remote archival request has timed out.
ORA-16451: A remote archival request has timed out.
Cause:
When opening or closing a database instance, the database may wait for up to 1 minute for pending remote archival requests to be performed before proceeding with the operation. This error was reported because that time limit was exceeded.
Action:
This is an informational message so no action is required.
Cause:
When opening or closing a database instance, the database may wait for up to 1 minute for pending remote archival requests to be performed before proceeding with the operation. This error was reported because that time limit was exceeded.
Action:
This is an informational message so no action is required.
ORA-16455: switchover to standby failed
ORA-16455: switchover to standby failed
Cause:
An attempt to switchover to a physical standby database failed.
Action:
Check alert log for more details. Issue the SHUTDOWN ABORT command on the database before issuing another ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY command.
Cause:
An attempt to switchover to a physical standby database failed.
Action:
Check alert log for more details. Issue the SHUTDOWN ABORT command on the database before issuing another ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY command.
ORA-16456: switchover to standby in progress or completed
ORA-16456: switchover to standby in progress or completed
Cause:
The requested operation was not allowed because a switchover to standby operation was either in progress or had completed.
Action:
Issue the SHUTDOWN ABORT command on the database after switchover operation completes.
Cause:
The requested operation was not allowed because a switchover to standby operation was either in progress or had completed.
Action:
Issue the SHUTDOWN ABORT command on the database after switchover operation completes.
ORA-16426: Recovery requested an incorrect log from which to apply redo data.
ORA-16426: Recovery requested an incorrect log from which to apply redo data.
Cause:
Media recovery selected an incorrect log.
Action:
Verify that the appropriate log has been properly registered and restart media recovery.
Cause:
Media recovery selected an incorrect log.
Action:
Verify that the appropriate log has been properly registered and restart media recovery.
ORA-16427: Redo gap is too large to resolve.
ORA-16427: Redo gap is too large to resolve.
Cause:
The redo transport lag at this database was too large for automatic redo gap detection to take place.
Action:
Re-create this standby database from a current backup copy of the primary database.
Cause:
The redo transport lag at this database was too large for automatic redo gap detection to take place.
Action:
Re-create this standby database from a current backup copy of the primary database.
ORA-16431: cannot expand control file
ORA-16431: cannot expand control file
Cause:
Additional redo log threads were added on the primary database after the standby control file was created.
Action:
Shut down the standby database and replace the control file with a new standby control file from the primary database or change the COMPATIBLE parameter to 10.2.0 or above and restart the standby database.
Cause:
Additional redo log threads were added on the primary database after the standby control file was created.
Action:
Shut down the standby database and replace the control file with a new standby control file from the primary database or change the COMPATIBLE parameter to 10.2.0 or above and restart the standby database.
ORA-16432: inconsistent set of logs applied at a standby database
ORA-16432: inconsistent set of logs applied at a standby database
Cause:
Redo apply stopped because it detected an inconsistency in the progression of the SCNs. If this database is a bystander standby database, this is most likely due to a failover operation in which incompatible logs were applied from the old and new primary databases.
Action:
Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end of redo (EOR) logs corresponding to the failover operation from the new primary and register all these logs at the target database. Restart redo apply.
Cause:
Redo apply stopped because it detected an inconsistency in the progression of the SCNs. If this database is a bystander standby database, this is most likely due to a failover operation in which incompatible logs were applied from the old and new primary databases.
Action:
Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end of redo (EOR) logs corresponding to the failover operation from the new primary and register all these logs at the target database. Restart redo apply.
ORA-16433: The database or pluggable database must be opened in read/write mode.
ORA-16433: The database or pluggable database must be opened in read/write mode.
Cause:
An attempt was made to open the database or pluggable database in read-only mode after an operation that requires the database or pluggable database be opened in read/write mode.
Action:
Open the database in read/write mode. The database can then be opened in read-only mode.
Cause:
An attempt was made to open the database or pluggable database in read-only mode after an operation that requires the database or pluggable database be opened in read/write mode.
Action:
Open the database in read/write mode. The database can then be opened in read-only mode.
ORA-16434: archive log for branch string thread string sequence string cannot be queued
ORA-16434: archive log for branch string thread string sequence string cannot be queued
Cause:
An archive log needed by the standby database to resolve a redo gap was not found on the source database. This is a fatal situation during a switchover or far sync instance assisted failover because the source database waits for the target standby to be clear of all archive log gaps before allowing the operation to proceed. If a redo gap cannot be resolved during these operations, the operation cannot succeed so it must be failed.
Action:
If the specified log is listed in V$ARCHIVED_LOG for the DEST_ID of the local destination on the source database but no longer exists at that location on disk, the archived log can be copied back to that location to allow gap processing to automatically resolve the gap. If the specified log has been purged from V$ARCHIVED_LOG, the archived log can be copied to disk on either the source or destination database and registered using the ALTER DATABASE REGISTER OR REPLACE LOGFILE command.
Cause:
An archive log needed by the standby database to resolve a redo gap was not found on the source database. This is a fatal situation during a switchover or far sync instance assisted failover because the source database waits for the target standby to be clear of all archive log gaps before allowing the operation to proceed. If a redo gap cannot be resolved during these operations, the operation cannot succeed so it must be failed.
Action:
If the specified log is listed in V$ARCHIVED_LOG for the DEST_ID of the local destination on the source database but no longer exists at that location on disk, the archived log can be copied back to that location to allow gap processing to automatically resolve the gap. If the specified log has been purged from V$ARCHIVED_LOG, the archived log can be copied to disk on either the source or destination database and registered using the ALTER DATABASE REGISTER OR REPLACE LOGFILE command.
ORA-16436: ALTER DATABASE ... RECOVER FINISH could not start
ORA-16436: ALTER DATABASE ... RECOVER FINISH could not start
Cause:
ALTER DATABASE ... RECOVER FINISH failed to start because the standby database was missing redo changes below the checkpoint of data files.
Action:
Issue ALTER DATABASE ACTIVATE STANDBY DATABASE command instead.
Cause:
ALTER DATABASE ... RECOVER FINISH failed to start because the standby database was missing redo changes below the checkpoint of data files.
Action:
Issue ALTER DATABASE ACTIVATE STANDBY DATABASE command instead.
ORA-16437: No active coordinator RFS for current operation
ORA-16437: No active coordinator RFS for current operation
Cause:
The coordinator Remote File Server (RFS) for this parallel archival either abnormally terminated or ran down before this subordinate RFS could begin its leg of the operation.
Action:
No explicit user action is required.
Cause:
The coordinator Remote File Server (RFS) for this parallel archival either abnormally terminated or ran down before this subordinate RFS could begin its leg of the operation.
Action:
No explicit user action is required.
ORA-16438: Switchover to primary cannot be executed at this time
ORA-16438: Switchover to primary cannot be executed at this time
Cause:
ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY could not be executed because an incompatible operation such as RMAN restore or flashback was in progress. See the database alert log for details.
Action:
Wait for the incompatible operation to complete. The files that have been flashed back or restored need recovery before you can reissue ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY statement. Start redo apply and verify that the SWITCHOVER_STATUS column of the V$DATABASE view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.
Cause:
ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY could not be executed because an incompatible operation such as RMAN restore or flashback was in progress. See the database alert log for details.
Action:
Wait for the incompatible operation to complete. The files that have been flashed back or restored need recovery before you can reissue ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY statement. Start redo apply and verify that the SWITCHOVER_STATUS column of the V$DATABASE view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.
ORA-16439: Standby not ready to receive redo at this time
ORA-16439: Standby not ready to receive redo at this time
Cause:
A logical standby or down stream capture database was not in a state where it could accept a request to receive redo from another database. This was likely due to the database not being open.
Action:
See the database alert log at the receiving side of the transfer for details of why the database was not ready. If the database was mounted but not open, open it to clear the problem. The initialization parameter LOG_ARCHIVE_DEST_STATE_n at the sending site may need to be set to ENABLE.
Cause:
A logical standby or down stream capture database was not in a state where it could accept a request to receive redo from another database. This was likely due to the database not being open.
Action:
See the database alert log at the receiving side of the transfer for details of why the database was not ready. If the database was mounted but not open, open it to clear the problem. The initialization parameter LOG_ARCHIVE_DEST_STATE_n at the sending site may need to be set to ENABLE.
ORA-16440: Control file is corrupt.
ORA-16440: Control file is corrupt.
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY failed because the control file was corrupt.
Action:
Restore the current control file at the primary database and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
Cause:
ALTER SYSTEM FLUSH REDO TO STANDBY failed because the control file was corrupt.
Action:
Restore the current control file at the primary database and then reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted primary instance.
ORA-16403: shut down in progress - remote connection is not permitted
ORA-16403: shut down in progress - remote connection is not permitted
Cause:
A redo transport session could not be started because the database was shutting down.
Action:
Wait for the remote instance to be restarted, or contact your DBA.
Cause:
A redo transport session could not be started because the database was shutting down.
Action:
Wait for the remote instance to be restarted, or contact your DBA.
ORA-16406: primary and standby database software version mismatch
ORA-16406: primary and standby database software version mismatch
Cause:
The primary and standby databases were not running compatible versions of Oracle server software.
Action:
Install the correct Oracle server software and try again.
Cause:
The primary and standby databases were not running compatible versions of Oracle server software.
Action:
Install the correct Oracle server software and try again.
ORA-16407: An archive log from an earlier redo branch has been rejected
ORA-16407: An archive log from an earlier redo branch has been rejected
Cause:
An archive log from a redo branch that is earlier than the one that the standby database is currently applying was rejected.
Action:
No action is required.
Cause:
An archive log from a redo branch that is earlier than the one that the standby database is currently applying was rejected.
Action:
No action is required.
ORA-16408: An archive log from an incompatible redo branch has been rejected.
ORA-16408: An archive log from an incompatible redo branch has been rejected.
Cause:
An archive log from a redo branch that is incompatible with the one that the standby database is currently applying was rejected.
Action:
No action is required.
Cause:
An archive log from a redo branch that is incompatible with the one that the standby database is currently applying was rejected.
Action:
No action is required.
ORA-16409: archive log switchover reference number mismatch
ORA-16409: archive log switchover reference number mismatch
Cause:
The archive log switchover reference numbers of the primary and standby database did not match. Remote archival of redo log files is not allowed to incompatible standby database instances.
Action:
No action is required.
Cause:
The archive log switchover reference numbers of the primary and standby database did not match. Remote archival of redo log files is not allowed to incompatible standby database instances.
Action:
No action is required.
ORA-16411: TRANSPORT=ONDEMAND is unsupported
ORA-16411: TRANSPORT=ONDEMAND is unsupported
Cause:
The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action:
Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
Cause:
The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action:
Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16412: TRANSPORT=ONDEMAND is unsupported
ORA-16412: TRANSPORT=ONDEMAND is unsupported
Cause:
The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action:
Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
Cause:
The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action:
Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16413: TRANSPORT=ONDEMAND is unsupported
ORA-16413: TRANSPORT=ONDEMAND is unsupported
Cause:
The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action:
Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
Cause:
The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database.
Action:
Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
ORA-16416: No viable stringswitchover targets available
ORA-16416: No viable stringswitchover targets available
Cause:
Switchover failed because no standby databases of the appropriate type were available.
Action:
Check the alert log for errors, correct the problem and retry the switchover.
Cause:
Switchover failed because no standby databases of the appropriate type were available.
Action:
Check the alert log for errors, correct the problem and retry the switchover.
ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required
ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required
Cause:
Activation occurred after recovery from standby redo log files.
Action:
Take a full database backup.
Cause:
Activation occurred after recovery from standby redo log files.
Action:
Take a full database backup.
ORA-16419: Snapshot standby must be converted to a physical standby database.
ORA-16419: Snapshot standby must be converted to a physical standby database.
Cause:
The database was not a physical standby database.
Action:
Convert to physical standby database and retry the operation.
Cause:
The database was not a physical standby database.
Action:
Convert to physical standby database and retry the operation.
ORA-16420: fast-start failover target cannot be converted to snapshot standby
ORA-16420: fast-start failover target cannot be converted to snapshot standby
Cause:
The database chosen for conversion to a snapshot standby was the fast-start failover target standby database.
Action:
Choose another physical standby database and retry the operation.
Cause:
The database chosen for conversion to a snapshot standby was the fast-start failover target standby database.
Action:
Choose another physical standby database and retry the operation.
ORA-16424: RECOVER FINISH cannot complete due to a redo gap.
ORA-16424: RECOVER FINISH cannot complete due to a redo gap.
Cause:
RECOVER FINISH failed because there was a redo gap on the standby database.
Action:
Resolve redo gap or issue ALTER DATABASE ACTIVATE STANDBY DATABASE to perform an immediate failover with some data loss.
Cause:
RECOVER FINISH failed because there was a redo gap on the standby database.
Action:
Resolve redo gap or issue ALTER DATABASE ACTIVATE STANDBY DATABASE to perform an immediate failover with some data loss.
Subscribe to:
Posts (Atom)