ORA-16131: An error occurred during a Terminal Recovery of the standby.

ORA-16131: An error occurred during a Terminal Recovery of the standby.

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

Action: Check the standby alert log additional information.

ORA-16130: supplemental log information is missing from log stream

ORA-16130: supplemental log information is missing from log stream

Cause: Supplemental logging is not enabled at the primary database.

Action: Issue the following command to enable supplemental logging. ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;

ORA-16129: unsupported dml encountered

ORA-16129: unsupported dml encountered

Cause: DML to tables in the SYS schema have been updated and are not part of a DDL operation. This may be due to some DBA activity or DML associated with a kernel PL or SQL request that Logical Standby does not yet support.

Action: Check the DBA_LOGSTDBY_EVENTS table for the name of the table being processed. Possibly use Log Miner to understand the transaction, and provide a compensating transaction on the standby system. Once complete, call DBMS_LOGSTDBY.SKIP_TRANSACTION with the associated transaction id, and resume apply.

ORA-16128: User initiated stop apply successfully completed

ORA-16128: User initiated stop apply successfully completed

Cause: Logical standby was shutdown in an orderly fashion.

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

ORA-16127: stalled waiting for additional transactions to be applied

ORA-16127: stalled waiting for additional transactions to be applied

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

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

ORA-16126: loading table or sequence string

ORA-16126: loading table or sequence string

Cause: Information on the given table or sequence is being loaded into an in memory cache for future use.

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

ORA-16125: large transaction string string string is waiting for more data

ORA-16125: large transaction string string string is waiting for more data

Cause: The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.

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

ORA-16124: transaction string string string is waiting on another transaction

ORA-16124: transaction string string string is waiting on another transaction

Cause: The apply process is waiting to apply additional changes. This transaction likely depends on another.

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

ORA-16123: transaction string string string is waiting for commit approval

ORA-16123: transaction string string string is waiting for commit approval

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

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

ORA-16122: applying large dml transaction at SCN string

ORA-16122: applying large dml transaction at SCN string

Cause: A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN.

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

ORA-16121: applying transaction with commit SCN string

ORA-16121: applying transaction with commit SCN string

Cause: The transaction committed at the given SCN is being applied.

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

ORA-16120: dependencies being computed for transaction at SCN string

ORA-16120: dependencies being computed for transaction at SCN string

Cause: The transaction committed at the given SCN is being analyzed for dependencies.

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

ORA-16119: building transaction at SCN string

ORA-16119: building transaction at SCN string

Cause: The transaction being committed at the given SCN is being prepared for apply.

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

ORA-16117: processing

ORA-16117: processing

Cause: The process is performing its primary function and is not waiting on any significant event.

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

ORA-16116: no work available

ORA-16116: no work available

Cause: The process is idle waiting for additional changes to be made available.

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

ORA-16115: %s or % of LogMiner dictionary loading is done

ORA-16115: %s or % of LogMiner dictionary loading is done

Cause: The process is loading dictionary information from the redo stream. This activity may take a few minutes.

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

ORA-16114: applying DDL transaction with commit SCN string

ORA-16114: applying DDL transaction with commit SCN string

Cause: The process is applying a DDL change that s committed at the given SCN.

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

ORA-16113: applying change to table or sequence string

ORA-16113: applying change to table or sequence string

Cause: The process is applying changes to a specific schema object.

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

ORA-16112: log mining and apply stopping

ORA-16112: log mining and apply stopping

Cause: This logical standby process is cleaning up and stopping Logical Standby apply.

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

ORA-16111: log mining and apply setting up

ORA-16111: log mining and apply setting up

Cause: This logical standby process is setting up to begin processing changes.

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

ORA-16110: user procedure processing of logical standby apply DDL

ORA-16110: user procedure processing of logical standby apply DDL

Cause: A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.

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

ORA-16109: failed to apply log data from previous primary

ORA-16109: failed to apply log data from previous primary

Cause: Log data from previous primary could not be completely applied.

Action: . Then, re-issue command.

ORA-16108: database is no longer a standby database

ORA-16108: database is no longer a standby database

Cause: The current database has already been made a primary database.

Action: Issue 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;

ORA-16107: all log data from primary has been processed

ORA-16107: all log data from primary has been processed

Cause: On the primary system, the log stream has been ended by the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command.

Action: Issue 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;

ORA-16105: Logical Standby is already running in background

ORA-16105: Logical Standby is already running in background

Cause: A Logical Standby apply operation is already running.

Action: none

ORA-16104: invalid Logical Standby option requested

ORA-16104: invalid Logical Standby option requested

Cause: The option requested is not valid.

Action: Check spelling or refer to the Oracle8i SQL Reference manual for the correct statement syntax, then re-enter the request.

ORA-16103: Logical Standby apply must be stopped to allow this operation

ORA-16103: Logical Standby apply must be stopped to allow this operation

Cause: Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.

Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or respecify the operation.

ORA-16102: remote information is not available on the specified primary

ORA-16102: remote information is not available on the specified primary

Cause: The new primary has not completed generating the necessary information for the standby to begin consuming its log stream.

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

ORA-16101: a valid start SCN could not be found

ORA-16101: a valid start SCN could not be found

Cause: An SCN from which to start could not be found.

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

ORA-16100: not a valid Logical Standby database

ORA-16100: not a valid Logical Standby database

Cause: This database has not been completely configured as a Logical Standby database.

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

ORA-16099: internal error ORA-00600 occurred at standby database

ORA-16099: internal error ORA-00600 occurred at standby database

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-16098: inaccessible standby database forced shutdown to protect primary

ORA-16098: inaccessible standby database forced shutdown to protect primary

