{"id":1950,"date":"2016-05-05T11:33:57","date_gmt":"2016-05-05T08:33:57","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=1950"},"modified":"2016-10-26T11:35:15","modified_gmt":"2016-10-26T08:35:15","slug":"oracle-11g-error-codes-and-solution-suggestions-from-ora-16700-to-ora-16800","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-11g-error-codes-and-solution-suggestions-from-ora-16700-to-ora-16800\/","title":{"rendered":"Oracle 11g Error Codes and Solution Suggestions from ORA-16700 to ORA-16800"},"content":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-16700 to ORA-16800<\/strong><\/p>\n

\n
ORA-16700: the standby database has diverged from the primary database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The primary database may have been flashed back or restored from a backup set and then reopened with the RESETLOGS option.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Re-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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16701: Data Guard broker command failed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Command to modify or query the database failed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log for the reason for the failure, and reissue the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16702: Data Guard broker command warning<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A command to modify or query the database resulted in a warning.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log for the warning and, if necessary, reissue the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16703: cannot set property while the database is enabled<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to change a database property while the database was enabled.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Disable the database first, update the property and then, reenable the database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16706: Data Guard broker worker process not available<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker worker process was not available to service the request.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16707: the value of the property\u00a0string<\/i>\u00a0is invalid, valid values are\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An invalid property value was specified while broker management of the database was disabled.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Reset the property to a valid value.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16708: the state supplied to broker is invalid<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The state name specified was invalid for the database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the state name and reissue the request.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16709: standby archived log location settings conflict with database recovery area<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The StandbyArchiveLocation or AlternateLocation property was set to USE_DB_RECOVERY_FILE_DEST, but the initialization parameter DB_RECOVERY_FILE_DEST did not specify a valid destination.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use a value other than USE_DB_RECOVERY_FILE_DEST for StandbyArchiveLocation or AlternateLocation, or set up a valid database recovery area by setting DB_RECOVERY_FILE_DEST to a valid destination.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16710: snapshot standby database should be converted back to a physical standby database as soon as possible<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A failover causes this snapshot standby database to enter a state that requires it to be re-created if another failover occurs before it is converted back to a physical standby database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Reenable the snapshot standby database if it is disabled and convert it back to a physical standby database as soon as possible because the snapshot standby database will have to be re-created if another failover occurs while it is in this state.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16713: the Data Guard broker command timed out<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker timed out the command.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify that the command is valid for the database and then retry the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16714: the value of property\u00a0string<\/i>\u00a0is inconsistent with the database setting<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The value of the specified configuration property was 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Query the InconsistentProperties property on the database to determine the which properties are set inconsistently. Reset the properties to make them with the database settings.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16715: redo transport-related property\u00a0string<\/i>\u00a0of standby database “string<\/i>” is inconsistent<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The value of the specified redo transport-related configuration property of the given standby database was inconsistent with the primary database redo transport service setting. This may be caused by changing an initialization parameter that corresponds to a configuration property.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Query the InconsistentLogXptProps property on the primary database to determine which redo transport properties are set inconsistently Reset the properties on the standby database to make them consistent with the primary database redo transport settings.<\/span><\/span><\/span><\/dd>\n

<\/p>\n

