{"id":2252,"date":"2016-09-20T21:16:16","date_gmt":"2016-09-20T18:16:16","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=2252"},"modified":"2017-02-15T21:17:19","modified_gmt":"2017-02-15T18:17:19","slug":"oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-16000-to-ora-16200","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-16000-to-ora-16200\/","title":{"rendered":"Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16000 to ORA-16200"},"content":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16000 to ORA-16200<\/strong><\/p>\n

\n
ORA-16000: database or pluggable database open for read-only access<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database or pluggable database was opened for read-only access. Attempts to modify the database using DML or DDL statements generate this error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0In order to modify the database or pluggable database, it must first be shut down and reopened for read\/write access.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16001: database already open for read-only access by another instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database has been opened for read-only access by another instance, and cannot be opened for read\/write access by this instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This instance must be opened for read\/write access, or all other instances must first be shut down and reopened for read-only access.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16002: database or pluggable database already open for read\/write access by another instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database or pluggable database has been opened for read\/write access by another instance, and cannot be opened for read-only access by this instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This instance must be opened for read-only access, or all other instances must first be shut down and reopened for read\/write access.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16003: standby database is restricted to read-only access<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to open a physical standby database in read\/write mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reissue the ALTER DATABASE OPEN specifying READ ONLY.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16004: backup database required recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database could not be opened for read-only access by this instance because it requires recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Perform the necessary recovery and reopen for read-only access.<\/span><\/span>
\n<\/p>\n

