LISTE CODE ERREURS ORACLE.

 

ORA-16700	ORA-16700: the standby database has diverged from the primary database
Cause	The primary database may have been flashed back or restored from a backup set and then reopened with the RESETLOGS option.
Action	Re-create the standby database from the primary database or flash back the standby database to the same point the primary database had been flashed back to.

 

ORA-16701	ORA-16701: generic resource guard request failed
Cause	Request to modify or query the resource failed.
Action	Check the Data Guard broker log for the reason for the failure, and reissue the request.

 

ORA-16702	ORA-16702: generic resource guard warning
Cause	A request to modify or query the resource resulted in a warning.
Action	Check the Data Guard broker log for the reason for the warning, and if necessary reissue the request.

 

ORA-16703	ORA-16703: cannot set property while the database is enabled
Cause	An attempt was made to change a database property while the database was enabled.
Action	Disable broker management of the database first, then update the property and reenable the database.

 

ORA-16704	ORA-16704: cannot modify a read-only property
Cause	An attempt was made to change a read-only property.
Action	The property is controlled internally by the Data Guard broker and cannot be modified.

 

ORA-16705	ORA-16705: internal error in resource guard
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16706	ORA-16706: no resource guard is available
Cause	No resource guard is available to service the request.
Action	Contact Oracle Support Services.

 

ORA-16707	ORA-16707: the value of the property string is invalid, valid values are string
Cause	An invalid property value was entered while broker management of the database was disabled.
Action	Reset the value to a correct one.

 

ORA-16708	ORA-16708: the state supplied to resource guard is invalid
Cause	The state name specified is invalid for the database.
Action	Check the state name and reissue the request.

 

ORA-16709	ORA-16709: standby archived log location settings conflict with flash recovery area
Cause	The flash recovery area was already set up on the standby database for storing incoming archived logs from the primary database. In this case, the StandbyArchiveLocation and AlternateLocation properties should not be used for setting up a standby archived log location. The Data Guard broker raised this error because it detected one of the following: (1) the user attempted to use the StandbyArchiveLocation or AlternateLocation properties to set up a standby archived log location; (2) On the standby database, a local destination corresponding to the StandbyArchiveLocation or AlternateLocation property was still set up to store archived logs from the primary database.
Action	If you get this error when trying to set property StandbyArchiveLocation or AlternateLocation (case (1) above), avoid setting these properties. If you get this error after a broker health check (case (2) above), reenable the standby database to clear the error.

 

ORA-16710	ORA-16710: the resource guard is out of memory
Cause	The resource guard was unable to allocate memory while trying to service a request.
Action	Disable broker management of the configuration, shut down Oracle, increase SGA size, and restart.

 

ORA-16711	ORA-16711: the resource guard index is out of bounds
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16712	ORA-16712: the resource handle is invalid
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16713	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-16714	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-16715	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-16716	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-16717	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-16718	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-16719	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-16720	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-16721	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-16722	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-16723	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-16724	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-16725	ORA-16725: the phase supplied to resource guard is invalid
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16726	ORA-16726: the external condition supplied to resource guard is invalid
Cause	Internal error
Action	Contact Oracle Support Services.

 

ORA-16727	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-16728	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-16729	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-16730	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-16731	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-16732	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-16733	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-16734	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-16735	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-16736	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-16737	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-16738	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-16739	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-16740	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-16741	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-16742	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-16743	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-16744	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-16745	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-16746	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-16747	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-16748	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-16749	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-16750	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-16751	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-16752	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-16753	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-16754	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-16755	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-16756	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-16757	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-16758	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-16759	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-16760	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-16761	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-16762	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-16763	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-16764	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-16765	ORA-16765: Redo Apply is unexpectedly online
Cause	Redo Apply was online when it should be offline.
Action	If necessary, stop Redo Apply.

 

ORA-16766	ORA-16766: Redo Apply unexpectedly offline
Cause	Redo Apply was offline when it should be online.
Action	If necessary, start Redo Apply.

 

ORA-16767	ORA-16767: SQL Apply unexpectedly online
Cause	SQL Apply was online when it should be offline.
Action	If necessary, stop SQL Apply.

 

