Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16200 to ORA-16400
- ORA-16200: Skip procedure requested to skip statement
Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: Logical standby called a skip procedure that requested for a particular statement to be applied.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: Logical standby apply engine was started with more processes requested than are available.
Action: Adjust 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.
Cause: stop_on_ddl callout specified and DDL was encountered.
Action: Either disable stop_on_ddl callout or remove DDL.
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.
Cause: internal error.
Action: This is an internal error. Contact Oracle support.
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 log file that followed the previous log stream.
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.
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.
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.
Cause: No failed transaction was found.
Action: Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command without the SKIP FAILED TRANSACTION option.
Cause: internal error.
Action: This is an internal error. Contact Oracle support.
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.
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.
Cause: Operation could not be performed because database guard is enabled
Action: Verify operation is correct and disable database guard
Cause: An attempt was made to register the log file for Capture without a specified LogMiner session name.
Action: Specify a valid LogMiner session name to which the log file will be registered.
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.
Cause: A table or other database object upon which this DDL depended was not defined on the Logical Standby database.
Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.
Cause: Insufficient amount of recovery was run for logical standby instantiation.
Action: Continue to recover the database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE.
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.
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.
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.
Cause: Table was previously supported but now is unsupported due to altered datatype or storage attribute definitions.
Action: None
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.
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.
Cause: The 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.
Action: Wait for the incompatible Logical Standby metadata operation to finish, then reenter or respecify the operation.
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/sga_target so that 1/4 of it will amount to 10 Megabytes.
Cause: Version 9 log files are not supported.
Action: Use log files of a supported version.
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.
Cause: Process is idle waiting for additional log file to be available.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
Cause: Reader process was idle waiting for the log file to fill the log sequence gap.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
Cause: Reader process was processing the log file.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
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.
Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a modifiable server parameter file (SPFILE).
Action: The 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.
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.
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.
Cause: Writes by RFS are not permitted while Logical Standby is performing Terminal Apply.
Action: Permit any outstanding Logical Standby operations to complete.
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.
Cause: The starting SCN for the new log stream could not be determined.
Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command.
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.
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.
Cause: A failure during a prior failover or configuration-related operation left the logical standby in an inconsistent state.
Action: Identify and reissue the operation before attempting to restart the logical standby apply engine.
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.
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.
Cause: The standby redo log files processed during the failover of a logical standby were not archived.
Action: Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival.
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.
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.
Cause: A 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.
Action: Ensure 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.
Cause: LogMiner 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.
Action: No action necessary. Once the fetch archive log (FAL) archiver replaces the log file, standby will automatically restart to process the replaced file.
Cause: Internal error in SQL Apply.
Action: Contact Oracle Support Services.
Cause: The value specified in APPLY_SET is invalid for the parameter.
Action: Specify correct parameter value. Please refer to documentation on DBMS_LOGSTDBY PL/SQL package for details.
Cause: Attempt to set a Logical standby dynamic parameter on an instacne other than where SQL apply coordinator is running.
Action: Connect to the instance where SQL apply coordinator is running and reissue the statement.
Cause: attempt to set PREPARE_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased.
Action: set PREPARE_SERVERS parameter to a non zero value and or increase MAX_SERVERS parameter accordingly.
Cause: Apply encountered an unsupported procedure from an Oracle supplied PL/SQL package that is otherwise supported
Action: Either 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.
Cause: An instantiation of a Logical Standby has been attempted for another database with the Logical Standby role, which is not supported.
Action: Instantiate a Logical Standby database only from a Primary Database.
Cause: An instantiation of a Logical Standby has been attempted for a primary database that is in the middle of a switchover.
Action: Execute ALTER DATABASE PREPARE TO SWITCHOVER CANCEL to cancel the switchover, and attempt the instantiation again.
Cause: A user-provided stored procedure was called to inspect a PL/SQL statement prior to the statement 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.
Cause: Because the PL/SQL procedure failed when executed on the primary database, it could not be executed on the standby database.
Action: This 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.
Cause: Because the PL/SQL procedure manipulated objects not being maintained by the standby database, it was skipped.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
Cause: A PL/SQL procedure was successfully applied on the logical standby database.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: A setting in the logical standby skip table indicated that this PL/SQL procedure should always be skipped.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: attempt to set APPLY_SERVERS parameter to zero or to a value which would require MAX_SERVERS to be increased.
Action: set APPLY_SERVERS parameter to a non zero value or increase MAX_SERVERS parameter accordingly.
Cause: One or more instances encountered an error while performing an operation.
Action: Ensure every instance in the Oracle RAC meets the requirements for the operation, and retry the operation.
Cause: During 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.
Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.
Cause: The database link specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE did not link to the primary database for this logical standby database.
Action: Specify 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.
Cause: A 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.
Action: Specify a table which is not listed in the DBA_LOGSTDBY_UNSUPPORTED_TABLE view.
Cause: A table that is instantiated via DBMS_LOGSTDBY.INSTANTIATE_TABLE must not have any skip rules defined with wildcard characters.
Action: Remove 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.
Cause: A 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.
Action: Grant the necessary privileges to the dblink and the user to which the dblink connects and retry the operation.
Cause: An attempt was made to change the master key for transparent data encryption on a logical standby database.
Action: Set GUARD to NONE and reissue the command. This prevents you from replicating tables with encrypted columns from the primary database.
Cause: No identification key was created for specified table.
Action: Create a primakey key or unique index for specified table.
Cause: An operation was attempted that is not supported during a rolling upgrade.
Action: Retry the operation upon completion of the upgrade.
Cause: An operation was attempted that is not supported since it requires a running logical apply on the local instance.
Action: Retry the operation on the instance on which the apply engine is running.
Cause: An operation timed out waiting for another operation to complete.
Action: Retry the operation when the in-progress operation has completed.
Cause: A prior attempt to change the role of this database has failed before the new role state could be fully committed.
Action: Retry the previously attempted role-related operation before attempting the current operation.
Cause: A synchronized log archive destination was not found to which the end-of-redo log file could be archived.
Action: Before 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.
Cause: An operation was attempted that was not supported while the logical standby database had an active apply state.
Action: Confirm 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.
Cause: The edition in which the DDL was performed on the primary did not exist on the standby database.
Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes.
Cause: Logical standby attempted to access a Pluggable Database that did not exist.
Action: Create or plug in the specified Pluggable Database or add an appropriate skip rule and then restart logical standby.
Cause: A transaction was already in progress.
Action: Commit or rollback the transaction and then reexecute.
Cause: An operation was denied due to the logical standby being in a transitional state.
Action: Perform any multistep procedures such as instantiation, switchover, or failover to completion as written in the documentation.
Cause: The logical standby database attempted to replicate an unsupported DDL statement. The DDL added a column with a sequence as the default.
Action: The table must be re-instantiated from the primary database using DBMS_LOGSTDBY.INSTANTIATE_TABLE().
- ORA-16300: LSBY architected tracing event
- ORA-16302: extended data type support is not supported for specified table
Cause: A 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.
Action: Specify a table for which support exists in EDS_ADD_TABLE.
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that already had EDS added on the local database.
Action: None
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE on a logical standby database without having first called it on the primary database.
Action: Call DBMS_LOGSTDBY.EDS_ADD_TABLE on the primary database and then retry on the standby.
Cause: A call was made to DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on a logical standby database which can only be called on a primary database
Action: Call DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on the primary database
Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that did not have a primary key.
Action: Add a primary key and retry the operation.
Cause: An ALTER SYSTEM SET ENCRYPTION KEY statement was successfully committed on the logical standby database.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE for a table that is being maintained by extended data type support.
Action: Call DBMS_LOGSTDBY.EDS_REMOVE_TABLE followed by either DBMS_LOGSTDBY.EDS_ADD_TABLE or a retry of the operation.
Cause: A call was made to finish an extended data type support evolve operation without having first started the operation.
Action: Call DBMS_LOGSTDBY.EDS_EVOLVE_MANUAL with START option and then retry.
Cause: An extended data type support evolve operation was started but not yet completed.
Action: Wait 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.
Cause: A 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.
Action: Drop the existing materialized view log and retry the operation.
Cause: An operation was attempted on a container and an error occurred.
Action: Address the failure condition and then retry.
Cause: An operation was attempted on a container. However, the container was not open.
Action: Open the container and then retry.
Cause: Logical standby apply encountered a non-fatal error during DDL execution and continued to process subsequent transactions.
Action: This error is informational only. No user action is required.
Cause: _MAX_LOG_LOOKBACK or MAX_SGA parameter was set to a value that will lead to decreased performance.
Action: Reset parameters such that _MAX_LOG LOOKBACK is at least 5 times the value of MAX_SGA.
Cause: The specified skip procedure did not exist.
Action: Ensure that the specified skip procedure exists and is accessible by the calling user.
Cause: Creation of global temporary table failed due to the specified reason.
Action: Run the statement after fixing the condition that caused the failure.
Cause: ASYNC redo transport was unable to find either an online log or archived redo log that represents the current live redo sequence number.
Action: No action is required.
Cause: A 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.
Action: No action is required.
Cause: Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined.
Action: No action is required.