ORA-16201: Skip procedure requested to apply statement

ORA-16201: Skip procedure requested to apply statement

Cause: Logical standby called a skip procedure that requested for a particular statement to be applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16200: Skip procedure requested to skip statement

ORA-16200: Skip procedure requested to skip statement

Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied.

Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.

ORA-16199: Terminal recovery failed to recover to a consistent point

ORA-16199: Terminal recovery failed to recover to a consistent point

Cause: See alert log for more details

Action: Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, call Oracle support.

ORA-16198: Timeout incurred on internal channel during remote archival

ORA-16198: Timeout incurred on internal channel during remote archival

Cause: A timeout was incurred during remote archival.

Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival.

ORA-16197: Invalid DB_UNIQUE_NAME parameter specification

ORA-16197: Invalid DB_UNIQUE_NAME parameter specification

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

Action: Check the documentation and re-enter the parameter.

ORA-16196: database has been previously opened and closed

ORA-16196: database has been previously opened and closed

Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime.

Action: Shut down the instance.

ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined

ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined

Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can only be used if the DB_UNIQUE_NAME parameter has been explicitly defined.

Action: Explicitly define a valid DB_UNIQUE_NAME.

ORA-16194: Modifying DB_UNIQUE_NAME requires SID= * qualifier

ORA-16194: Modifying DB_UNIQUE_NAME requires SID= * qualifier

Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the same on all RAC instances so the SID= * qualifier is required.

Action: Re-enter the command using the SID= * qualifier.

ORA-16193: Primary and standby network encryption mismatch

ORA-16193: Primary and standby network encryption mismatch

Cause: Standby wants sqlnet network encryption for redo shipment which is not configured properly at the primary.

Action: Check sqlnet.ora documentation regarding how to setup network encryption and set it up identically on both primary and standby. Restart primary and or or standby.

ORA-16192: Primary and standby network integrity mismatch

ORA-16192: Primary and standby network integrity mismatch

Cause: Standby wants sqlnet network integrity for redo shipment which is not configured properly at the primary.

Action: Check sqlnet.ora documentation regarding how to setup network integrity and set it up identically on both primary and standby. Restart primary and or or standby.

ORA-16191: Primary log shipping client not logged on standby

ORA-16191: Primary log shipping client not logged on standby

Cause: An attempt to ship redo to standby without logging on to standby or with invalid user credentials.

Action: Check that primary and standby are using password files and that both primary and standby have the same SYS password. Restart primary and or or standby after ensuring that password file is accessible and REMOTE_LOGIN_ PASSWORDFILE initialization parameter is set to SHARED or EXCLUSIVE.

ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance

ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance

Cause: The settings for the LOG_ARCHIVE_CONFIG parameter are inconsistent with the settings of a previously started instance. The settings for this parameter must be exactly the same for all instances.

Action: Make sure all instances use the exact same LOG_ARCHIVE_CONFIG settings.

ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes

ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes

Cause: The LOG_ARCHIVE_CONFIG parameter was specified with duplicate, conflicting or invalid attributes.

Action: Check the documentation regarding the correct specification of the LOG_ ARCHIVE_CONFIG parameter.

ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID= * qualifier

ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID= * qualifier

Cause: The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly the same on all RAC instances so the SID= * qualifier is required.

Action: Re-enter the command using the SID= * qualifier.

ORA-16185: REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive

ORA-16185: REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive

Cause: Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG parameters are defined in the initialization file and they are mutually exclusive.

Action: The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use only the LOG_ARCHIVE_CONFIG parameter.

ORA-16184: DB_UNIQUE_NAME string hashes to the same value as DB_UNIQUE_ NAME string

ORA-16184: DB_UNIQUE_NAME string hashes to the same value as DB_UNIQUE_ NAME string

Cause: The internal hash value generated for one DB_UNIQUE_NAME collided with the hash value of another DB_UNIQUE_NAME.

Action: Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a different value.

ORA-16182: Internal error on internal channel during remote archival

ORA-16182: Internal error on internal channel during remote archival

Cause: An internal error was encountered on the internal channel between LGWR and Network Server.

Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival.

ORA-16181: SGA specified for Logical Standby is too large

ORA-16181: SGA specified for Logical Standby is too large

Cause: MAX_SGA is larger than the larger of initialization parameters SHARED_ POOL_SIZE and SGA_TARGET.

Action: Specify the value of MAX_SGA to be less than the maximum of SHARED_POOL_SIZE and SGA_TARGET. Likely only 75% or lower.

