ORA-16067: activation identifier mismatch in archive log string

ORA-16067: activation identifier mismatch in archive log string

Cause: The 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.

Action: Locate the appropriate archive log for the database.

ORA-16066: remote archival disabled

ORA-16066: remote archival disabled

Cause: An 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.

Action: If 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.

ORA-16065: remote archival disabled at standby destination

ORA-16065: remote archival disabled at standby destination

Cause: Receipt of remote archived REDO log files has been disabled at the associated standby destination host database.

Action: If 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.

ORA-16064: remote archival is disabled by another instance

ORA-16064: remote archival is disabled by another instance

Cause: Remote archival of database REDO log files has been disabled by another instance, and cannot be enabled for this instance.

Action: Set the REMOTE_ARCHIVE_ENABLE parameter to FALSE and restart this instance.

ORA-16063: remote archival is enabled by another instance

ORA-16063: remote archival is enabled by another instance

Cause: Remote archival of database REDO log files has been enabled by another instance, and cannot be disabled for this instance.

Action: Set the REMOTE_ARCHIVE_ENABLE parameter to TRUE and restart this instance.

ORA-16062: DGID from standby not in Data Guard configuration

ORA-16062: DGID from standby not in Data Guard configuration

Cause: The Data Guard name from the standby is not in the Data Guard configuration of the server.

Action: In order for the server to be allowed to archive logs to the standby, the Data Guard name of the standby must be in the Data Guard configuration of the server.

ORA-16061: Log file status has changed

ORA-16061: Log file status has changed

Cause: It is possible the online log file was reclaimed as a new log file either before archival started, or during the archival operation.

Action: No action is required.

ORA-16060: Log file is current

ORA-16060: Log file is current

Cause: The current log file cannot be archived using its file name.

Action: No action is required.

ORA-16059: Log file is empty or invalid next available block

ORA-16059: Log file is empty or invalid next available block

Cause: Archiving not allowed of an empty or invalid log file.

Action: No action is required.

ORA-16058: standby database instance is not mounted

ORA-16058: standby database instance is not mounted

Cause: The RFS process on the standby database received an internal error.

Action: Check the standby alert log and RFS trace files for more information.

ORA-16057: DGID from server not in Data Guard configuration

ORA-16057: DGID from server not in Data Guard configuration

Cause: The Data Guard name of the primary database or the FAL server is not in the Data Guard configuration of the standby.

Action: In order for the primary database or the FAL server to archive logs to the standby database, the Data Guard name of the primary or FAL server must be in the Data Guard configuration of the standby.

ORA-16056: backup control file archival requires proper syntax

ORA-16056: backup control file archival requires proper syntax

Cause: An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified.

Action: If the archival operation is correct when using a backup control file, then the USING BACKUP CONTROLFILE syntax is required.

ORA-16055: FAL request rejected

ORA-16055: FAL request rejected

Cause: FAL server rejects the FAL request from the FAL client. This may be caused by different reasons.

Action: to solve the problem.

ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration

ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration

Cause: The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.

Action: If 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.

ORA-16052: DB_UNIQUE_NAME attribute is required

ORA-16052: DB_UNIQUE_NAME attribute is required

Cause: The DB_UNIQUE_NAME attribute is required when DG_CONFIG is enabled.

Action: Use the DB_UNIQUE_NAME attribute to specify a valid Data Guard Name for the destination. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view.

ORA-16051: parameter string contains an invalid delay time

ORA-16051: parameter string contains an invalid delay time

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760 (in minutes).

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16050: destination exceeded specified quota size

ORA-16050: destination exceeded specified quota size

Cause: An 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.

Action: No action is required.

ORA-16047: DGID mismatch between destination setting and standby

ORA-16047: DGID mismatch between destination setting and standby

Cause: The DB_UNIQUE_NAME specified for the destination does not match the DB_UNIQUE_NAME at the destination.

Action: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_ DEST_n parameter defined for the destination matches the DB_UNIQUE_NAME parameter defined at the destination.

ORA-16046: Archive log destination failed due to failed dependent destination

ORA-16046: Archive log destination failed due to failed dependent destination

Cause: The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails.

Action: No action required.

ORA-16045: circular archive log destination dependency chain

ORA-16045: circular archive log destination dependency chain

Cause: An archive log destination contains a dependency to another archive log destination that also contains a dependency.

Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.

ORA-16044: destination string attribute cannot be specified at session level

ORA-16044: destination string attribute cannot be specified at session level