\n
<\/a> ORA-16005: database requires recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database required recovery, and therefore could not be opened for read-only access by this instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If the database was terminated abnormally (possibly using a shutdown abort), the database first needs to be opened in read\/write mode. Otherwise, perform the necessary recovery and reopen for read-only access.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16006: A remote archival request was aborted due to database shutdown.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When opening or closing a database instance, the database may wait for pending remote archival requests to complete before proceeding with the operation. This error was reported because a shutdown was detected.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is an informational message so no action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16007: invalid backup control file checkpoint<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database could not be opened for read-only access because its control file did not contain a valid control file checkpoint.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Open the database for read\/write access to create a valid control file checkpoint. The database can then be opened for read-only access.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16008: indeterminate control file checkpoint<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The control file for the database being opened for read-only access was created using the CREATE CONTROLFILE statement. Therefore, a control file checkpoint could not be calculated and the database could not be opened for read-only access.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0First, open the database for read\/write access. This creates a valid control file checkpoint. Then, reopen the database for read-only access.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16009: invalid redo transport destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The redo transport destination could not accept redo data because it was not a valid redo transport destination type.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that all redo transport destinations are either standby databases or downstream capture databases.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16011: Remote File Server process is in Error state.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Remote File Server (RFS) process at the specified redo transport destination experienced an unrecoverable error and was unable to receive further redo data.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the problem at the redo transport destination.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16012: database identifier mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database identifier of a physical standby database did not match that of the primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that the database identifier of each physical standby database matches that of the primary database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16013: log\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0does not need archiving<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16014: log\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0not archived, no available destinations<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to archive the named log, but the archive was unsuccessful. The archival failed because there were no archive log destinations specified, or all destinations are in an error state.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that archive log destinations are specified or take the necessary step to correct any errors that may have occurred.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16015: Log\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0was not archived.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to archive the named log to a destination, but the operation did not succeed because the destination was not in ARCHIVELOG mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Enable ARCHIVELOG mode at all destinations and retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16016: archived log for thread\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0unavailable<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Redo apply timed out waiting for the requested archived log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the primary database is still archiving redo data to the standby database and reissue the RECOVER STANDBY DATABASE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Set the primary archive destination to a valid non-NULL value.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16018: cannot use\u00a0string<\/i>\u00a0with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1…31) parameter was encountered while fetching initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Eliminate any incompatible parameter definitions.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16019: cannot use\u00a0string<\/i>\u00a0with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified LOG_ARCHIVE_DEST_n (n = 1…31) or DB_RECOVERY_FILE_DEST parameter was encountered while fetching initialization parameters. 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Eliminate any incompatible parameter definitions.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16020: fewer destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The number of archive log destinations that could be used was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either adjust the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16021: session\u00a0string<\/i>\u00a0destination cannot be the same as session\u00a0string<\/i>\u00a0destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change the first specified archive log parameter using ALTER SESSION to have a destination value that duplicates the session-level destination value of the second specified archive log parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16023: system\u00a0string<\/i>\u00a0destination cannot be the same as session\u00a0string<\/i>\u00a0destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter produced a destination that duplicates the session destination value of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a non-NULL value with the ALTER SYSTEM command. Or, this error can occur when setting a NULL value with ALTER SESSION command, because then the associated system destination value may appear as a duplicate.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16024: parameter\u00a0string<\/i>\u00a0cannot be parsed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The value for the indicated LOG_ARCHIVE_DEST_n (n = 1…31) parameter could not be parsed. Common causes for this error are a misplaced equal sign, an unrecognized attribute, or an attribute that is missing a required value.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16025: parameter\u00a0string<\/i>\u00a0contains repeated or conflicting attributes<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained either repeated attributes or attributes that conflicted with each other.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16026: parameter\u00a0string<\/i>\u00a0contains an invalid attribute value<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained an attribute with an invalid value.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16027: parameter\u00a0string<\/i>\u00a0is missing a destination option<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The value for the indicated LOG_ARCHIVE_DEST_n (n = 1…31) parameter failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attrbute.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16028: new\u00a0string<\/i>\u00a0causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change the indicated LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameter (n = 1…31) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16029: cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Define one or more log archive destinations using parameters LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1…31). Then, change the value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16030: session specific change to the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter requires a LOG_ARCHIVE_DEST_n destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1…31) parameters.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16031: parameter\u00a0string<\/i>\u00a0destination string exceeds\u00a0string<\/i>\u00a0character limit<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The value for the specified parameter contained a destination string that is too long.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16032: parameter\u00a0string<\/i>\u00a0destination string cannot be translated<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The value for the specified parameter contained a destination string that could not be translated.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a valid destination string in the specified parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16033: parameter\u00a0string<\/i>\u00a0destination cannot be the same as parameter\u00a0string<\/i>\u00a0destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change the first specified archive log parameter to have a destination value that duplicates the system-level destination value of the second specified archive log parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a different value for one of the archive log parameters.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16034: Recovery could not be started.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Database recovery could not be started because the FROM and MANAGED STANDBY DATABASE clauses were both specifed when attempting to start recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the command with either the FROM or MANAGED STANDBY DATABASE clause, but not both.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16035: missing required keyword\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The indicated keyword is required but was not specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the syntax and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16036: invalid CANCEL option<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A mode other than IMMEDIATE followed the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify either nothing or IMMEDIATE following CANCEL.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16037: user requested cancel of managed recovery operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The managed standby database recovery operation has been canceled per user request.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16038: log\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0cannot be archived<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16039: RFS request version mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A request to archive a redo log to a redo transport destination failed because of an Oracle software version mismatch at the destination.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that a compatible version of Oracle software is running at the redo transport destination.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16040: Destination archive log file is locked.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The target archive log file was locked. This indicates that the file is being archived to another Remote File Server (RFS) process.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that each remote redo transport destination uses a unique network service name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16041: Remote File Server fatal error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Remote File Server (RFS) process at a redo transport destination encountered a fatal error and was no longer available. Further redo transmission to this destination may not be possible.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Refer to the appropriate RFS trace file located at the redo transport destination for details regarding the error encountered and take corrective action.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16042: user requested cancel immediate of redo apply<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Redo apply was canceled immediately per user request. Processing of the current archive log file has been interrupted and, therefore, the database is in an inconsistent state.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16043: Redo apply has been canceled.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Redo apply was canceled per user request or operation timeout.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0More specific messages will accompany this message.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16044: Destination\u00a0string<\/i>\u00a0attribute cannot be specified at session level.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to modify a redo transport destination attribute using the ALTER SESSION command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the ALTER SYSTEM command to modify the destination attribute.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16045: circular redo transport destination dependency chain<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to make a redo transport destination dependent on a redo transport destination that was dependent on it.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that no redo transport destination is dependent on any destination that is dependent on it.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16046: Redo transport destination failed due to failed dependent destination.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The redo transport destination was dependent upon another destination, which failed. Therefore, this destination failed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16047: DGID mismatch between destination setting and target database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The DB_UNIQUE_NAME specified for the destination did not match the DB_UNIQUE_NAME at the target database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter matches the DB_UNIQUE_NAME parameter defined at the destination.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16050: destination exceeded specified quota size<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An archive log was attempted to be created in a destination with a specified maximum quota size. The creation of the archive log exceeded the specified quota size. Therefore, the destination has been made inaccessible to future archival operations.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16051: parameter\u00a0string<\/i>\u00a0contains an invalid delay time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760 (in minutes).<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16052: DB_UNIQUE_NAME attribute is required.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0DB_UNIQUE_NAME attribute was not specified. The value of the LOG_ARCHIVE_DEST_n parameter for each remote redo transport destination must contain the DB_UNIQUE_NAME attribute if the LOG_ARCHIVE_CONFIG parameter value contains the DG_CONFIG attribute.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the DB_UNIQUE_NAME attribute to specify the DB_UNIQUE_NAME for the destination.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16053: DB_UNIQUE_NAME\u00a0string<\/i>\u00a0is not in the Data Guard Configuration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This problem can also occur when specifying a non-standby destination with an DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME initialization parameter for the current instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16055: FAL request rejected<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Fetch archive log (FAL) server rejected a redo gap fetch request from the client. This may have various causes.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the alert log on the primary database. Take the appropriate action to solve the problem.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16056: Backup control file archival requires proper syntax.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the USING BACKUP CONTROLFILE clause to perform an online log file archival using a backup control file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16057: server not in Data Guard configuration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The primary database or fetch archive log (FAL) server was not found in the Data Guard configuration of the standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Add the database unique name of the primary database or FAL server to the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database initialization parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16058: standby database instance is not mounted<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Remote File Server (RFS) process on the standby database received an internal error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the standby alert log and RFS trace files for more information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16059: empty log file or invalid next available block<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to archive an empty or invalid log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16060: Log file is current.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to archive current log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16061: Log file status has changed.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The online log file was reclaimed as a new log file either before archival started or during the archival operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16062: standby database not in Data Guard configuration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The standby database was not found in the Data Guard configuration of the server.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Add the database unique name of the standby database to the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database initialization parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16065: remote archival disabled at standby destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Receipt of remote archived REDO log files has been disabled at the associated standby destination host database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If appropriate change the associated archive log parameter to specify a local destination with the LOCATION keyword or defer the associated archive log destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the RECEIVE attribute of the LOG_ARCHIVE_CONFIG parameterand restart the standby database instance before further REDO log file archivals occur.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16066: remote archival disabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An archive log destination parameter has specified a remote destination with the SERVICE keyword. Remote archival of REDO log files has been disabled for this database. The associated archive log destination has been disabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If appropriate change the archive log parameter to specify a local destination with the LOCATION keyword or (if appropriate) set the REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the SEND attribute of the LOG_ARCHIVE_CONFIG parameter and restart the database instance before further REDO log file archivals occur.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16067: activation identifier mismatch in archive log\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The activation identifier contained in the archive log file header does not match the activation identifier of the database being recovered. The indicated archive log cannot be applied to the database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Locate the appropriate archive log for the database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16068: redo log file activation identifier mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The activation identifier of the indicated redo log file does not match the activation identifier of the database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-16069: activation identifier mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Redo transport failed because the activation identifier of the primary and physical standby databases did not match. This can happen if the physical standby database was not created from a backup of the primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create a valid configuration and re-try the failed operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16070: parameter\u00a0string<\/i>\u00a0contains an invalid REGISTER attribute value<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an O\/S-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the value for the LOG_ARCHIVE_DEST_n parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16071: Archived log file\u00a0string<\/i>\u00a0was not found at dependency destination.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified archived log file was not found at a redo tranpsort destination on which other destinations are dependent.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that all redo transport destinations that are dependent upon another destination or upon which other destinations are dependent are configured correctly.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16072: a minimum of one standby database destination is required<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0No standby database archive log destinations were specified.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a standby archive log destination in the initialization parameter file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16073: archiving must be enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Online log file archiving is disabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Enable log file archiving.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16074: No ARCH processes are active.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0All ARCH processes have stopped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restart the instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16075: standby database destination mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Another instance had access to a standby database destination that this instance did not. If the initialization parameter LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this may be due to a standby database becoming unavailable recently.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that at each instance the set of standby databases referred to by LOG_ARCHIVE_DEST_n initialization parameters is the same and define a DG_CONFIG at each instance to identify those databases explicitly.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16076: unknown standby database destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A standby database destination was specified that was not accessed by another instance. If the initialization parameter LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this mismatch may be due to a standby database having been restarted recently.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that at each instance the set of standby databases referred to by LOG_ARCHIVE_DEST_n initialization parameters is the same and define a DG_CONFIG at each instance to identify those databases explicitly.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16078: media recovery disabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database is not in ARCHIVELOG mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Place the database in ARCHIVELOG mode.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16079: standby archival not enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The standby database did not have archival enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0In order to allow the standby database to access the standby log files, the standby database must be in ARCHIVELOG mode.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16080: invalid LogMiner session\u00a0string<\/i>\u00a0for APPLY<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby apply engine was started with an invalid LogMiner session identifier.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Fix the problem with the LogMiner session or create a new session.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16081: insufficient number of processes for APPLY<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby apply engine was started with fewer processes available than needed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase the values of the initialization parameters PROCESSES and or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16082: logical standby is not initialized correctly<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby apply engine was started but it found inconsistencies in its metadata.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Look in the trace file for more information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16083: LogMiner session has not been created<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby apply engine was started without creating a LogMiner session.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create a LogMiner session and restart the apply engine.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16084: an apply engine is already running<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A logical standby apply engine was running when another was created.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shut down the previous apply engine before starting a new one.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16086: Redo data cannot be written to the standby redo log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The primary database was in MAXIMUM PROTECTION or MAXIMUM AVAILABILITY mode, but redo data could not be written to the standby redo log at the standby database(s).<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the Remote File Server (RFS) trace file for specific errors and reconfigure the standby redo log as appropriate.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16087: Switchover requires standby or current control file.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to perform a switchover operation using a backup or clone control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Convert the backup control file into a current control file prior to attempting a switchover operation. A clone control file cannot be used for a switchover operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16088: archive log has not been completely archived<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to register an archive log that has not been completely archived. The specified archive log may be a “current” log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a completed archive log.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16089: archive log has already been registered<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to register an archive log that already has a corresponding thread# and sequence# entry in the standby database control file. Duplicate information is not permitted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the V$ARCHIVED_LOG fixed view to verify the archive log information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16090: archive log to be replaced not created by managed standby process<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to replace an archive log entry that was not originally created by the managed standby operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No user action required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16091: dependent archive log destination already archived<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An archive log destination contains a dependency to another archive log destination that has previously been archived.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16092: dependent archive log destination is not active<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An archive log destination contains a dependency to another archive log destination that is not active”<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The child archive log destination cannot be dependent on another invalid archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16093: dependent archive log destination is not LGWR-enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An archive log destination contains a dependency to another archive log destination that is not enabled for the LGWR process”<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The child archive log destination cannot be dependent on another archive log destination not archived by the LGWR. Use the ALTER SYSTEM command to change the parent archive log to specify the LGWR process.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16094: Database shut down during archival operation.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database was shut down while an online log file archival was active.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16095: Dependent destination removal for inactivation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A dependent archive log destination was inactivated due to the parent archive log destination becoming inelligible for archival. This may be due to the parent destination being manually deferred by an application user.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16096: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0None<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify this command to switch the primary database to the physical standby role.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16097: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0None<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify this command to switch the physical standby database to the primary role.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16098: Primary database has been shut down to prevent data loss.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The primary database was shut down because it was operating in maximum protection mode and no suitable standby databases were available to protect the primary database from data loss.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Diagnose and correct whatever errors exist in the configuration or configure the primary database for maximum availability or maximum performance mode.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16099: internal error ORA-00600 occurred at standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The RFS process on the standby database received an internal error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the standby alert log and RFS trace files for more information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16100: not a valid Logical Standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This database has not been completely configured as a Logical Standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY INITIAL statement. See the Oracle8i SQL Reference manual for the statement syntax.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16101: a valid start SCN could not be found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An SCN from which to start could not be found.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Register the first log file following the backup from which this database was generated. Using the ALTER DATABASE REGISTER LOGILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this startement.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16102: remote information is not available on the specified primary<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The new primary has not completed generating the necessary information for the standby to begin consuming its log stream.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the database link provided references a system that is about to become a new primary. Wait a short time before retrying the command to allow the primary some time to generate the necessary information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16103: Logical Standby apply must be stopped to allow this operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or respecify the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16104: Invalid Logical Standby parameter<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified parameter is not valid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check spelling or refer to the DBMS_LOGSTDBY PL\/SQL package documentation for the correct statement syntax.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16105: Logical Standby is already running in background<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A Logical Standby apply operation is already running.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-16106: loading previously applied transaction information<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical Standby coordinator was performing a scan to identify previously applied transactions.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16107: all log data from primary has been processed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0On the primary system, the log stream has been ended by the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Issue one of the following commands to make this standby a primary or resume applying changes from a new primary. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL PRIMARY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;<\/span><\/span><\/p>\n

