ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST

ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST

Cause: Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.

Action: No action is required.

ORA-16260: Waiting to replace partial or corrupt logfile (thread# string, sequence# string)

ORA-16260: Waiting to replace partial or corrupt logfile (thread# string, sequence# string)

Cause: LogMiner Reader process reached end of a partial logfile or encountered a corrupted block. It is now waiting for the logfile to be recovered and re-registered.

Action: No action necessary. Once the FAL archiver replaces the logfile, standby will automatically restart to process the replaced file.

ORA-16259: Switchover to logical standby requires a log archive destination

ORA-16259: Switchover to logical standby requires a log archive destination

Cause: A valid log archive destination was not found to which the local system could archive the EOR logfile. A minimum of one destination is required.

Action: Ensure all log archive destinations are properly configured and, if applicable, have network connectivity before re-issuing the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY DDL operation.

ORA-16258: marking index unusable due to a constraint violation

ORA-16258: marking index unusable due to a constraint violation

Cause: A constraint violation occurred during the apply of a direct path load. The index will be marked unusable and the apply will be restarted.

Action: No action necessary. See alert log for index schema and name.

ORA-16257: Switchover initiated stop apply successfully completed

ORA-16257: Switchover initiated stop apply successfully completed

Cause: SQL Apply was stopped because of a switchover.

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

ORA-16256: Failure to complete standby redo logfile archival after failover

ORA-16256: Failure to complete standby redo logfile archival after failover

Cause: The standby redo logfiles processed during the failover of a logical standby were not archived.

Action: Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival.

ORA-16255: Log Auto Delete conflicts with another LogMiner session

ORA-16255: Log Auto Delete conflicts with another LogMiner session

Cause: Log Auto Delete cannot be on while another LogMiner session is running on the same database.

Action: Start Logical Standby without Log Auto Delete or destroy other LogMiner sessions first.

ORA-16254: change db_name to string in the client-side parameter file (pfile)

ORA-16254: change db_name to string in the client-side parameter file (pfile)

Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a server parameter file (spfile).

Action: The client-side parameter file must be edited so that db_name is set to the given name before mounting the database again.

ORA-16253: Logical Standby cannot start due to incomplete terminal apply

ORA-16253: Logical Standby cannot start due to incomplete terminal apply

Cause: A previous ACTIVATE of the logical standby failed to complete.

Action: Reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE FINISH APPLY command.

ORA-16252: Rebuild operation not permitted

ORA-16252: Rebuild operation not permitted

Cause: The REBUILD operation is not permitted.

Action: Only on a primary database that has failed to complete the LogMiner dictionary build may the REBUILD operation take place. Reissue the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed to complete.

ORA-16251: LSP1 Background Build not permitted

ORA-16251: LSP1 Background Build not permitted

Cause: The LSP1 background process is not permitted to start because it had previously been attempted.

Action: This is an internal error. Contact Oracle support.

ORA-16250: Failed to acquire starting scn of new log stream

ORA-16250: Failed to acquire starting scn of new log stream

Cause: The starting SCN for the new log stream could not be determined.

Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command.

ORA-16249: Terminal apply failed to complete during failover

ORA-16249: Terminal apply failed to complete during failover

Cause: The logical standby coordinator process terminated abnormally.

Action: Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the abnormal shutdown, and resolve accordingly. Once the problem has been rectified, reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE command to complete the failover.

ORA-16248: RFS connections not permitted during Terminal Apply

ORA-16248: RFS connections not permitted during Terminal Apply

Cause: Writes by RFS are not permitted while Logical Standby is performing Terminal Apply.

Action: Permit any outstanding Logical Standby operations to complete.

ORA-16247: DDL skipped on internal schema

ORA-16247: DDL skipped on internal schema

Cause: Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM. For a complete list of internal schemas ignored by Logical Standby perform the following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt = INTERNAL SCHEMA .

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

ORA-16246: User initiated abort apply successfully completed

ORA-16246: User initiated abort apply successfully completed

Cause: SQL Apply was stopped using the abort option.

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

ORA-16245: paging in transaction string, string, string

ORA-16245: paging in transaction string, string, string

Cause: Builder process is paging in transactions from disk.

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

ORA-16244: taking checkpoint and paging out string bytes to disk

ORA-16244: taking checkpoint and paging out string bytes to disk

Cause: Builder process is taking a checkpoint to advance restart_scn

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

ORA-16243: paging out string bytes of memory to disk

ORA-16243: paging out string bytes of memory to disk

Cause: Builder process is paging out momery to free up space in lcr cache.

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

ORA-16242: Processing logfile (thread# string, sequence# string)

ORA-16242: Processing logfile (thread# string, sequence# string)

Cause: Reader process is processing the logfile.

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

ORA-16241: Waiting for gap logfile (thread# string, sequence# string)

ORA-16241: Waiting for gap logfile (thread# string, sequence# string)

Cause: Reader process is idle waiting for the logfile to fill the log sequence gap.

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

ORA-16240: Waiting for logfile (thread# string, sequence# string)

ORA-16240: Waiting for logfile (thread# string, sequence# string)

Cause: Reader process is idle waiting for additional logfile to be available.

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

ORA-16239: IMMEDIATE option not available without standby redo logs

ORA-16239: IMMEDIATE option not available without standby redo logs

Cause: The IMMEDIATE option cannot be used without standby redo logs.

Action: Do not specify the IMMEDIATE option unless standby redo logs are being used.

ORA-16238: attempt to use version 9 log

ORA-16238: attempt to use version 9 log

Cause: Version 9 log files are not supported.

Action: Use log files of a supported version.

ORA-16237: SGA specified for Logical Standby is too small

ORA-16237: SGA specified for Logical Standby is too small

Cause: MAX_SGA must be at least 10 Megabytes for proper functioning of Logical Standby.

Action: Specify the value of MAX_SGA to be greater than or equal to 10Mb. Alternatively, increase the shared_pool_size or sga_target so that 1 or 4 of it will amount to 10 Megabytes.

ORA-16236: Logical Standby metadata operation in progress

ORA-16236: Logical Standby metadata operation in progress

Cause: The requested operation failed because a Logical Standby metadata operation, such as DBMS_LOGSTDBY.SET_TABLESPACE or DBMS_ LOGSTDBY.INSTANTIATE_TABLE, has not finished.

Action: Wait for the Logical Standby metadata operation to finish, then re-enter or respecify the operation.

ORA-16235: DDL skipped because import has occurred

ORA-16235: DDL skipped because import has occurred

Cause: An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export.

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

ORA-16234: restarting to reset Logical Standby apply

ORA-16234: restarting to reset Logical Standby apply

Cause: Logical Standby encountered a work load that required a restart to properly reschedule.

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

ORA-16233: The table string.string is unsupported now

ORA-16233: The table string.string is unsupported now

Cause: Table was previously supported but now is unsupported due to altered datatype or storage attribute definitions.

Action: None.

ORA-16232: adding Logical Standby skip entry for table string.string

ORA-16232: adding Logical Standby skip entry for table string.string

Cause: Table was previously unsupported due to datatype or storage attribute definitions. Table is now capable of being supported.

Action: To have Logical Standby maintain the table, import that table directly from the primary.

ORA-16231: DDL barrier

ORA-16231: DDL barrier

Cause: Logical Standby was holding back changes until dependent changes were applied.

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

ORA-16230: committing transaction string string string

ORA-16230: committing transaction string string string

Cause: Logical Standby apply was committing changes for the given transaction.

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

ORA-16229: PDML child string string string for parent string string string cannot be skipped.

ORA-16229: PDML child string string string for parent string string string cannot be skipped.

Cause: A request was made to skip a parallel DML child transaction id. This is not supported.

Action: Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove the child transaction id, then specify the parent transaction id using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate.

ORA-16228: Insufficient recovery for logical standby

ORA-16228: Insufficient recovery for logical standby

Cause: Insufficient amount of recovery was run for logical standby instantiation.

Action: Continue to recover the database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE.

ORA-16227: DDL skipped due to missing object

ORA-16227: DDL skipped due to missing object

Cause: A table or other database object upon which this DDL depends is not defined on the Logical Standby database.

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

ORA-16226: DDL skipped due to lack of support

ORA-16226: DDL skipped due to lack of support

Cause: Logical Standby does not support this type of DDL in this version, so the DDL is skipped.

Action: The DBA may apply the DDL explicitly at a later time or a procedure to handle this type of DDL can be created. see DBMS_LOGSTDBY.SKIP procedure for details.

ORA-16225: Missing LogMiner session name for Streams

ORA-16225: Missing LogMiner session name for Streams

Cause: An attempt was made to register the log file for Streams without a specified LogMiner session name.

Action: Specify a valid LogMiner session name to which the log file will be registered.

ORA-16224: Database Guard is enabled

ORA-16224: Database Guard is enabled

Cause: Operation could not be performed because database guard is enabled

Action: Verify operation is correct and disable database guard

ORA-16223: DDL skipped, unsupported in current version

ORA-16223: DDL skipped, unsupported in current version

Cause: The given DDL statement was not supported in the current version of Logical Standby and was skipped.

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

ORA-16222: automatic Logical Standby retry of last action

ORA-16222: automatic Logical Standby retry of last action

Cause: A failure occurred while running Logical Standby apply. A new attempt is automatically being made by Logical Standby apply.

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

ORA-16221: history table synchronization error

ORA-16221: history table synchronization error

Cause: internal error.

Action: This is an internal error. Contact Oracle support.

ORA-16220: no failed transaction found

ORA-16220: no failed transaction found

Cause: No failed transaction was found.

Action: Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command without the SKIP FAILED TRANSACTION option.

ORA-16219: This database is not preparing to switch over.

ORA-16219: This database is not preparing to switch over.

Cause: The database was not preparing to switch over. Therefore, it was not possible to cancel the SWITCHOVER command.

Action: Preparing for the SWITCHOVER command can be accomplished with the ALTER DATABASE PREPARE TO SWITCHOVER command.

ORA-16218: This database is already preparing to switch over.

ORA-16218: This database is already preparing to switch over.

Cause: The database was already preparing to switch over and was not able to accomodate another prepare attempt.

Action: Cancel the current prepare attempt with the ALTER DATABASE PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare request.

ORA-16217: prepare to switchover has not completed

ORA-16217: prepare to switchover has not completed

Cause: An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but the prepare activity did not complete.

Action: Verify that the standby was prepared properly. You may cancel the prepare and perform an unprepared switchover which requires a database link to complete. Or reissue the prepare operation on the standby.

ORA-16216: Log stream sequence error

ORA-16216: Log stream sequence error

Cause: The log stream being processed did not follow the last processed stream.

Action: If the database is in an active configuration, issue an ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY command to synchronize log stream data with the current primary database. If the database is not in an active configuration, manually add the next dictionary-begin logfile that followed the previous log stream.

ORA-16215: history metadata inconsistency

ORA-16215: history metadata inconsistency

Cause: internal error.

Action: This is an internal error. Contact Oracle support.

ORA-16214: apply stalled for apply delay

ORA-16214: apply stalled for apply delay

Cause: A delay has been specified on the primary database for this destination.

Action: Either turn off the delay on the primary or use DBMS_ LOGSTDBY.APPLY_UNSET( APPLY_DELAY ); to override.

ORA-16213: ddl encountered, stopping apply engine

ORA-16213: ddl encountered, stopping apply engine

Cause: stop_on_ddl callout specified and DDL was encountered.

Action: Either disable stop_on_ddl callout or remove DDL.

ORA-16212: number processes specified for APPLY is too great

ORA-16212: number processes specified for APPLY is too great

Cause: Logical standby apply engine was started with more processes requested than are available.

Action: Adjust 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-16211: unsupported record found in the archived redo log

ORA-16211: unsupported record found in the archived redo log

Cause: Log apply services encountered a record in the archived redo log that could not be interpreted.

Action: 1. Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table on the standby database or simply drop the table if it s unimportant. 2. ALTER DATABASE START LOGICAL STANDBY APPLY; 3. Examine the current_scn column in the DBA_LOGSTDBY_EVENTS view to determine which log file contains the unsupported record. 4. Provide the log file to Oracle Support Services.

ORA-16210: Logical standby coordinator process terminated with error

ORA-16210: Logical standby coordinator process terminated with error

Cause: The logical standby coordinator process terminated abnormally.

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-16209: Logical standby dictionary build failed to complete.

ORA-16209: Logical standby dictionary build failed to complete.

Cause: The logical standby dictionary build process terminated abnormally.

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-16208: Logical standby dictionary build failed to start.

ORA-16208: Logical standby dictionary build failed to start.

Cause: Failure to start the logical standby dictionary build process (LSP1)

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-16207: Logical standby dictionary build not permitted.

ORA-16207: Logical standby dictionary build not permitted.

Cause: A dictionary build is currently in progress. Only one build can be active at a time.

Action: Wait for the active build to complete before invoking a new build.

ORA-16206: database already configured as Logical Standby database

ORA-16206: database already configured as Logical Standby database

Cause: This database has been previously configured as a Logical Standby database. A Logical Standby database is not capable of processing the requested operation.

Action: Ensure that you entered the command on the correct database as this database is a Logical Standby and is not capable of servicing the request.

ORA-16205: DDL skipped due to skip setting

ORA-16205: DDL skipped due to skip setting

Cause: A setting in the logical standby skip table indicates that this type of DDL should always be skipped.

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

ORA-16204: DDL successfully applied

ORA-16204: DDL successfully applied

Cause: A DDL statement has successfully commited on the logical standby database.

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

ORA-16203: Unable to interpret skip procedure return values

ORA-16203: Unable to interpret skip procedure return values

Cause: The skip procedure returned conflicting or invalid values.

Action: Ensure that the new_statement output parameter is non-NULL when returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE and NULL otherwise. Also ensure SKIP_ACTION is specified correctly.

ORA-16202: Skip procedure requested to replace statement

ORA-16202: Skip procedure requested to replace statement

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

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