ORA-16771: failover to a physical standby database failed

ORA-16771: failover to a physical standby database failed

Cause: In the failover operation, the step of converting the physical standby database to the primary database failed.

Action: Check the alert log and the Data Guard broker log for more details about the error.

ORA-16770: physical standby database not in read-only state

ORA-16770: physical standby database not in read-only state

Cause: All instances in the physical standby database were put into a LOG-APPLY-OFF state instead of READ-ONLY.

Action: Issue the set state command to move the database to READ-ONLY state.

ORA-16769: the physical standby database is open read-only

ORA-16769: the physical standby database is open read-only

Cause: All instances in the physical standby database were put into a read-only state instead of LOG-APPLY-OFF.

Action: Issue the set state command to move the database to LOG-APPLY-OFF state.

ORA-16768: SQL Apply unexpectedly offline

ORA-16768: SQL Apply unexpectedly offline

Cause: SQL Apply was offline when it should be online.

Action: If necessary, start SQL Apply.

ORA-16767: SQL Apply unexpectedly online

ORA-16767: SQL Apply unexpectedly online

Cause: SQL Apply was online when it should be offline.

Action: If necessary, stop SQL Apply.

ORA-16766: Redo Apply unexpectedly offline

ORA-16766: Redo Apply unexpectedly offline

Cause: Redo Apply was offline when it should be online.

Action: If necessary, start Redo Apply.

ORA-16765: Redo Apply is unexpectedly online

ORA-16765: Redo Apply is unexpectedly online

Cause: Redo Apply was online when it should be offline.

Action: If necessary, stop Redo Apply.

ORA-16764: redo transport service to a standby database is offline

ORA-16764: redo transport service to a standby database is offline

Cause: The redo transport service to a standby database was offline instead of online.

Action: Query the StatusReport property of the primary database for more details. If necessary, start the redo transport service.

ORA-16763: redo transport service for a standby database is online

ORA-16763: redo transport service for a standby database is online

Cause: The redo transport service for a standby database was online instead of offline.

Action: Query the StatusReport property of the primary database for more details. If necessary, stop the redo transport service for the database.

ORA-16762: invalid database state

ORA-16762: invalid database state

Cause: Database was not in the intended state.

Action: Determine the reason for invalid state, and reissue the get status request.

ORA-16761: resource guard could not stop SQL Apply

ORA-16761: resource guard could not stop SQL Apply

Cause: The resource guard failed to stop SQL Apply.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16760: resource guard could not start SQL Apply

ORA-16760: resource guard could not start SQL Apply

Cause: The resource guard failed to start SQL Apply.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16759: resource guard unable to start SQL Apply with initial SCN

ORA-16759: resource guard unable to start SQL Apply with initial SCN

Cause: The resource guard failed to start SQL Apply with an initial SCN.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16758: the specified apply instance is not running

ORA-16758: the specified apply instance is not running

Cause: The apply instance specified by the user is not running, so the Data Guard broker cannot move the apply service to that instance.

Action: Start the instance that you wish the apply service to upon and retry the command.

ORA-16757: resource guard could not get property

ORA-16757: resource guard could not get property

Cause: The resource guard failed to get the specified property.

Action: Check the Data Guard broker log for more details.

ORA-16756: resource guard could not open standby database read-only

ORA-16756: resource guard could not open standby database read-only

Cause: The resource guard could not open the standby database read-only.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16755: failed to set initialization parameter

ORA-16755: failed to set initialization parameter

Cause: The ALTER SYSTEM SET or ALTER SYSTEM RESET command issued by the Data Guard broker failed.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16754: resource guard could not activate standby database

ORA-16754: resource guard could not activate standby database

Cause: The resource guard could not activate the standby database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16753: resource guard could not open standby database

ORA-16753: resource guard could not open standby database

Cause: The resource guard could not open the standby database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16752: resource guard could not mount standby database

ORA-16752: resource guard could not mount standby database

Cause: The resource guard could not mount the standby database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16751: resource guard encountered errors in switchover to primary database

ORA-16751: resource guard encountered errors in switchover to primary database

Cause: The resource guard was unable to switch a standby database to a primary database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16750: resource guard encountered errors while activating logical primary database

ORA-16750: resource guard encountered errors while activating logical primary database

Cause: The resource guard could not activate a primary database from a logical standby database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16749: resource guard encountered errors in switchover to logical primary database