ORA-16768	ORA-16768: SQL Apply unexpectedly offline
Cause	SQL Apply was offline when it should be online.
Action	If necessary, start SQL Apply.

 

ORA-16769	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-16770	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-16771	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-16772	ORA-16772: error switching over between primary and standby databases
Cause	There was an error during switchover of primary and standby databases.
Action	Check the Data Guard broker log and Oracle alert log for more details.

 

ORA-16773	ORA-16773: error starting Redo Apply
Cause	There was an error starting Redo Apply on a physical standby database.
Action	Check the Data Guard broker log and Oracle alert log for more details.

 

ORA-16774	ORA-16774: error stopping Redo Apply
Cause	There was an error stopping Redo Apply on a physical standby database.
Action	Check the Data Guard broker log and Oracle alert log for more details.

 

ORA-16775	ORA-16775: target standby database in broker operation has potential data loss
Cause	The target standby database in the broker operation did not have all the redo logs from the primary database. The switchover or protection mode upgrade to maximum protection could not be performed.
Action	Query the SendQEntries monitorable property on the primary database to see which redo logs are missing. Confirm that the redo transport service on the primary database is functioning correctly by checking its status using the StatusReport monitorable property. Perform log switches on the primary database in order to activate the redo log gap fetching mechanism. Once all redo logs are available on the target standby database, reissue the broker command.

 

ORA-16776	ORA-16776: health check of the redo transport service failed
Cause	Due to some internal failure, the database resource guard could not complete the health check of the redo transport service.
Action	Check the Data Guard broker log and Oracle alert log for more details.

 

ORA-16777	ORA-16777: unable to find the destination entry of a standby database in V$ARCHIVE_DEST
Cause	Either a destination was manually deleted or no entry was available for Data Guard.
Action	Check the Data Guard broker log and the Oracle alert log for more details. The redo transport service may need to be reset.

 

ORA-16778	ORA-16778: redo transport error for one or more databases
Cause	The redo transport service was unable to send redo data to one or more standby databases.
Action	Check the Data Guard broker log and Oracle alert log for more details. Query the LogXptStatus property to see the errors.

 

ORA-16779	ORA-16779: the destination parameter of a database is set incorrectly
Cause	The destination was defined in the LOG_ARCHIVE_DEST_n server parameter file with incorrect syntax. The Data Guard broker failed to update the destination when the redo transport was turned on.
Action	Check the Data Guard broker log to see which database has the problem. Fix the syntax error in the server parameter file or remove the entry from the server parameter file. Check if the syntax of the redo transport-related properties are correct.

 

ORA-16780	ORA-16780: a database has exhausted its archived redo log storage quota
Cause	A database has exhausted its quota for storing archived redo logs.
Action	Check the Data Guard broker log to see which database has the problem. Remove some archived logs at the standby database or increase its quota.

 

ORA-16781	ORA-16781: the status of redo transport service for a database is unknown
Cause	The redo transport service status to a standby database could not be determined.
Action	Check the Data Guard broker log and Oracle alert log for more details.

 

ORA-16782	ORA-16782: instance not open for read and write access
Cause	An instance was left in a mounted mode and was not open for read and write access.
Action	Query the StatusReport property for more details. Open the instance manually or by reenabling the database through the Data Guard broker.

 

ORA-16783	ORA-16783: instance string not open for read and write access
Cause	The instance was left in a mounted mode and was not open for read and write access.
Action	Open the instance manually or by reenabling the database through the Data Guard broker.

 

ORA-16784	ORA-16784: the database name in Dependency property is incorrect
Cause	The database name, which should be the value of the DB_UNIQUE_NAME initialization parameter, specified in property Dependency is incorrect.
Action	Reset the Dependency property to the correct name of the database.

 

ORA-16785	ORA-16785: the database is not in ARCHIVELOG mode
Cause	The database is in NOARCHIVELOG mode, when it is either a primary database or a standby database that is being switched over to be a primary database.
Action	Reset the database to ARCHIVELOG mode by issuing ALTER DATABASE ARCHIVELOG command.

 

ORA-16786	ORA-16786: resource guard cannot access Data Guard broker metadata
Cause	The Data Guard broker configuration files did not exist or for some other reason the resource guard could not access the Data Guard broker configuration metadata.
Action	Check the Data Guard broker log for more details.

 

