Friday, 23 March 2012

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.