\n
<\/a> ORA-16108: database is no longer a standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The current database has already been made a primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Issue the following commands to make this primary a standby. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;<\/span><\/span><\/p>\n

\n
<\/a> ORA-16109: failed to apply log data from previous primary<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Log data from previous primary could not be completely applied.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check DBA_LOGSTDBY_EVENTS for failures and take corrective action. Then, reissue command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16110: user procedure processing of logical standby apply DDL<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16111: log mining and apply setting up<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This logical standby process is setting up to begin processing changes.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16112: log mining and apply stopping<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This logical standby process is cleaning up and stopping Logical Standby apply.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16113: applying change to table or sequence\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The process is applying changes to a specific schema object.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16114: applying DDL transaction with commit SCN\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The process is applying a DDL change that’s committed at the given SCN.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16115:\u00a0string<\/i>\\% of LogMiner dictionary loading is done<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The process is loading dictionary information from the redo stream. This activity may take a few minutes.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16116: no work available<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The process is idle waiting for additional changes to be made available.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16117: processing<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The process is performing its primary function and is not waiting on any significant event.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16119: building transaction at SCN\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The transaction being committed at the given SCN is being prepared for apply.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16120: dependencies being computed for transaction at SCN\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The transaction committed at the given SCN is being analyzed for dependencies.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16121: applying transaction with commit SCN\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The transaction committed at the given SCN is being applied.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16122: applying large dml transaction at SCN\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16123: transaction\u00a0string<\/i>\u00a0string<\/i>\u00a0string<\/i>\u00a0is waiting for commit approval<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The apply process is waiting for approval to commit a transaction. This transaction may depend on another or other synchronization activity may delay the committing of a transaction.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16124: transaction\u00a0string<\/i>\u00a0string<\/i>\u00a0string<\/i>\u00a0is waiting on another transaction<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The apply process is waiting to apply additional changes. This transaction likely depends on another.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16125: large transaction\u00a0string<\/i>\u00a0string<\/i>\u00a0string<\/i>\u00a0is waiting for more data<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16126: loading table or sequence\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Information on the given table or sequence is being loaded into an in memory cache for future use.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16127: stalled waiting for additional transactions to be applied<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This process is waiting for additional memory before continuing. Additional log information cannot be read into memory until more transactions have been applied to the database, thus freeing up additional memory.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, increase available SGA or the number of apply processes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16128: User initiated stop apply successfully completed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby was shutdown in an orderly fashion.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16129: unsupported DML encountered<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One or more DMLs to an unsupported table were encountered and skipped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. This informational statement is provided to record the event for diagnostic purposes. Optionally, check the DBA_LOGSTDBY_EVENTS view for more information including the impacted table owner and name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16130: supplemental log information is missing from log stream<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Supplemental logging is not enabled at the primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Issue the following command to enable supplemental logging. ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;<\/span><\/span><\/p>\n