Cause: An archive log destination attribute was attempted to be modified at the session level.

Action: Use the ALTER SYSTEM command to modify the destination attribute.

ORA-16043: managed recovery session canceled

ORA-16043: managed recovery session canceled

Cause: The standby database managed recovery operation has been canceled per user request or operation timeout.

Action: More specific messages will accompany this message.

ORA-16042: user requested cancel immediate of managed recovery operation

ORA-16042: user requested cancel immediate of managed recovery operation

Cause: The managed standby database recovery operation has been canceled immediately per user request. Processing of the current archive log file has been interrupted and therefore the database is in an inconsistent state.

Action: No action is required.

ORA-16041: Remote File Server fatal error

ORA-16041: Remote File Server fatal error

Cause: The Remote File Server (RFS) process at the standby destination archive log site has encountered a disabling error and is no longer available. Further archiving to the standby site may not be possible.

Action: Refer to the appropriate RFS trace file located at the standby site for details regarding the error encountered and if possible take corrective action.

ORA-16040: standby destination archive log file is locked

ORA-16040: standby destination archive log file is locked

Cause: The target standby destination archive log file is currently locked. This indicates that the file is being archived to by another Remote File Server (RFS) process.

Action: Check for and eliminate duplicate standby destination archive log service names defined for the primary database.

ORA-16039: RFS request version mismatch

ORA-16039: RFS request version mismatch

Cause: A request to archive a redo log to a standby site failed because the request was incompatible with the Remote File Server (RFS) at the standby site.

Action: Verify that compatible versions of Oracle are running on the primary and all standby sites.

ORA-16038: log string sequence# string cannot be archived

ORA-16038: log string sequence# string cannot be archived

Cause: An 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.

Action: No action is required.

ORA-16037: user requested cancel of managed recovery operation

ORA-16037: user requested cancel of managed recovery operation

Cause: The managed standby database recovery operation has been canceled per user request.

Action: No action is required.

ORA-16036: invalid MANAGED recovery CANCEL option

ORA-16036: invalid MANAGED recovery CANCEL option

Cause: A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.

Action: Specify either nothing or IMMEDIATE following CANCEL.

ORA-16035: missing required keyword string

ORA-16035: missing required keyword string

Cause: The indicated keyword is required but was not specified.

Action: Correct the syntax and retry the command.

ORA-16034: FROM parameter is incompatible with MANAGED recovery

ORA-16034: FROM parameter is incompatible with MANAGED recovery

Cause: Use of the FROM location parameter is not allowed when MANAGED recovery has been specified.

Action: Correct the syntax and retry the command.

ORA-16033: parameter string destination cannot be the same as parameter string destination

ORA-16033: parameter string destination cannot be the same as parameter string destination

Cause: An 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.

Action: Specify a different value for one of the archive log parameters.

ORA-16032: parameter string destination string cannot be translated

ORA-16032: parameter string destination string cannot be translated

Cause: The value for the specified parameter contained a destination string that could not be translated.

Action: Use a valid destination string in the specified parameter.

ORA-16031: parameter string destination string exceeds string character limit

ORA-16031: parameter string destination string exceeds string character limit

Cause: The value for the specified parameter contained a destination string that is too long.

Action: Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message.

ORA-16030: session specific change requires a LOG_ARCHIVE_DEST_n destination

ORA-16030: session specific change requires a LOG_ARCHIVE_DEST_n destination

Cause: The 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.

Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_ DEST parameters with LOG_ARCHIVE_DEST_n (n = 1...10) parameters.

ORA-16029: cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations

ORA-16029: cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations

Cause: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_ DEST parameter when there are no archive log destinations.

Action: Define one or more log archive destinations using parameters LOG_ ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1...10). Then, change the value of parameter LOG_ARCHIVE_MIN_ SUCCEED_DEST.

ORA-16028: new string causes less destinations than LOG_ARCHIVE_MIN_ SUCCEED_DEST requires

ORA-16028: new string causes less destinations than LOG_ARCHIVE_MIN_ SUCCEED_DEST requires

Cause: With automatic archiving enabled, an attempt was made to change the indicated LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...10) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.

Action: Either 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.

ORA-16027: parameter string is missing a destination option

ORA-16027: parameter string is missing a destination option

Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attrbute.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16026: parameter string contains an invalid attribute value

ORA-16026: parameter string contains an invalid attribute value

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained an attribute with an invalid value.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16025: parameter string contains repeated or conflicting attributes