ORA-16749: resource guard encountered errors in switchover to logical primary database

Cause: The resource guard was unable to switch a logical standby database to a primary database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16748: resource guard encountered errors during database open

ORA-16748: resource guard encountered errors during database open

Cause: The resource guard could not open the database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16747: logical standby database guard could not be turned on

ORA-16747: logical standby database guard could not be turned on

Cause: The resource guard could not turn on the logical standby database guard.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16746: resource guard encountered errors during database mount

ORA-16746: resource guard encountered errors during database mount

Cause: The resource guard could not mount the database.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16745: unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full

ORA-16745: unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full

Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add the specified DB_UNIQUE_NAME to the list.

Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.

ORA-16744: the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full

ORA-16744: the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full

Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add a new DB_UNIQUE_NAME to the list.

Action: Remove some unused entries in the DG_CONFIG list, then reenable the database.

ORA-16743: the status of redo transport service for standby database string is unknown

ORA-16743: the status of redo transport service for standby database string is unknown

Cause: The status of redo transport to the specified standby database could not be determined.

Action: Check the Data Guard broker log and Oracle alert log for more details.

ORA-16742: the standby database string has exhausted its quota

ORA-16742: the standby database string has exhausted its quota

Cause: The standby database has exhausted its quota for storing archived redo logs.

Action: Remove some archived logs from the standby database or increase its quota.

ORA-16741: the destination parameter of standby database string has incorrect syntax

ORA-16741: the destination parameter of standby database string has incorrect syntax

Cause: The destination defined in the server parameter file of the primary database has incorrect syntax and Data Guard broker failed to update the destination when redo transport services were enabled.

Action: Fix the syntax error in the primary database s server parameter file or remove the entry from the server parameter file. Also Check the values of the redo transport-related properties for the specified standby database.

ORA-16740: redo transport service for standby database string incorrectly set to ALTERNATE

ORA-16740: redo transport service for standby database string incorrectly set to ALTERNATE

Cause: The redo transport service to the standby database is currently set to ALTERNATE when no other destination is set to alternate to this destination.

Action: Reset the database state to turn on redo transport again if necessary.

ORA-16739: redo transport service for standby database string unexpectedly online

ORA-16739: redo transport service for standby database string unexpectedly online

Cause: The redo transport service for the standby database was online instead of offline.

Action: Check the Data Guard broker log for more details. If necessary, stop the redo transport service for the standby database.

ORA-16738: redo tranport service for standby database string unexpectedly offline

ORA-16738: redo tranport service for standby database string unexpectedly offline

Cause: The redo transport service for the standby database was offline instead of online.

Action: Check the Data Guard broker log for more details. If necessary, start the redo transport service.

ORA-16737: the redo transport service for standby database string has an error

ORA-16737: the redo transport service for standby database string has an error

Cause: A communication problem with the standby database caused the redo transport to fail.

Action: Query the LogXptStatus property to see the error message. Check the Data Guard broker log and Oracle alert log for more details.

ORA-16736: unable to find the destination entry of standby database string in V$ARCHIVE_DEST

ORA-16736: unable to find the destination entry of standby database string in V$ARCHIVE_DEST

Cause: Either the standby destination was manually changed or deleted outside the Data Guard broker s control, or no entry was available for Data Guard broker.

Action: Clean up the destination setting, remove the unused ones, and reset the redo transport service.

ORA-16735: error executing dbms_logstdby.unskip_error procedure

ORA-16735: error executing dbms_logstdby.unskip_error procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16734: error executing dbms_logstdby.skip_error procedure

ORA-16734: error executing dbms_logstdby.skip_error procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16733: error executing dbms_logstdby.unskip procedure

ORA-16733: error executing dbms_logstdby.unskip procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16732: error executing dbms_logstdby.skip procedure

ORA-16732: error executing dbms_logstdby.skip procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16731: error executing dbms_logstdby.unskip_txn procedure

ORA-16731: error executing dbms_logstdby.unskip_txn procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16730: error executing dbms_logstdby.skip_txn procedure

ORA-16730: error executing dbms_logstdby.skip_txn procedure

Cause: Logical standby database package may not be installed.

Action: Install logical standby database packages and reissue the request.

ORA-16729: validation of value for property string found string error

ORA-16729: validation of value for property string found string error

Cause: The property value validitation failed due to the error shown.

Action: Check the error message and clear the error.