ORA-16180: number processes specified for MAX_PARALLEL_SERVERS is too small

ORA-16180: number processes specified for MAX_PARALLEL_SERVERS is too small

Cause: The max number of parallel servers available for Logical Standby is less than 5 becase of the limit imposed by the too small value of MAX_PARALLEL_ SERVERS.

Action: Adjust the values of the initialization parameters PARALLEL_MAX_ SERVERS to be at least 5.

ORA-16179: incremental changes to string not allowed with SPFILE

ORA-16179: incremental changes to string not allowed with SPFILE

Cause: Incremental changes to a log_archive_dest_n parameter cannot be made when using an SPFILE.

Action: Specify either LOCATION or SERVICE plus all other attributes to be set in one ALTER SYSTEM or SESSION SET command.

ORA-16178: Cannot specify remote destinations in archivelog manual mode

ORA-16178: Cannot specify remote destinations in archivelog manual mode

Cause: The database is operating in ARCHIVELOG MANUAL mode. Remote archivelog destinations are not allowed in this mode.

Action: Use the ALTER DATABASE ARCHIVELOG command to place the database in automatic archivelog mode, or defer the archivelog destinations that specify the SERVICE= attribute.

ORA-16177: media recovery is not required

ORA-16177: media recovery is not required

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

Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby.

ORA-16176: background dictionary build cannot be running

ORA-16176: background dictionary build cannot be running

Cause: The background process dedicated to dictionary build is active.

Action: wait and try it later.

ORA-16175: cannot shut down database when media recovery is active

ORA-16175: cannot shut down database when media recovery is active

Cause: An attempt was made to shut down a standby database while media recovery was active.

Action: Cancel media recovery to proceed with the shutdown.

ORA-16174: user requested thread or sequence termination of managed recovery

ORA-16174: user requested thread or sequence termination of managed recovery

Cause: The managed standby database recovery operation has been terminated per user specified THROUGH THREAD or SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement.

Action: No action is required.

ORA-16173: incompatible archival network connections active

ORA-16173: incompatible archival network connections active

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

Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation.

ORA-16172: archive logs detected beyond Terminal End-Of-Redo

ORA-16172: archive logs detected beyond Terminal End-Of-Redo

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

Action: none

ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq string-string

ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq string-string

Cause: See alert log for more details

Action: Copy missing archived logs from primary or another standby. Register the logs and re-issue 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.

ORA-16170: Terminal recovery may have left the database in an inconsistent state

ORA-16170: Terminal recovery may have left the database in an inconsistent state

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

Action: Continue standby recovery with additional log shipping from primary.

ORA-16169: LGWR network server invalid parameters

ORA-16169: LGWR network server invalid parameters

Cause: The LGWR network server could not switch to blocking mode

Action: The alert log contains more problem-specific information

ORA-16168: LGWR network server could not switch to blocking mode

ORA-16168: LGWR network server could not switch to blocking mode

Cause: The LGWR network server could not switch to blocking mode

Action: The alert log contains more problem-specific information

ORA-16167: LGWR network server could not switch to non-blocking mode

ORA-16167: LGWR network server could not switch to non-blocking mode

Cause: The LGWR network server could not switch to non-blocking mode

Action: The alert log contains more problem-specific information

ORA-16166: LGWR network server failed to send remote message

ORA-16166: LGWR network server failed to send remote message

Cause: The LGWR network server could not communicate with the remote host

Action: The alert log contains more problem-specific information

ORA-16165: LGWR failed to hear from network server

ORA-16165: LGWR failed to hear from network server

Cause: The LGWR lost its connection to the network server

Action: The alert log contains more problem-specific information

ORA-16164: LGWR network server host detach error

ORA-16164: LGWR network server host detach error

Cause: The LGWR network server could not detach from remote host

Action: The alert log contains more problem-specific information

ORA-16163: LGWR network server host attach error

ORA-16163: LGWR network server host attach error

Cause: The LGWR network server could not attach to remote host

Action: The alert log contains more problem-specific information

ORA-16162: Cannot add new standby databases to protected configuration

ORA-16162: Cannot add new standby databases to protected configuration

Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.

Action: The standby database must be added to the configuration before the primary database is opened.

ORA-16161: Cannot mix standby and online redo log file members for group string

ORA-16161: Cannot mix standby and online redo log file members for group string

Cause: An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile group, or adding an online redo log file member to a standby redo log file group.

Action: Verify the log file group type using the TYPE column of the V$LOG fixed view.

ORA-16160: Cannot change protected standby database configuration