<\/a><\/a>ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt to clear the LOG_ARCHIVE_DEST parameter failed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16717: clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16718: failed to locate database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker was unable to locate the database in the broker configuration.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Add the database to the broker configuration and then reissue the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16719: unable to query V$ARCHIVE_DEST fixed view<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The broker failed to query the V$ARCHIVE_DEST fixed view.”<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Test and clear the problem using SQL*Plus.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16720: no LOG_ARCHIVE_DEST_n initialization parameters available<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0All LOG_ARCHIVE_DEST_n initialization parameters were in use.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Clear one or more LOG_ARCHIVE_DEST_n initialization parameters so that broker can use them to set up the primary database redo transport.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16721: unable to set LOG_ARCHIVE_DEST_n initialization parameters<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The broker was unable to set one or more LOG_ARCHIVE_DEST_n initialization parameters.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert logs for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16722: unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_n initialization parameters.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert logs for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16723: setting AlternateLocation property conflicts with the redo transport setting<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The standby database was not using standby redo logs, and the redo transport service to the standby database is set to a nonzero value for the ReopenSecs property and a value of zero for the MaxFailure property. In this case, the redo transport service will attempt to send redo data to the standby database indefinitely and never switch to the alternate destination.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Any one of the following actions will solve the problem:<\/span><\/span><\/span><\/dd>\n
– add standby redo logs to the standby database.<\/span><\/span><\/span><\/dd>\n
– set ReopenSecs property to zero.<\/span><\/span><\/span><\/dd>\n
– set MaxFailure property to a nonzero value. After performing one of the above actions, reset the standby database AlternateLocation property.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16724: cannot resolve gap for one or more standby databases<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The primary database could not resolve a gap request from one or more standby databases.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0To see which standby database has an unresolvable gap, check the status of the primary database using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. Copy the missing archived log files from either backups or from another database in the configuration that has the files to the standby database that is missing the files.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16727: cannot close database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker could not close the database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Terminate any active sessions connected to the database and then reissue the request.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16728: consistency check for property\u00a0string<\/i>\u00a0found\u00a0string<\/i>\u00a0error<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The consistency check for the specified property failed due to the error shown.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the error message and clear the error.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16729: validation of value for property\u00a0string<\/i>\u00a0found\u00a0string<\/i>\u00a0error<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The property value validation failed due to the error shown.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the error message and clear the error.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16730: error executing DBMS_LOGSTDBY.SKIP_TXN procedure<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby database package may not be installed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Install logical standby database packages and reissue the request.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16731: error executing DBMS_LOGSTDBY.UNSKIP_TXN procedure<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby database package may not be installed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Install logical standby database packages and reissue the request.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16732: error executing DBMS_LOGSTDBY.SKIP procedure<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby database package may not be installed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Install logical standby database packages and reissue the request.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16733: error executing DBMS_LOGSTDBY.UNSKIP procedure<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby database package may not be installed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Install logical standby database packages and reissue the request.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16734: error executing DBMS_LOGSTDBY.SKIP_ERROR procedure<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby database package may not be installed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Install logical standby database packages and reissue the request.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16735: error executing DBMS_LOGSTDBY.UNSKIP_ERROR procedure<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby database package may not be installed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Install logical standby database packages and reissue the request.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16736: unable to find the destination entry of standby database “string<\/i>” in V$ARCHIVE_DEST<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Either the standby destination was manually changed or deleted outside of Data Guard broker, or no entry was available for the Data Guard broker to use.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Clean up the destination setting, remove the unused settings, and reset the redo transport service.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16737: the redo transport service for standby database “string<\/i>” has an error<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A communication problem with the standby database caused the redo transport to fail.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Query the LogXptStatus property to see the error message. Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16738: redo transport service for database “string<\/i>” is not running<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The redo transport service for the specified standby database was not running.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and\/or the alert log for more details. If necessary, start the redo transport service for the standby database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16739: redo transport service for standby database “string<\/i>” is running<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The redo transport service for the standby database was running.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log for more details. If necessary, stop the redo transport service for the standby database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16740: redo transport service for standby database “string<\/i>” incorrectly set to ALTERNATE<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The redo transport service to the standby database was set to ALTERNATE when no other destination was set to alternate to this destination.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Reenable the standby database or the entire configuration to allow the configuration property settings to be propagated to the initialization parameters.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16741: the destination parameter of standby database “string<\/i>” has incorrect syntax<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The destination defined in the server parameter file of the primary database had incorrect syntax and Data Guard broker failed to update the destination when redo transport services were enabled.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Fix the syntax error in the primary database 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16742: the standby database “string<\/i>” has exhausted its quota<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The standby database exhausted its quota for storing archived redo logs.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Remove some archived redo logs from the standby database or increase its quota.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16743: cannot determine status of redo transport service for standby database “string<\/i>“<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The status of redo transport to the specified standby database could not be determined.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16744: the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Remove some unused entries in the DG_CONFIG list, then reenable the database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16745: unable to add DB_UNIQUE_NAME “string<\/i>” into the DG_CONFIG list because it is full<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Remove some unused entries in the DG_CONFIG list, then reenable the database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16746: Data Guard broker cannot mount the database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to mount the database.”<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16747: logical standby database guard could not be turned on<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker could not turn on the logical standby database guard.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16748: Data Guard broker cannot open the primary database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to open the primary database” the database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16749: switchover to logical standby database failed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to switch a logical standby database over to a primary database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16750: failed to activate logical standby database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to activate a logical standby database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16751: failed to switchover to physical standby database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to switch a physical standby database over to a primary database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16753: Data Guard broker cannot open standby database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to open the standby database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16754: failed to activate physical standby database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to activate the physical standby database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16755: failed to set initialization parameter<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to set an initialization parameter using either the ALTER SYSTEM SET or ALTER SYSTEM RESET command.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16757: unable to get this property’s value<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to get the value for the specified property, possibly because the specified property’s value is not available for the current database role.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If the specified property’s value is not available for the database’s current role, please specify this property for a database for which it is available. Otherwise, check the Data Guard broker log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16758: the specified apply instance is not running<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker could not start apply services on the specified instance because that instance was not running.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Start the instance and then retry the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16759: cannot start SQL Apply with initial SCN<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to start SQL Apply with an initial SCN.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16760: cannot start SQL Apply<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to start SQL Apply.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16761: cannot stop SQL Apply<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to stop SQL Apply.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16762: invalid database state<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Database was not in the intended state.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Determine the reason why the database is not running in the intended state and reissue the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16763: redo transport service for a standby database is running<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The redo transport service for a standby database was running.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0For more details, check the status of the primary database using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. If necessary, stop the redo transport service to the standby database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16764: redo transport service to a standby database is not running<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The redo transport service to a standby database was not running.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0For more details, check the status of the primary database using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. If necessary, start the redo transport service to the standby database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16765: Redo Apply is running<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Redo Apply was running when it should have been stopped.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If necessary, stop Redo Apply.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16766: Redo Apply is stopped<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Redo Apply was stopped when it should have been running.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the alert log to see why Redo Apply terminated, correct any problems that may exist, and restart Redo Apply by setting the physical standby database state to APPLY-ON.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16767: SQL Apply is running<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0SQL Apply was running when it should have been stopped.”<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If necessary, stop SQL Apply.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16768: SQL Apply is stopped<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0SQL Apply was stopped when it should have been running.”<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the alert log to see why SQL Apply terminated, correct any problems that may exist, and restart SQL Apply by setting the logical standby database state to APPLY-ON.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16769: the physical standby database is open read-only<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0All instances in the physical standby database were put into a read-only state instead of APPLY-OFF.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Issue the EDIT DATABASE SET STATE command to set the database to the APPLY-OFF state.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16770: Redo Apply not started since physical standby database is opening<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Redo Apply services could not be started on the physical standby database because it was being opened. The Data Guard broker will start Redo Apply services once the physical standby database has been opened.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16771: failover to a physical standby database failed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker encountered errors when converting a physical standby database to a primary database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and the Oracle alert log for more details about the error.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16772: switchover to a standby database failed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker encountered errors when switching over to the specified standby database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16773: cannot start Redo Apply<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to start Redo Apply.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details. If the database is already open, the broker will not start Redo Apply if the Active Data Guard option is not enabled.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16774: cannot stop Redo Apply<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker failed to stop Redo Apply.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16775: target standby database in broker operation has potential data loss<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The target standby database specified for the broker operation did not have all the redo data from the primary database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Confirm that the redo transport service on the primary database is functioning correctly by checking its status using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. Reissue the broker command once all redo data is available on the target standby database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16776: health check of the redo transport service failed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker could not complete the health check for the redo transport service.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16777: unable to find the destination entry of a standby database in V$ARCHIVE_DEST<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Either a destination was manually deleted or no entry was available for Data Guard.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and the Oracle alert log for more details. The redo transport service may need to be reset.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16778: redo transport error for one or more databases<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The redo transport service was unable to send redo data to one or more standby databases.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details. Query the LogXptStatus property to see the errors.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16779: the destination parameter of a database is set incorrectly<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16780: a database has exhausted its archived redo log storage quota<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A database has exhausted its quota for storing archived redo logs.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log to see which database has the problem. Remove some archived logs at the standby database or increase its quota.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16781: cannot determine status of redo transport service for standby database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The status of redo transport to the specified standby database could not be determined.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and Oracle alert log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16782: instance not open for read and write access<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database was mounted on an instance but not opened for read and write access.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0For more details, check the status of the database using either Enterprise Manager or the DGMGRL CLI SHOW DATABASE command. If possible, open the instance manually.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16783: cannot resolve gap for database\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The primary database could not resolve a gap request from the specified standby database(s).<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Copy the missing archived redo log files from either backups or from another database in the configuration that has the files to the standby database(s) missing the files.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16784: database name specified by Dependency property is incorrect<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database name, that should be the value of the DB_UNIQUE_NAME initialization parameter, specified in the Dependency property was incorrect.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Reset the Dependency property to the correct name of the database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16785: the database is in NOARCHIVELOG mode<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database was in NOARCHIVELOG mode when it was either a primary database or when it was a standby database that was being switched over to be a primary database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Set the database to ARCHIVELOG mode by issuing the ALTER DATABASE ARCHIVELOG command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16786: unable to access Data Guard broker configuration files<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The Data Guard broker configuration files did not exist or or could not be accessed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log for more details.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16788: unable to set one or more database configuration property values<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This situation occurred when the broker attempted to set database configurable property values into the database by issuing ALTER SYSTEM or ALTER DATABASE commands. Typical causes of this error are:<\/span><\/span><\/span><\/dd>\n
– The values of redo transport-related properties contain syntax syntax errors.<\/span><\/span><\/span><\/dd>\n
– The value of the LogArchiveTrace property was out of range.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log to see which property has the problem and set the property to the correct value.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16789: standby redo logs not configured<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Standby redo logs were not configured for the database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Standby redo logs are required when the redo transport mode is set to SYNC or ASYNC. Check the Data Guard documentation to see how to create standby redo logs.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16790: the value of the configurable property is invalid<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An invalid property value was entered, or a RESET was attempted on a property for which no Broker default value exists.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Set the property to a correct value.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16791: unable to check the existence of the standby redo logs<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database may not be mounted, or the query of the V$STANDBY_LOG fixed view failed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Ensure the database is mounted and query the V$STANDBY_LOG fixed view to see if the problem has been corrected, and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16792: configurable property value is inconsistent with database setting<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The values of one or more configurable properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by directly altering initialization parameters instead of editing configurable property values using Data Guard broker.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Query the InconsistentProperties property 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 configurable property settings to be propagated to the initialization parameters.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16793: logical standby database guard is off<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The logical standby database guard was turned off.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Issue the ALTER DATABASE GUARD ALL command to turn the guard on and verify that Data Guard health check error or warning is cleared.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16794: database guard is on for primary database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database guard was turned on for the primary database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Issue the ALTER DATABASE GUARD NONE command to turn off the guard and verify that Data Guard health check error or warning is cleared.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16795: the standby database needs to be re-created<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A switchover or failover operation caused this database to require re-creation. The database was marked for re-creation because it was not 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Re-create (or flash back) the standby database. Connect to the primary database in the broker configuration and reenable broker management of that database. Once enabled, it is possible to connect to that standby database and manage it with the broker. 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16796: one or more properties could not be imported from the database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The broker was unable to import property values for the database being added to the broker configuration. This error indicates:<\/span><\/span><\/span><\/dd>\n
– The Oracle Net service name specified in DGMGRL CREATE CONFIGURATION or ADD DATABASE command was not one that provides access to the database being added.<\/span><\/span><\/span><\/dd>\n
– There were no instances running for the database being added.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Remove 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 Oracle Net service name provides access to the running instance. Also check the broker log file for additional information. Then, reissue the CREATE CONFIGURATION or ADD DATABASE command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16797: database is not using a server parameter file<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database was not using a server parameter file or the broker was unable to access the server parameter file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Issue the CREATE SPFILE=’..’ FROM PFILE=’…'” command to create a server parameter file and then restart the database to use it.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16798: unable to complete recovery during failover<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The physical standby database could not complete recovery during failover.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the Data Guard broker log and the Oracle alert logs to see more details on the reason for the failure.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16799: Redo Apply is not running<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Either the Data Guard broker configuration indicates that Redo Apply was turned off, or the recovery process, MRP0, was not running. As a result, Redo Apply-related properties could not be set.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Turn on Redo Apply through Data Guard broker and reissue the command to set a Redo Apply-related property.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16800: redo transport service for a standby database incorrectly set to ALTERNATE<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The redo transport service for a standby database was set to ALTERNATE when no other destination is set to alternate to this destination.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Reenable the standby database or the entire configuration to allow the configuration property settings to be propagated to the initialization parameters.<\/span><\/span><\/span><\/dd>\n
<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-16700 to ORA-16800 ORA-16700: the standby database has diverged from the primary database Cause:\u00a0The primary database may have been flashed back or restored from a backup set and then reopened with the RESETLOGS option. Action:\u00a0Re-create the standby database from the primary database or flash back the standby…<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[14,32,54],"class_list":["post-1950","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-database-administration","tag-oracle-administration","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-vs","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1950","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/comments?post=1950"}],"version-history":[{"count":1,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1950\/revisions"}],"predecessor-version":[{"id":1951,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1950\/revisions\/1951"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=1950"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=1950"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=1950"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}