ORA-16728: consistency check for property string found string error

ORA-16728: consistency check for property string found string error

Cause: The consistency check for the specified property failed due to the error shown.

Action: Check the error message and clear the error.

ORA-16727: resource guard cannot close database

ORA-16727: resource guard cannot close database

Cause: The resource guard could not close the database.

Action: Check if there any active sessions connect to the database, terminate them, then reissue the request.

ORA-16726: the external condition supplied to resource guard is invalid

ORA-16726: the external condition supplied to resource guard is invalid

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16725: the phase supplied to resource guard is invalid

ORA-16725: the phase supplied to resource guard is invalid

Cause: Internal error

Action: Contact Oracle Support Services.

ORA-16724: the intended state for the database has been set to OFFLINE

ORA-16724: the intended state for the database has been set to OFFLINE

Cause: The intended state of the database has been set to offline.

Action: If broker management of the database is currently enabled, set the database s state to online.

ORA-16723: setting AlternateLocation property conflicts with the redo transport setting

ORA-16723: setting AlternateLocation property conflicts with the redo transport setting

Cause: The standby database is not using standby redo logs, and the redo transport service to the standby database is set with a nonzero value of ReopenSecs and a zero value of MaxFailure. In this case, the redo transport service will retry the standby destination indefinitely and never switch to the alternate destination.

Action: Any one of the following actions will solve the problem: (1) add standby redo logs to the standby database; (2) set ReopenSecs property to zero; (3) set MaxFailure property to a nonzero value. After executing one of the above actions, reset the AlternateLocation property.

ORA-16722: unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters

ORA-16722: unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters

Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_ n initialization parameters.

Action: Check the Data Guard broker log and Oracle alert logs for more details.

ORA-16721: unable to set LOG_ARCHIVE_DEST_n initialization parameters

ORA-16721: unable to set LOG_ARCHIVE_DEST_n initialization parameters

Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_n initialization parameters.

Action: Check the Data Guard broker log and Oracle alert logs for more details.

ORA-16720: no LOG_ARCHIVE_DEST_n initialization parameters available

ORA-16720: no LOG_ARCHIVE_DEST_n initialization parameters available

Cause: All LOG_ARCHIVE_DEST_n initialization parameters are in use.

Action: Clear one or more LOG_ARCHIVE_DEST_n initialization parameters so that broker can use them to setup the primary database s redo transport.

ORA-16719: unable to query V$ARCHIVE_DEST fixed view

ORA-16719: unable to query V$ARCHIVE_DEST fixed view

Cause: The broker failed to query the V$ARCHIVE_DEST fixed view.

Action: Test and clear the problem using SQL*Plus.

ORA-16718: failed to locate database object

ORA-16718: failed to locate database object

Cause: The resource guard was unable to locate the database in the broker configuration.

Action: Add the database to the broker configuration and then reissue the request.

ORA-16717: clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed

ORA-16717: clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed

Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed.

Action: Contact Oracle Support Services.

ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed

ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed

Cause: An attempt to clear the LOG_ARCHIVE_DEST parameter failed.

Action: Contact Oracle Support Services.

ORA-16715: redo transport-related property string of standby database string is inconsistent

ORA-16715: redo transport-related property string of standby database string is inconsistent

Cause: The value of the specified redo transport-related configuration property of the given standby database is inconsistent with the primary database s redo transport service setting. This may be caused by changing an initialization parameter that corresponds to a configuration property.

Action: Query property InconsistentLogXptProps on the primary database to determine the inconsistent values. Reset the property on the standby database to make it consistent with the primary database s redo transport setting.

ORA-16714: the value of property string is inconsistent with the database setting

ORA-16714: the value of property string is inconsistent with the database setting

Cause: The value of the specified configuration property is inconsistent with database in-memory settings or server parameter file settings. This may be caused by changing an initialization parameter that corresponds to a configuration property.

Action: Query property InconsistentProperties on the database to determine the inconsistent values. Reset the property to make it consistent with the database setting.

ORA-16713: the resource guard timed out while servicing the request

ORA-16713: the resource guard timed out while servicing the request

Cause: The resource guard timed out while servicing the request.

Action: Verify that the operation is valid for the database and then reissue the request.

ORA-16712: the resource handle is invalid

ORA-16712: the resource handle is invalid

Cause: Internal error

Action: Contact Oracle Support Services.