ORA-16160: Cannot change protected standby database configuration

Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode.

Action: The standby database must be added to the configuration before the primary database is opened.

ORA-16159: Cannot change protected standby destination attributes

ORA-16159: Cannot change protected standby destination attributes

Cause: An attempt was made to change the LGWR or ARCH or SYNC or ASYNC attributes for a destination that is participating in the standby protection mode of the database.

Action: No action is required.

ORA-16157: media recovery not allowed following successful FINISH recovery

ORA-16157: media recovery not allowed following successful FINISH recovery

Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed.

Action: Issue one of these operations following a FINISH recocvery: ALTER DATABASE OPEN READ ONLY or ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.

ORA-16156: LGWR archive log dependency not allowed if database is standby protected

ORA-16156: LGWR archive log dependency not allowed if database is standby protected

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

Action: Remove the LGWR archive log dependency and use normal LGWR archival instead.

ORA-16154: suspect attribute: string

ORA-16154: suspect attribute: string

Cause: Use of the indicated attribute is illegal in the given context.

Action: Make the appropriate changes and reissue the statement.

ORA-16152: standby database is in no-data-loss protected mode

ORA-16152: standby database is in no-data-loss protected mode

Cause: The attempted database operation is not allowed while the standby database is in no-data-loss protected mode.

Action: Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement.

ORA-16151: Managed Standby Recovery not available

ORA-16151: Managed Standby Recovery not available

Cause: The attempted operation failed because of a pending CANCEL of the managed standby recovery operation.

Action: Wait for the managed standby recovery session to end. Then retry the operation.

ORA-16150: FINISH recovery performed on another, older standby database

ORA-16150: FINISH recovery performed on another, older standby database

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

Action: No action is required.

ORA-16148: user requested expiration of managed recovery operation

ORA-16148: user requested expiration of managed recovery operation

Cause: The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement.

Action: No action is required.

ORA-16147: standby database referenced by multiple archive log destinations

ORA-16147: standby database referenced by multiple archive log destinations

Cause: Multiple archive log destinations reference the same standby database, using different service names. This is not allowed.

Action: Remove one of the duplicate archive log destinations.

ORA-16146: standby destination control file enqueue unavailable

ORA-16146: standby destination control file enqueue unavailable

Cause: The target standby destination control file is currently unavailable to the Remote File Server (RFS) process. This indicates that the target destination is the primary database itself.

Action: Check for and eliminate the standby destination archive log parameter in question.

ORA-16145: archival for thread# string sequence# string in progress

ORA-16145: archival for thread# string sequence# string in progress

Cause: The indicated archived log file is not available for recovery due to the fact that it is still being archived.

Action: Verify that archival of the indicated log file has completed and reissue the RECOVER STANDBY DATABASE command.

ORA-16143: RFS connections not allowed during or after terminal recovery

ORA-16143: RFS connections not allowed during or after terminal recovery

Cause: An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery.

Action: The primary must not attempt to archive to the standby after a terminal recovery.

ORA-16140: standby online logs have not been recovered

ORA-16140: standby online logs have not been recovered

Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs.

Action: To recover the standby online logs issue the following command: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH. Then re-issue 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.

ORA-16139: media recovery required

ORA-16139: media recovery required

Cause: The database has not been recovered through the end of log stream. Graceful switchover is not possible.

Action: Ensure that the entire log stream has been applied. If appropriate, reissue the graceful switchover command.

ORA-16138: end of log stream not received from primary

ORA-16138: end of log stream not received from primary

Cause: The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible.

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

ORA-16137: No terminal recovery is required

ORA-16137: No terminal recovery is required

Cause: All archived logs have been applied, and there are no current logs to be applied. Terminal recovery is not required.

Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby.

ORA-16136: Managed Standby Recovery not active

ORA-16136: Managed Standby Recovery not active

Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active.

Action: No action is necessary.

ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected mode

ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected mode

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

Action: Make the modification before the database is opened by any instance.

ORA-16134: invalid MANAGED recovery FINISH option

ORA-16134: invalid MANAGED recovery FINISH option

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

Action: Specify either nothing or NOWAIT following FINISH.

ORA-16133: Datafile string has incorrect terminal recovery stamp.

ORA-16133: Datafile string has incorrect terminal recovery stamp.

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

Action: A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery.

ORA-16132: An error occurred during activation of the standby.

ORA-16132: An error occurred during activation of the standby.

Cause: An error occurred during activation of the standby database following a Terminal Recovery.

Action: Check the standby alert log additional information.