{"id":2254,"date":"2016-09-20T21:17:56","date_gmt":"2016-09-20T18:17:56","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=2254"},"modified":"2017-02-15T21:19:01","modified_gmt":"2017-02-15T18:19:01","slug":"oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-16200-to-ora-16400","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-16200-to-ora-16400\/","title":{"rendered":"Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16200 to ORA-16400"},"content":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16200 to ORA-16400<\/strong><\/p>\n

\n
ORA-16200: Skip procedure requested to skip statement<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby called a skip procedure that requested for a particular statement not to be applied.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16201: Skip procedure requested to apply statement<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby called a skip procedure that requested for a particular statement to be applied.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16202: Skip procedure requested to replace statement<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16203: Unable to interpret skip procedure return values<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The skip procedure returned conflicting or invalid values.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16204: DDL successfully applied<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A DDL statement has successfully commited on the logical standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span>
\n<\/p>\n

\n
<\/a> ORA-16205: DDL skipped due to skip setting<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A setting in the logical standby skip table indicates that this type of DDL should always be skipped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16206: database already configured as Logical Standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This database has been previously configured as a Logical Standby database. A Logical Standby database is not capable of processing the requested operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that you entered the command on the correct database as this database is a Logical Standby and is not capable of servicing the request.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16207: Logical standby dictionary build not permitted.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A dictionary build is currently in progress. Only one build can be active at a time.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait for the active build to complete before invoking a new build.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16208: Logical standby dictionary build failed to start.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Failure to start the logical standby dictionary build process (LSP1)<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16209: Logical standby dictionary build failed to complete.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The logical standby dictionary build process terminated abnormally.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16210: Logical standby coordinator process terminated with error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The logical standby coordinator process terminated abnormally.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16211: unsupported record found in the archived redo log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Log apply services encountered a record in the archived redo log that could not be interpreted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a01. 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16212: number of processes specified for SQL Apply is too great<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby apply engine was started with more processes requested than are available.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Adjust the values of the initialization parameters PROCESSES or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view. If you did not specify MAX_SERVERS, but instead specified PREPARE_SERVERS and APPLY_SERVERS through the dbms_logstdby.apply_set procedure, you will need to decrease either one or both of them.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16213: ddl encountered, stopping apply engine<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0stop_on_ddl callout specified and DDL was encountered.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either disable stop_on_ddl callout or remove DDL.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16214: apply stalled for apply delay<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A delay has been specified on the primary database for this destination.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either turn off the delay on the primary or use DBMS_LOGSTDBY.APPLY_UNSET(‘APPLY_DELAY’); to override.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16215: history metadata inconsistency<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0internal error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is an internal error. Contact Oracle support.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16216: Log stream sequence error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The log stream being processed did not follow the last processed stream.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If 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 log file that followed the previous log stream.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16217: prepare to switchover has not completed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but the prepare activity did not complete.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16218: This database is already preparing to switch over.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database was already preparing to switch over and was not able to accomodate another prepare attempt.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Cancel the current prepare attempt with the ALTER DATABASE PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare request.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16219: This database is not preparing to switch over.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database was not preparing to switch over. Therefore, it was not possible to cancel the SWITCHOVER command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Preparing for the SWITCHOVER command can be accomplished with the ALTER DATABASE PREPARE TO SWITCHOVER command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16220: no failed transaction found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0No failed transaction was found.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command without the SKIP FAILED TRANSACTION option.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16221: history table synchronization error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0internal error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is an internal error. Contact Oracle support.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16222: automatic Logical Standby retry of last action<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A failure occurred while running Logical Standby apply. A new attempt is automatically being made by Logical Standby apply.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16223: DDL skipped, unsupported in current version<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The given DDL statement was not supported in the current version of Logical Standby and was skipped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16224: Database Guard is enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Operation could not be performed because database guard is enabled<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify operation is correct and disable database guard<\/span><\/span><\/p>\n