\n
<\/a> ORA-16131: An error occurred during a Terminal Recovery of the standby.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred during a Terminal Recovery of the standby.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the standby alert log additional information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16132: An error occurred during activation of the standby.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred during activation of the standby database following a Terminal Recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the standby alert log additional information.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16133: Datafile\u00a0string<\/i>\u00a0has incorrect terminal recovery stamp.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0After activation of a standby database following a terminal recovery (recovery of standby using current logs), recovery of a datafile from before the activation must have completed the same terminal recovery to avoid corruption.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16134: invalid MANAGED recovery FINISH option<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A mode other than NOWAIT follows the FINISH keyword in RECOVER MANAGED STANDBY DATABASE statement.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify either nothing or NOWAIT following FINISH.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected mode<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LOG_ARCHIVE_CONFIG parameter can not be modified while any RAC instance is open in either maximum protection or maximum availability mode. Also, the parameter can not be modified in such way that would cause all destinations to fail while in maximum protection mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make the modification before the database is opened by any instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16136: Managed Standby Recovery not active<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to cancel a managed recovery session but no managed recovery session was active.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is necessary.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16137: invalid state change to a managed alternate destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to explicitly change the state of a destination participating in an internally managed set of alternate destinations. For example, a destination in the ALTERNATE state was explicitly ENABLED. Doing so will thwart the internal mechanisms to manage these cooperating destinations.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The destination must be reset before making this state change.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16138: end of log stream not received from primary<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the primary log stream has been terminated. Ensure that the standby has applied all necessary redo from the primary system and, if appropriate, reissue the graceful switchover command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16139: media recovery required<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error has occurred while performing a switchover.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If you were switching a primary database to the standby role, the conversion was successful, but one or more errors occurred after the conversion completed. See the alert log for more information. You can proceed with switching the target standby database to the primary role, but you must address the errors reported at the old primary database before it can protect the new primary database. If you encountered this error while switching a physical standby database to the primary role, the switchover did not succeed because additional redo must be applied. Verify that redo apply is active and wait until the SWITCHOVER_STATUS column of the V$DATABASE dynamic performance view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying the switchover.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16140: standby online logs have not been recovered<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0To recover the standby online logs issue the following command: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH. Then reissue the ALTER DATABASE ACTIVATE STANDBY DATABASE command. To activate the standby without recovering the online logs, issue the following command: ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16143: RFS connections not allowed during or after terminal recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The primary must not attempt to archive to the standby after a terminal recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16145: archival for thread#\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0in progress<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The indicated archived log file is not available for recovery due to the fact that it is still being archived.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that archival of the indicated log file has completed and reissue the RECOVER STANDBY DATABASE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16146:\u00a0string<\/i>control file enqueue unavailable<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The control file enqueue is currently unavailable.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No Action is required. We will try to re-fetch it at a later time.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16147: standby database referenced by multiple archive log destinations<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Multiple archive log destinations reference the same standby database, using different service names. This is not allowed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Remove one of the duplicate archive log destinations.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16148: user requested expiration of managed recovery operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16150: FINISH recovery performed on another, older standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An archive log containing a FINISH recovery indicator was received by a standby database that has received archive logs in the future of the received archive log. Because of the possibility that these future archive logs have been applied to this standby database, the received archive log must be rejected.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16151: Managed Standby Recovery not available<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The attempted operation failed because of a pending CANCEL of the managed standby recovery operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait for the managed standby recovery session to end. Then retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16152: standby database is in ‘no-data-loss’ protected mode<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The attempted database operation is not allowed while the standby database is in ‘no-data-loss’ protected mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16154: suspect attribute:\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Use of the indicated attribute is illegal in the given context.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make the appropriate changes and reissue the statement.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16156: LGWR archive log dependency not allowed if database is standby protected<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The use of a LGWR archive log dependency is not allowed when the primary is protected by a standby database, as this requires use of the standby redo log files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Remove the LGWR archive log dependency and use normal LGWR archival instead.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16157: media recovery not allowed following successful FINISH recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Issue one of these operations following a FINISH recocvery: ALTER DATABASE OPEN READ ONLY or ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16159: Cannot change protected standby destination attributes<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change the LGWR\/ARCH or SYNC\/ASYNC attributes for a destination that is participating in the standby protection mode of the database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16160: Cannot change protected standby database configuration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change the standby database configuration when the primary database is in standby protected mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The standby database must be added to the configuration before the primary database is opened.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16161: Cannot mix standby and online redo log file members for group\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to add a log file member that did not match the other member types. This problem typically occurs when adding a standby log file member to an online redo log file group, or adding an online redo log file member to a standby redo log file group.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify the log file group type using the TYPE column of the V$LOG fixed view.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16162: Cannot add new standby databases to protected configuration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The standby database must be added to the configuration before the primary database is opened.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16163: LGWR network server host attach error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LGWR network server could not attach to remote host<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/p>\n