Cause: No standby database archive log destinations remain accessible and the primary database is in protected no-data-loss mode.

Action: Specify an alternate standby archive log destination in the initialization parameter file.

ORA-16097: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY

ORA-16097: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY

Cause: None

Action: Specify this command to prepare the standby database for switchover

ORA-16096: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY

ORA-16096: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY

Cause: None

Action: Specify this command to prepare the primary database for switchover

ORA-16095: Dependent destination removal for inactivation

ORA-16095: Dependent destination removal for inactivation

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

Action: None required.

ORA-16094: database shutdown during archival operation

ORA-16094: database shutdown during archival operation

Cause: The database was shut down while an online log file archival was active.

Action: None required. The ARCH process is terminated.

ORA-16093: dependent archive log destination is not LGWR-enabled

ORA-16093: dependent archive log destination is not LGWR-enabled

Cause: An archive log destination contains a dependency to another archive log destination that is not enabled for the LGWR process

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

ORA-16092: dependent archive log destination is not active

ORA-16092: dependent archive log destination is not active

Cause: An archive log destination contains a dependency to another archive log destination that is not active

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

ORA-16091: dependent archive log destination already archived

ORA-16091: dependent archive log destination already archived

Cause: An archive log destination contains a dependency to another archive log destination that has previously been archived.

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-16090: archive log to be replaced not created by managed standby process

ORA-16090: archive log to be replaced not created by managed standby process

Cause: An attempt was made to replace an archive log entry that was not originally created by the managed standby operation.

Action: No user action required.

ORA-16089: archive log has already been registered

ORA-16089: archive log has already been registered

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

Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log information.

ORA-16088: archive log has not been completely archived

ORA-16088: archive log has not been completely archived

Cause: An attempt was made to register an archive log that has not been completely archived. The specified archive log may be a current log file.

Action: Specify a completed archive log.

ORA-16087: graceful switchover requires standby or current control file

ORA-16087: graceful switchover requires standby or current control file

Cause: An attempt was made to perform a graceful switchover operation using a backup or clone control file.

Action: Convert the backup control file into a current control file prior to attempting a graceful switchover operation. A clone control file cannot be used for a graceful switchover operation.

ORA-16086: standby database does not contain available standby log files

ORA-16086: standby database does not contain available standby log files

Cause: The primary database is in no data loss mode, but the standby database does not contain any standby log files .

Action: Add one or more standby log files to the standby database. This can be done while the standby database is mounted.

ORA-16084: an apply engine is already running

ORA-16084: an apply engine is already running

Cause: A logical standby apply engine was running when another was created.

Action: Shut down the previous apply engine before starting a new one.

ORA-16083: LogMiner session has not been created

ORA-16083: LogMiner session has not been created

Cause: Logical standby apply engine was started without creating a LogMiner session.

Action: Create a LogMiner session and restart the apply engine.

ORA-16082: logical standby is not initialized correctly

ORA-16082: logical standby is not initialized correctly

Cause: Logical standby apply engine was started but it found inconsistencies in its metadata.

Action: Look in the trace file for more information.

ORA-16081: insufficient number of processes for APPLY

ORA-16081: insufficient number of processes for APPLY

Cause: Logical standby apply engine was started with fewer processes available than needed.

Action: Increase the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_ LOGSTDBY_PARAMETERS view.

ORA-16080: invalid LogMiner session string for APPLY

ORA-16080: invalid LogMiner session string for APPLY

Cause: Logical standby apply engine was started with an invalid LogMiner session identifier.

Action: Fix the problem with the LogMiner session or create a new session.

ORA-16079: standby archival not enabled

ORA-16079: standby archival not enabled

Cause: The standby database does not have archival enabled.

Action: In order to allow the standby database to access the standby log files, the ARCH process must be enabled and active.

ORA-16078: media recovery disabled

ORA-16078: media recovery disabled

Cause: The database is not in ARCHIVELOG mode.

Action: Place the database in ARCHIVELOG mode.

ORA-16076: unknown standby database destination

ORA-16076: unknown standby database destination

Cause: A standby database destination was specified that is not accessed by another instance.

Action: All database instances must access the same standby databases.

ORA-16075: standby database destination mismatch

ORA-16075: standby database destination mismatch

Cause: A standby database destination was specified that is not accessed by another instance.

Action: All database instances must access the same standby databases.

ORA-16074: ARCH processes must be active

ORA-16074: ARCH processes must be active

Cause: There are no active ARCH processes.

Action: It is required that at least one ARCH process be active.

ORA-16073: archiving must be enabled

ORA-16073: archiving must be enabled

Cause: Online log file archiving is disabled.

Action: Enable log file archiving.

ORA-16072: a minimum of one standby database destination is required

ORA-16072: a minimum of one standby database destination is required

Cause: No standby database archive log destinations were specified.

Action: Specify a standby archive log destination in the initialization parameter file.

ORA-16071: dependency archived log file not found string

ORA-16071: dependency archived log file not found string

Cause: The specified archived log file was not found at the indicated standby destination.

Action: Verify the correctness of the dependency archived log file name template specified for the indicated standby destination against the actual dependency archived log file.

ORA-16070: parameter string contains an invalid REGISTER attribute value

ORA-16070: parameter string contains an invalid REGISTER attribute value

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) 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 or S-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).

Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter.

ORA-16069: Archive Log standby database activation identifier mismatch

ORA-16069: Archive Log standby database activation identifier mismatch

Cause: The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database.

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

ORA-16068: redo log file activation identifier mismatch

ORA-16068: redo log file activation identifier mismatch

Cause: The activation identifier of the indicated redo log file does not match the activation identifier of the database.

Action: none