\n
<\/a> ORA-16225: Missing LogMiner session name for Capture<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to register the log file for Capture without a specified LogMiner session name.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a valid LogMiner session name to which the log file will be registered.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16226: DDL skipped due to lack of support<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical Standby does not support this type of DDL in this version, so the DDL is skipped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16227: DDL skipped due to missing object<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A table or other database object upon which this DDL depended was not defined on the Logical Standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16228: Insufficient recovery for logical standby<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Insufficient amount of recovery was run for logical standby instantiation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Continue to recover the database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16229: PDML child\u00a0string<\/i>\u00a0string<\/i>\u00a0string<\/i>\u00a0for parent\u00a0string<\/i>\u00a0string<\/i>\u00a0string<\/i>\u00a0cannot be skipped.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A request was made to skip a parallel DML child transaction id. This is not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove the child transaction id, then specify the parent transaction id using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16230: committing transaction\u00a0string<\/i>\u00a0string<\/i>\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical Standby apply was committing changes for the given transaction.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16232: adding Logical Standby skip entry for table\u00a0string<\/i>.string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Table was previously unsupported due to datatype or storage attribute definitions. Table is now capable of being supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0To have Logical Standby maintain the table, import that table directly from the primary.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16233: The table\u00a0string<\/i>.string<\/i>\u00a0is unsupported now<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Table was previously supported but now is unsupported due to altered datatype or storage attribute definitions.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-16234: restarting to reset Logical Standby apply<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical Standby encountered a work load that required a restart to properly reschedule.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16235: DDL skipped because import has occurred<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16236: Logical Standby metadata operation in progress<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The requested operation failed because an incompatible Logical Standby metadata operation such as DBMS_LOGSTDBY.SET_TABLESPACE, DBMS_LOGSTDBY.APPLY_SET or DBMS_LOGSTDBY.INSTANTIATE_TABLE was still running.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait for the incompatible Logical Standby metadata operation to finish, then reenter or respecify the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16237: SGA specified for Logical Standby is too small<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0MAX_SGA must be at least 10 Megabytes for proper functioning of Logical Standby.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the value of MAX_SGA to be greater than or equal to 10Mb. Alternatively, increase the shared_pool_size\/sga_target so that 1\/4 of it will amount to 10 Megabytes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16238: attempt to use version 9 log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Version 9 log files are not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use log files of a supported version.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16239: IMMEDIATE option not available without standby redo logs<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The IMMEDIATE option cannot be used without standby redo logs.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not specify the IMMEDIATE option unless standby redo logs are being used.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16240: Waiting for log file (thread#\u00a0string<\/i>, sequence#\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Process is idle waiting for additional log file to be available.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16241: Waiting for gap log file (thread#\u00a0string<\/i>, sequence#\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Reader process was idle waiting for the log file to fill the log sequence gap.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16242: Processing log file (thread#\u00a0string<\/i>, sequence#\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Reader process was processing the log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16243: paging out\u00a0string<\/i>\u00a0bytes of memory to disk<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Builder process is paging out momery to free up space in lcr cache.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16245: change db_name to\u00a0string<\/i>\u00a0in the server-side parameter file (SPFILE)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a modifiable server parameter file (SPFILE).<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The server-side parameter file must be modified so that db_name is set to the given name before mounting the database again. You must do this by executing CREATE PFILE FROM SPFILE, editing the resulting text parameter file, and then executing CREATE SPFILE FROM PFILE.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16246: User initiated abort apply successfully completed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0SQL Apply was stopped using the abort option.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16247: DDL skipped on internal schema<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical 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’.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16248: RFS connections not permitted during Terminal Apply<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Writes by RFS are not permitted while Logical Standby is performing Terminal Apply.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Permit any outstanding Logical Standby operations to complete.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16249: Terminal apply failed to complete during failover<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The logical standby coordinator process terminated abnormally.”<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Examine 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16250: Failed to acquire starting scn of new log stream<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The starting SCN for the new log stream could not be determined.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16251: LSP1 Background Build not permitted<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The LSP1 background process is not permitted to start because it had previously been attempted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is an internal error. Contact Oracle support.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16252: Rebuild operation not permitted<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The REBUILD operation is not permitted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Only 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16253: Logical standby cannot start due to a prior, incomplete operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A failure during a prior failover or configuration-related operation left the logical standby in an inconsistent state.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Identify and reissue the operation before attempting to restart the logical standby apply engine.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16254: change db_name to\u00a0string<\/i>\u00a0in the client-side parameter file (pfile)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a server parameter file (spfile).<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The client-side parameter file must be edited so that db_name is set to the given name before mounting the database again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16255: Log Auto Delete conflicts with another LogMiner session<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Log Auto Delete cannot be on while another LogMiner session is running on the same database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Start Logical Standby without Log Auto Delete or destroy other LogMiner sessions first.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16256: Failure to complete standby redo log file archival after failover<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The standby redo log files processed during the failover of a logical standby were not archived.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16257: Switchover initiated stop apply successfully completed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0SQL Apply was stopped because of a switchover.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16258: marking index unusable due to a constraint violation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A constraint violation occurred during the apply of a direct path load. The index will be marked unusable and the apply will be restarted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. See alert log for index schema and name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16259: Switchover to logical standby requires a log archive destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A valid log archive destination was not found to which the local system could archive the end of redo (EOR) log file. A minimum of one destination is required.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure all log archive destinations are properly configured and, if applicable, have network connectivity before reissuing the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY DDL operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16260: Waiting to replace partial or corrupt log file (thread#\u00a0string<\/i>, sequence#\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0LogMiner Reader process reached the end of a partial log file or encountered a corrupted block. It is now waiting for the log file to be recovered and reregistered.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. Once the fetch archive log (FAL) archiver replaces the log file, standby will automatically restart to process the replaced file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16261: Identification key mismatch for table “string<\/i>“.”string<\/i>“.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Internal error in SQL Apply.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16262: Invalid value specified for Logical Standby parameter<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The value specified in APPLY_SET is invalid for the parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify correct parameter value. Please refer to documentation on DBMS_LOGSTDBY PL\/SQL package for details.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16263: Dynamic parameters can only be set on SQL apply instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempt to set a Logical standby dynamic parameter on an instacne other than where SQL apply coordinator is running.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Connect to the instance where SQL apply coordinator is running and reissue the statement.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16264: invalid value for PREPARE_SERVERS parameter<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0attempt to set PREPARE_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0set PREPARE_SERVERS parameter to a non zero value and or increase MAX_SERVERS parameter accordingly.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16265: Unsupported PL\/SQL procedure encountered<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Apply encountered an unsupported procedure from an Oracle supplied PL\/SQL package that is otherwise supported<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either add a skip rule for this procedure or manually apply the procedure and restart apply skipping the failed transaction Please refer to documentation on the PL\/SQL package for details.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16266: Cannot instantiate a Logical Standby from another Logical Standby<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An instantiation of a Logical Standby has been attempted for another database with the Logical Standby role, which is not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Instantiate a Logical Standby database only from a Primary Database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16267: Cannot instantiate a Logical Standby during a switchover<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An instantiation of a Logical Standby has been attempted for a primary database that is in the middle of a switchover.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Execute ALTER DATABASE PREPARE TO SWITCHOVER CANCEL to cancel the switchover, and attempt the instantiation again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16268: user procedure processing of logical standby apply PL\/SQL<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A user-provided stored procedure was called to inspect a PL\/SQL statement prior to the statement being processed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16269: PL\/SQL procedure skipped due to failure on primary database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Because the PL\/SQL procedure failed when executed on the primary database, it could not be executed on the standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This informational statement is provided to record the event for diagnostic purposes. The failed PL\/SQL procedure needs to be investigated to ensure it did not commit interesting data before it failed.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16270: PL\/SQL procedure skipped due to unmaintained standby objects<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Because the PL\/SQL procedure manipulated objects not being maintained by the standby database, it was skipped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16271: PL\/SQL successfully applied<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A PL\/SQL procedure was successfully applied on the logical standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16272: PL\/SQL procedure skipped due to skip setting<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A setting in the logical standby skip table indicated that this PL\/SQL procedure should always be skipped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16273: invalid value for APPLY_SERVERS parameter<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0attempt to set APPLY_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0set APPLY_SERVERS parameter to a non zero value or increase MAX_SERVERS parameter accordingly.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16274: failure to perform operation on all Oracle RAC instances<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One or more instances encountered an error while performing an operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure every instance in the Oracle RAC meets the requirements for the operation, and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16275: prior failed CTAS detected and pre-existing table dropped<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During the processing of a CTAS operation, an existing empty table with the same name and attributes as the CTAS source table was found, and the table was dropped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16276: specified database link does not correspond to primary database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database link specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE did not link to the primary database for this logical standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a database link that corresponds to the primary database for this logical standby database. The link should have privileges to read and lock the table being instantiated, as well as the SELECT_CATALOG_ROLE.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16277: specified table is not supported by logical standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE to instantiate an unsupported table on the logical standby database. Tables with unsupported data types cannot be replicated to a logical standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a table which is not listed in the DBA_LOGSTDBY_UNSUPPORTED_TABLE view.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16278: specified table has a multi-object skip rule defined<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A table that is instantiated via DBMS_LOGSTDBY.INSTANTIATE_TABLE must not have any skip rules defined with wildcard characters.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Remove or rewrite any skip rules defined for the specified table so that they no longer contain wildcard characters, or no longer affect the specified table.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16279: supplied dblink does not have sufficient privileges<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A dblink was specified that lacked one or more of the CONNECT, RESOURCE, or SELECT_CATALOG_ROLE roles or that connects to a user with insufficient privileges to lock the table.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Grant the necessary privileges to the dblink and the user to which the dblink connects and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16280: cannot change master key on a logical standby database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change the master key for transparent data encryption on a logical standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Set GUARD to NONE and reissue the command. This prevents you from replicating tables with encrypted columns from the primary database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16281: missing identification key for table “string<\/i>“.”string<\/i>“.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0No identification key was created for specified table.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create a primakey key or unique index for specified table.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16282: operation not permitted during rolling upgrade<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operation was attempted that is not supported during a rolling upgrade.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation upon completion of the upgrade.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16283: operation not permitted on non-apply instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operation was attempted that is not supported since it requires a running logical apply on the local instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation on the instance on which the apply engine is running.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16284: timed out waiting for an in-progress operation to complete<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operation timed out waiting for another operation to complete.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation when the in-progress operation has completed.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16285: operation not permitted due to inconsistent role state<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A prior attempt to change the role of this database has failed before the new role state could be fully committed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the previously attempted role-related operation before attempting the current operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16286: operation not permitted due to lack of synchronized destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A synchronized log archive destination was not found to which the end-of-redo log file could be archived.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Before re-attempting the operation, wait at least one minute for the Remote File Server to automatically recover any missing log files or manually recover and register any missing log files with logical standby.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16287: operation not permitted due to active apply state<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operation was attempted that was not supported while the logical standby database had an active apply state.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Confirm the procedures used to configure the logical standby database. Procedures which attempt to reconfigure a logical standby database for a new primary database may encounter this error if an error in a preliminary step was encountered.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16288: DDL skipped due to missing edition “string<\/i>“<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The edition in which the DDL was performed on the primary did not exist on the standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16289: unable to access Pluggable Database “string<\/i>“<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby attempted to access a Pluggable Database that did not exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create or plug in the specified Pluggable Database or add an appropriate skip rule and then restart logical standby.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16290: cannot alter the session logical replication state within a transaction<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A transaction was already in progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Commit or rollback the transaction and then reexecute.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16291: operation not permitted due to incomplete setup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operation was denied due to the logical standby being in a transitional state.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Perform any multistep procedures such as instantiation, switchover, or failover to completion as written in the documentation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16292: cannot replicate ALTER TABLE ADD COLUMN with sequence default value<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The logical standby database attempted to replicate an unsupported DDL statement. The DDL added a column with a sequence as the default.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The table must be re-instantiated from the primary database using DBMS_LOGSTDBY.INSTANTIATE_TABLE().<\/span><\/span><\/p>\n

\n
<\/a> ORA-16300: LSBY architected tracing event<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-16302: extended data type support is not supported for specified table<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that was not supported for such an operation. The table either does not have a primary key or it has a data type not supported by this procedure.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a table for which support exists in EDS_ADD_TABLE.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16303: specified table already has extended data type support<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that already had EDS added on the local database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-16304: procedure must first be called on primary database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE on a logical standby database without having first called it on the primary database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Call DBMS_LOGSTDBY.EDS_ADD_TABLE on the primary database and then retry on the standby.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16305: procedure not supported on a logical standby<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A call was made to DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on a logical standby database which can only be called on a primary database<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Call DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on the primary database<\/span><\/span><\/p>\n

\n
<\/a> ORA-16306: specified table does not have a primary key<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that did not have a primary key.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Add a primary key and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16307: TSE key\u00a0string<\/i>\u00a0successfully applied<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An ALTER SYSTEM SET ENCRYPTION KEY statement was successfully committed on the logical standby database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16308: specified table has extended data type support<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE for a table that is being maintained by extended data type support.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Call DBMS_LOGSTDBY.EDS_REMOVE_TABLE followed by either DBMS_LOGSTDBY.EDS_ADD_TABLE or a retry of the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16309: extended data type support evolve operation not yet started<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A call was made to finish an extended data type support evolve operation without having first started the operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Call DBMS_LOGSTDBY.EDS_EVOLVE_MANUAL with START option and then retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16310: extended data type support evolve operation in progress<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An extended data type support evolve operation was started but not yet completed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait a few seconds and retry the command if automatic evolve has been enabled or call DBMS_LOGSTDBY.EDS_EVOLVE_MANUAL with the FINISH option and then retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16311: materialized view log already exists<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table with a LOB that requires the creation of a specifically-defined materialized view log but one already exists.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Drop the existing materialized view log and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16330: error in container “string<\/i>“<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operation was attempted on a container and an error occurred.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Address the failure condition and then retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16331: container “string<\/i>” is not open<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operation was attempted on a container. However, the container was not open.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Open the container and then retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16332: logical standby encountered non-fatal error ORA-string<\/i>\u00a0during DDL execution<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logical standby apply encountered a non-fatal error during DDL execution and continued to process subsequent transactions.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This error is informational only. No user action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16333: _MAX_LOG_LOOKBACK parameter not sufficiently larger than MAX_SGA<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0_MAX_LOG_LOOKBACK or MAX_SGA parameter was set to a value that will lead to decreased performance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reset parameters such that _MAX_LOG LOOKBACK is at least 5 times the value of MAX_SGA.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16334: skip procedure does not exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified skip procedure did not exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that the specified skip procedure exists and is accessible by the calling user.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16397: creation of global temporary table failed on Oracle Active Data Guard standby\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Creation of global temporary table failed due to the specified reason.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Run the statement after fixing the condition that caused the failure.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16398: online log has been reused and archived log cannot be found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ASYNC redo transport was unable to find either an online log or archived redo log that represents the current live redo sequence number.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16399: current redo has moved to a new branch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A new branch was detected by ASYNC redo transport. No further redo will be transferred from the old branch. ASYNC redo transport will commence on the new branch.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action is required.<\/span><\/span><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16200 to ORA-16400 ORA-16200: Skip procedure requested to skip statement Cause:\u00a0Logical standby called a skip procedure that requested for a particular statement not to be applied. Action:\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16201: Skip procedure requested to…<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[54],"class_list":["post-2254","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-Am","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2254","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/comments?post=2254"}],"version-history":[{"count":1,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2254\/revisions"}],"predecessor-version":[{"id":2255,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2254\/revisions\/2255"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=2254"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=2254"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=2254"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}