\n
<\/a> ORA-16164: LGWR network server host detach error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LGWR network server could not detach from remote host<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/p>\n

\n
<\/a> ORA-16165: LGWR failed to hear from network server<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LGWR lost its connection to the network server<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/p>\n

\n
<\/a> ORA-16166: LGWR network server failed to send remote message<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LGWR network server could not communicate with the remote host<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/p>\n

\n
<\/a> ORA-16167: LGWR network server could not switch to non-blocking mode<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LGWR network server could not switch to non-blocking mode<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/p>\n

\n
<\/a> ORA-16168: LGWR network server could not switch to blocking mode<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LGWR network server could not switch to blocking mode<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/p>\n

\n
<\/a> ORA-16169: LGWR network server invalid parameters<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LGWR network server could not switch to blocking mode<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/p>\n

\n
<\/a> ORA-16170: Terminal recovery may have left the database in an inconsistent state<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Continue standby recovery with additional log shipping from primary.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16171: RECOVER…FINISH not allowed due to gap for thr\u00a0string<\/i>, seq\u00a0string<\/i>–string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0See alert log for more details<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Copy missing archived logs from primary or another standby. Register the logs and reissue the RECOVER…FINISH command. If the logs are not available, issue the ALTER DATABASE RECOVER MANAGED STANDBY SKIP command to ignore the standby redo log files.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16172: archive logs detected beyond Terminal End-Of-Redo<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due the existence, at the remote site, of archive logs containing REDO in the future of the Terminal EOR.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0n\/a<\/span><\/span><\/p>\n