ORA-16788	ORA-16788: unable to set one or more database configuration property values
Cause	This situation occurs when the database resource guard attempted to set database configuration property values into the database by issuing "ALTER SYSTEM" or "ALTER DATABASE" commands. Typical causes of this error are: a) The values of redo transport-related properties have syntax errors; b) The Value of LogArchiveTrace is out of range; c) Database initialization parameter STANDBY_FILE_MANAGEMENT cannot be set to AUTO because the database compatability is not set to 9.0.0.0.0 or higher.
Action	Check the Data Guard broker log to see which property has the problem and reset the property correctly.

 

ORA-16789	ORA-16789: missing standby redo logs
Cause	Standby redo logs are missing and are needed for SYNC and ASYNC log transport modes.
Action	Check the Data Guard documentation to see how to create standby redo logs.

 

ORA-16790	ORA-16790: the value of the configurable property is invalid
Cause	User entered an invalid property value.
Action	Reset the property to a correct value.

 

ORA-16791	ORA-16791: unable to check the existence of the standby redo logs
Cause	The database may not be mounted, or the query of V$STANDBY_LOG failed.
Action	Bring the database to the mounted state and then query V$STANDBY_LOG to see if the problem has been corrected. Then retry the operation.

 

ORA-16792	ORA-16792: configuration property value is inconsistent with database setting
Cause	The values of one or more configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by altering initialization parameters directly instead of altering property values using Data Guard broker.
Action	Query property the InconsistentProperties on the database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configuration property settings to be propagated to to the initialization parameters.

 

ORA-16793	ORA-16793: logical standby database guard is unexpectedly off
Cause	The logical standby database guard was unexpectedly turned off.
Action	Issue the ALTER DATABASE GUARD ALL command to turn the guard on and verify that Data Guard health check error/warning is cleared.

 

ORA-16794	ORA-16794: database guard is on for primary database
Cause	The database guard was turned on for the primary database.
Action	Issue the ALTER DATABASE GUARD NONE to turn off the guard and verify that Data Guard health check error/warning is cleared.

 

ORA-16795	ORA-16795: database resource guard detects that database re-creation is required
Cause	In the act of failover or switchover, the database resource guard may have detected that re-creation of the database is necessary. This occurs when the database resource guard recognizes a situation in which the database in question cannot be a viable standby database for the new primary database. Until this error status is resolved for this database, information about this database and the broker configuration to which it belongs is unavailable to a broker client that is connected to this database. Therefore, all commands directed by that client to this database cannot be completed.
Action	Re-create (or flash back) the standby database. Connect to the primary database in the broker configuration and reenable broker management of that database. At this point you may connect to that standby database and resume issuing client commands. Alternatively, many client commands that cannot be completed at the standby database when in this error state can be completed successfully when issued to the primary database. In this case, simply reconnect to the primary database and retry the command.

 

ORA-16796	ORA-16796: one or more properties could not be imported from the database
Cause	The broker was unable to import property values for the database being added to the broker configuration. This error indicates:
Action	Remove the database from the configuration using the REMOVE CONFIGURATION or REMOVE DATABASE command. Make sure that the database to be added has at least one instance running and that the net-service-name provides access to the running instance. Then reissue the CREATE CONFIGURATION or ADD DATABASE command.

 

ORA-16797	ORA-16797: database is not using a server parameter file
Cause	The database is not using a server parameter file or the resource guard was unable to access the server parameter file.
Action	Issue CREATE SPFILE=".." FROM PFILE="..." command to create a server parameter file and then restart the database to use it.

 

ORA-16798	ORA-16798: unable to complete terminal recovery on the standby database
Cause	Terminal recovery on the standby database failed during the failover operation.
Action	Check Data Guard broker log and alert logs to see more details on the reason of the failure.

 

ORA-16799	ORA-16799: Redo Apply is offline
Cause	Either the Data Guard broker metadata indicates that Redo Apply is turned off, or the recovery process, MRP0, is not running. In either of the cases, Redo Apply-related properties cannot be set.
Action	Turn on Redo Apply through Data Guard broker and reissue the command to set a Redo Apply-related property.