ORA-16025: parameter string contains repeated or conflicting attributes

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained either repeated attributes or attributes that conflicted with each other.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16024: parameter string cannot be parsed

ORA-16024: parameter string cannot be parsed

Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) 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.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16023: system string destination cannot be the same as session string destination

ORA-16023: system string destination cannot be the same as session string destination

Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1...10) 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.

Action: Specify a different destination value for the first specified LOG_ ARCHIVE_DEST_n parameter.

ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_ DUPLEX_DEST is non-NULL

ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_ DUPLEX_DEST is non-NULL

Cause: An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL.

Action: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value.

ORA-16021: session string destination cannot be the same as session string destination

ORA-16021: session string destination cannot be the same as session string destination

Cause: An 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.

Action: Specify a different session destination value for one of the LOG_ ARCHIVE_DEST_n parameters.

ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_ SUCCEED_DEST

ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_ SUCCEED_DEST

Cause: With automatic archiving enabled, the number of archive log destinations that could be used for the database was less than the LOG_ARCHIVE_MIN_ SUCCEED_DEST parameter value.

Action: Either adjust the settings of the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.

ORA-16019: cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_ DUPLEX_DEST

ORA-16019: cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_ DUPLEX_DEST

Cause: One 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...10) 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.

Action: Eliminate any incompatible parameter definitions.

ORA-16018: cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_ FILE_DEST

ORA-16018: cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_ FILE_DEST

Cause: One 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...10) 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.

Action: Eliminate any incompatible parameter definitions.

ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination

ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination

Cause: The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly.

Action: Set the primary archive destination to a valid non-NULL value.

ORA-16016: archived log for thread string sequence# string unavailable

ORA-16016: archived log for thread string sequence# string unavailable

Cause: The managed standby database recovery operation has timed out waiting for the requested archived log file.

Action: Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command.

ORA-16015: log string sequence# string not archived, media recovery disabled

ORA-16015: log string sequence# string not archived, media recovery disabled

Cause: An attempt was made to archive the named log, but the archive was unsuccessful. A standby archive log destination was specified and the database was not media recovery enabled. This is not allowed.

Action: Disable the standby destination or enable media recovery and retry.

ORA-16014: log string sequence# string not archived, no available destinations

ORA-16014: log string sequence# string not archived, no available destinations

Cause: An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors.

Action: Verify that archive log destinations are being specified and or or take the necessary step to correct any errors that may have occurred.

ORA-16013: log string sequence# string does not need archiving

ORA-16013: log string sequence# string does not need archiving

Cause: An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived.

Action: No action is required.

ORA-16012: Archive log standby database identifier mismatch

ORA-16012: Archive log standby database identifier mismatch

Cause: The database identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16011: Archivelog Remote File Server process in Error state

ORA-16011: Archivelog Remote File Server process in Error state

Cause: The archivelog remote file server (RFS) process at the specified standby database site has experienced an unrecoverable error and is unable to receive further archive log data.

Action: Correct the problem at the standby database site.

ORA-16009: remote archive log destination must be a STANDBY database

ORA-16009: remote archive log destination must be a STANDBY database

Cause: The database associated with the archive log destination service name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16008: indeterminate control file checkpoint

ORA-16008: indeterminate control file checkpoint

Cause: The control file for the database being opened for read-only access was created via CREATE CONTROLFILE. Therefore a control file checkpoint could not be calculated and the database cannot be opened for read-only access.

Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access.

ORA-16007: invalid backup control file checkpoint

ORA-16007: invalid backup control file checkpoint

Cause: The backup control file being opened for read-only access does not contain a valid control file checkpoint. Therefore the database cannot be opened for read-only access.

Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access.

ORA-16006: audit_trail destination incompatible with database open mode

ORA-16006: audit_trail destination incompatible with database open mode

Cause: The audit_trail initialization parameter was set to DB (or TRUE), which is incompatible with a database opened for read-only access.

Action: When the database is opened for read-only access, the audit_trail initialization parameter can only be set to OS or NONE (FALSE).

ORA-16005: database requires recovery

ORA-16005: database requires recovery

Cause: The database requires recovery, and therefore cannot be opened for read-only access by this instance.

Action: Perform the necessary recovery and re-open for read-only access.

ORA-16004: backup database requires recovery

ORA-16004: backup database requires recovery

Cause: The control file is for a backup database which requires recovery, and cannot be opened for read-only access by this instance.

Action: Perform the necessary recovery and re-open for read-only access.