\n
<\/a> ORA-16173: incompatible archival network connections active<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One of two situations can cause this error: 1) An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected. 2) An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to an active Remote File Server process at the remote site. An active Remote File Server (RFS) process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16174: user requested thread\/sequence termination of managed recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The managed standby database recovery operation has been terminated per user specified THROUGH THREAD\/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16175: cannot shut down database when media recovery is active<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to shut down a standby database while media recovery was active.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Cancel media recovery to proceed with the shutdown.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16176: background dictionary build cannot be running<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The background process dedicated to dictionary build is active.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0wait and try it later.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16177: media recovery is not required<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The THROUGH LAST SWITCHOVER clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE was specified and the database has been recovered to the most recent End-Of-Redo marker. All known archived logs have been applied. Managed recovery is not required.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is necessary. The standby database may be activated as a new primary or may continue as a standby.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16178: Cannot specify remote destinations in manual archiving mode<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database is operating in manual archiving mode. Remote archivelog destinations are not allowed in this mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the ALTER DATABASE ARCHIVELOG command to place the database in automatic ARCHIVELOG mode, or defer the archivelog destinations that specify the SERVICE= attribute.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16179: incremental changes to “string<\/i>” not allowed with SPFILE<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Incremental changes to a log_archive_dest_n parameter cannot be made when using an SPFILE.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify either LOCATION or SERVICE plus all other attributes to be set in one ALTER SYSTEM\/SESSION SET command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16180: number of processes specified is too large<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The number of server processes available for Logical Standby is currently limited to 1024 LogMiner processes and 1024 apply processes or a total of 2048.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry with a lower value.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16181: SGA specified for Logical Standby is too large<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0MAX_SGA is larger than 75% of the larger of initialization parameters SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the value of MAX_SGA to be less than 75% of the maximum of SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16182: Internal error on internal channel during remote archival<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An internal error was encountered on the internal channel between LGWR and Network Server.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required, as an attempt will be made to re-archive the file that had this failure during archival.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16184: DB_UNIQUE_NAME\u00a0string<\/i>\u00a0hashes to the same value as DB_UNIQUE_NAME\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The internal hash value generated for one DB_UNIQUE_NAME collided with the hash value of another DB_UNIQUE_NAME.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a different value.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16185: REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG parameters are defined in the initialization file and they are mutually exclusive.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use only the LOG_ARCHIVE_CONFIG parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID=’*’ qualifier<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly the same on all RAC instances so the SID=’*’ qualifier is required.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-enter the command using the SID=’*’ qualifier.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LOG_ARCHIVE_CONFIG parameter was specified with duplicate, conflicting or invalid attributes.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the documentation regarding the correct specification of the LOG_ARCHIVE_CONFIG parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The settings for the LOG_ARCHIVE_CONFIG parameter were inconsistent with the settings of a previously started instance. The settings for this parameter must be exactly the same for all instances.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that all instances use the exact same LOG_ARCHIVE_CONFIG settings.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16191: Primary log shipping client not logged on standby<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to ship redo to standby without logging on to standby or with invalid user credentials.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check that primary and standby are using password files and that both primary and standby have the same SYS password. Restart primary and\/or standby after ensuring that password file is accessible and REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED or EXCLUSIVE.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16192: Primary and standby network integrity mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Standby wants sqlnet network integrity for redo shipment which is not configured properly at the primary.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check sqlnet.ora documentation regarding how to setup network integrity and set it up identically on both primary and standby. Restart primary and\/or standby.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16193: Primary and standby network encryption mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Standby wants sqlnet network encryption for redo shipment which is not configured properly at the primary.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check sqlnet.ora documentation regarding how to setup network encryption and set it up identically on both primary and standby. Restart primary and\/or standby.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16194: Modifying DB_UNIQUE_NAME requires SID=’*’ qualifier<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The setting for the DB_UNIQUE_NAME parameter must be exactly the same on all RAC instances so the SID=’*’ qualifier is required.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-enter the command using the SID=’*’ qualifier.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can only be used if the DB_UNIQUE_NAME parameter has been explicitly defined.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Explicitly define a valid DB_UNIQUE_NAME.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16196: database has been previously opened and closed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The instance has already opened and closed the database, which is allowed only once in its lifetime.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shut down the instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16197: Invalid DB_UNIQUE_NAME parameter specification<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The DB_UNIQUE_NAME parameter has an invalid specification. The DB_UNIQUE_NAME parameter has a maximum length of 30 characters and the only characters allowed are alpha-numeric characters and “_”, “$” and “#”.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the documentation and re-enter the parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16198: Timeout incurred on internal channel during remote archival<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A timeout was incurred during remote archival.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required, as an attempt will be made to re-archive the file that had this failure during archival.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16199: Terminal recovery failed to recover to a consistent point<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0See alert log for more details<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, call Oracle support.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16200: Skip procedure requested to skip statement<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby called a skip procedure that requested for a particular statement not to be applied.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16000 to ORA-16200 ORA-16000: database or pluggable database open for read-only access Cause:\u00a0The database or pluggable database was opened for read-only access. Attempts to modify the database using DML or DDL statements generate this error. Action:\u00a0In order to modify the database or pluggable database, it must…<\/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":[54],"class_list":["post-2252","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-Ak","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2252","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=2252"}],"version-history":[{"count":1,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2252\/revisions"}],"predecessor-version":[{"id":2253,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2252\/revisions\/2253"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=2252"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=2252"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=2252"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}