Oracle 12c R2 Error Codes and Solution Suggestions from ORA-16000 to ORA-16200
- ORA-16000: database or pluggable database open for read-only access
Cause: The database or pluggable database was opened for read-only access. Attempts to modify the database using DML or DDL statements generate this error.
Action: In order to modify the database or pluggable database, it must first be shut down and reopened for read/write access.
Cause: The database has been opened for read-only access by another instance, and cannot be opened for read/write access by this instance.
Action: This instance must be opened for read/write access, or all other instances must first be shut down and reopened for read-only access.
Cause: The database or pluggable database has been opened for read/write access by another instance, and cannot be opened for read-only access by this instance.
Action: This instance must be opened for read-only access, or all other instances must first be shut down and reopened for read/write access.
Cause: An attempt was made to open a physical standby database in read/write mode.
Action: Reissue the ALTER DATABASE OPEN specifying READ ONLY.
Cause: The database could not be opened for read-only access by this instance because it requires recovery.
Action: Perform the necessary recovery and reopen for read-only access.
Cause: The database required recovery, and therefore could not be opened for read-only access by this instance.
Action: If the database was terminated abnormally (possibly using a shutdown abort), the database first needs to be opened in read/write mode. Otherwise, perform the necessary recovery and reopen for read-only access.
Cause: When opening or closing a database instance, the database may wait for pending remote archival requests to complete before proceeding with the operation. This error was reported because a shutdown was detected.
Action: This is an informational message so no action is required.
Cause: The database could not be opened for read-only access because its control file did not contain a valid control file checkpoint.
Action: Open the database for read/write access to create a valid control file checkpoint. The database can then be opened for read-only access.
Cause: The control file for the database being opened for read-only access was created using the CREATE CONTROLFILE statement. Therefore, a control file checkpoint could not be calculated and the database could not be opened for read-only access.
Action: First, open the database for read/write access. This creates a valid control file checkpoint. Then, reopen the database for read-only access.
Cause: The redo transport destination could not accept redo data because it was not a valid redo transport destination type.
Action: Verify that all redo transport destinations are either standby databases or downstream capture databases.
Cause: The Remote File Server (RFS) process at the specified redo transport destination experienced an unrecoverable error and was unable to receive further redo data.
Action: Correct the problem at the redo transport destination.
Cause: The database identifier of a physical standby database did not match that of the primary database.
Action: Ensure that the database identifier of each physical standby database matches that of the primary database.
Cause: An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived.
Action: No action is required.
Cause: An attempt was made to archive the named log, but the archive was unsuccessful. The archival failed because there were no archive log destinations specified, or all destinations are in an error state.
Action: Verify that archive log destinations are specified or take the necessary step to correct any errors that may have occurred.
Cause: An attempt was made to archive the named log to a destination, but the operation did not succeed because the destination was not in ARCHIVELOG mode.
Action: Enable ARCHIVELOG mode at all destinations and retry.
Cause: Redo apply timed out waiting for the requested archived log file.
Action: Verify that the primary database is still archiving redo data to the standby database and reissue the RECOVER STANDBY DATABASE command.
Cause: The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly.
Action: Set the primary archive destination to a valid non-NULL value.
Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1…31) parameter was encountered while fetching initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.
Action: Eliminate any incompatible parameter definitions.
Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified LOG_ARCHIVE_DEST_n (n = 1…31) or DB_RECOVERY_FILE_DEST parameter was encountered while fetching initialization parameters. 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter.
Action: Eliminate any incompatible parameter definitions.
Cause: The number of archive log destinations that could be used was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.
Action: Either adjust the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.
Cause: An attempt was made to change the first specified archive log parameter using ALTER SESSION to have a destination value that duplicates the session-level destination value of the second specified archive log parameter.
Action: Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters.
Cause: An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL.
Action: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value.
Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter produced a destination that duplicates the session destination value of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a non-NULL value with the ALTER SYSTEM command. Or, this error can occur when setting a NULL value with ALTER SESSION command, because then the associated system destination value may appear as a duplicate.
Action: Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter.
Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1…31) parameter could not be parsed. Common causes for this error are a misplaced equal sign, an unrecognized attribute, or an attribute that is missing a required value.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained either repeated attributes or attributes that conflicted with each other.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained an attribute with an invalid value.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1…31) parameter failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attrbute.
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
Cause: An attempt was made to change the indicated LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameter (n = 1…31) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.
Action: Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.
Cause: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations.
Action: Define one or more log archive destinations using parameters LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1…31). Then, change the value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.
- ORA-16030: session specific change to the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter requires a LOG_ARCHIVE_DEST_n destination
Cause: The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command.
Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1…31) parameters.
Cause: The value for the specified parameter contained a destination string that is too long.
Action: Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message.
Cause: The value for the specified parameter contained a destination string that could not be translated.
Action: Use a valid destination string in the specified parameter.
Cause: An attempt was made to change the first specified archive log parameter to have a destination value that duplicates the system-level destination value of the second specified archive log parameter.
Action: Specify a different value for one of the archive log parameters.
Cause: Database recovery could not be started because the FROM and MANAGED STANDBY DATABASE clauses were both specifed when attempting to start recovery.
Action: Retry the command with either the FROM or MANAGED STANDBY DATABASE clause, but not both.
Cause: The indicated keyword is required but was not specified.
Action: Correct the syntax and retry the command.
Cause: A mode other than IMMEDIATE followed the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.
Action: Specify either nothing or IMMEDIATE following CANCEL.
Cause: The managed standby database recovery operation has been canceled per user request.
Action: No action is required.
Cause: An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error.
Action: No action is required.
Cause: A request to archive a redo log to a redo transport destination failed because of an Oracle software version mismatch at the destination.
Action: Verify that a compatible version of Oracle software is running at the redo transport destination.
Cause: The target archive log file was locked. This indicates that the file is being archived to another Remote File Server (RFS) process.
Action: Ensure that each remote redo transport destination uses a unique network service name.
Cause: The Remote File Server (RFS) process at a redo transport destination encountered a fatal error and was no longer available. Further redo transmission to this destination may not be possible.
Action: Refer to the appropriate RFS trace file located at the redo transport destination for details regarding the error encountered and take corrective action.
Cause: Redo apply was canceled immediately per user request. Processing of the current archive log file has been interrupted and, therefore, the database is in an inconsistent state.
Action: No action is required.
Cause: Redo apply was canceled per user request or operation timeout.
Action: More specific messages will accompany this message.
Cause: An attempt was made to modify a redo transport destination attribute using the ALTER SESSION command.
Action: Use the ALTER SYSTEM command to modify the destination attribute.
Cause: An attempt was made to make a redo transport destination dependent on a redo transport destination that was dependent on it.
Action: Ensure that no redo transport destination is dependent on any destination that is dependent on it.
Cause: The redo transport destination was dependent upon another destination, which failed. Therefore, this destination failed.
Action: No action required.
Cause: The DB_UNIQUE_NAME specified for the destination did not match the DB_UNIQUE_NAME at the target database.
Action: Ensure that the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter matches the DB_UNIQUE_NAME parameter defined at the destination.
Cause: An archive log was attempted to be created in a destination with a specified maximum quota size. The creation of the archive log exceeded the specified quota size. Therefore, the destination has been made inaccessible to future archival operations.
Action: No action is required.
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760 (in minutes).
Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
Cause: DB_UNIQUE_NAME attribute was not specified. The value of the LOG_ARCHIVE_DEST_n parameter for each remote redo transport destination must contain the DB_UNIQUE_NAME attribute if the LOG_ARCHIVE_CONFIG parameter value contains the DG_CONFIG attribute.
Action: Use the DB_UNIQUE_NAME attribute to specify the DB_UNIQUE_NAME for the destination.
Cause: The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.
Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This problem can also occur when specifying a non-standby destination with an DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME initialization parameter for the current instance.
Cause: Fetch archive log (FAL) server rejected a redo gap fetch request from the client. This may have various causes.
Action: Check the alert log on the primary database. Take the appropriate action to solve the problem.
Cause: An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified.
Action: Use the USING BACKUP CONTROLFILE clause to perform an online log file archival using a backup control file.
Cause: The primary database or fetch archive log (FAL) server was not found in the Data Guard configuration of the standby database.
Action: Add the database unique name of the primary database or FAL server to the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database initialization parameter.
Cause: The Remote File Server (RFS) process on the standby database received an internal error.
Action: Check the standby alert log and RFS trace files for more information.
Cause: An attempt was made to archive an empty or invalid log file.
Action: No action is required.
Cause: An attempt was made to archive current log file.
Action: No action is required.
Cause: The online log file was reclaimed as a new log file either before archival started or during the archival operation.
Action: No action is required.
Cause: The standby database was not found in the Data Guard configuration of the server.
Action: Add the database unique name of the standby database to the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database initialization parameter.
Cause: Receipt of remote archived REDO log files has been disabled at the associated standby destination host database.
Action: If appropriate change the associated archive log parameter to specify a local destination with the LOCATION keyword or defer the associated archive log destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the RECEIVE attribute of the LOG_ARCHIVE_CONFIG parameterand restart the standby database instance before further REDO log file archivals occur.
Cause: An archive log destination parameter has specified a remote destination with the SERVICE keyword. Remote archival of REDO log files has been disabled for this database. The associated archive log destination has been disabled.
Action: If appropriate change the archive log parameter to specify a local destination with the LOCATION keyword or (if appropriate) set the REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the SEND attribute of the LOG_ARCHIVE_CONFIG parameter and restart the database instance before further REDO log file archivals occur.
Cause: The activation identifier contained in the archive log file header does not match the activation identifier of the database being recovered. The indicated archive log cannot be applied to the database.
Action: Locate the appropriate archive log for the database.
Cause: The activation identifier of the indicated redo log file does not match the activation identifier of the database.
Action: n/a
Cause: Redo transport failed because the activation identifier of the primary and physical standby databases did not match. This can happen if the physical standby database was not created from a backup of the primary database.
Action: Create a valid configuration and re-try the failed operation.
Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1…31) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an O/S-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).
Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter.
Cause: The specified archived log file was not found at a redo tranpsort destination on which other destinations are dependent.
Action: Verify that all redo transport destinations that are dependent upon another destination or upon which other destinations are dependent are configured correctly.
Cause: No standby database archive log destinations were specified.
Action: Specify a standby archive log destination in the initialization parameter file.
Cause: Online log file archiving is disabled.
Action: Enable log file archiving.
Cause: All ARCH processes have stopped.
Action: Restart the instance.
Cause: Another instance had access to a standby database destination that this instance did not. If the initialization parameter LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this may be due to a standby database becoming unavailable recently.
Action: Ensure that at each instance the set of standby databases referred to by LOG_ARCHIVE_DEST_n initialization parameters is the same and define a DG_CONFIG at each instance to identify those databases explicitly.
Cause: A standby database destination was specified that was not accessed by another instance. If the initialization parameter LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this mismatch may be due to a standby database having been restarted recently.
Action: Ensure that at each instance the set of standby databases referred to by LOG_ARCHIVE_DEST_n initialization parameters is the same and define a DG_CONFIG at each instance to identify those databases explicitly.
Cause: The database is not in ARCHIVELOG mode.
Action: Place the database in ARCHIVELOG mode.
Cause: The standby database did not have archival enabled.
Action: In order to allow the standby database to access the standby log files, the standby database must be in ARCHIVELOG mode.
Cause: Logical standby apply engine was started with an invalid LogMiner session identifier.
Action: Fix the problem with the LogMiner session or create a new session.
Cause: Logical standby apply engine was started with fewer processes available than needed.
Action: Increase the values of the initialization parameters PROCESSES and or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS view.
Cause: Logical standby apply engine was started but it found inconsistencies in its metadata.
Action: Look in the trace file for more information.
Cause: Logical standby apply engine was started without creating a LogMiner session.
Action: Create a LogMiner session and restart the apply engine.
Cause: A logical standby apply engine was running when another was created.
Action: Shut down the previous apply engine before starting a new one.
Cause: The primary database was in MAXIMUM PROTECTION or MAXIMUM AVAILABILITY mode, but redo data could not be written to the standby redo log at the standby database(s).
Action: Check the Remote File Server (RFS) trace file for specific errors and reconfigure the standby redo log as appropriate.
Cause: An attempt was made to perform a switchover operation using a backup or clone control file.
Action: Convert the backup control file into a current control file prior to attempting a switchover operation. A clone control file cannot be used for a switchover operation.
Cause: An attempt was made to register an archive log that has not been completely archived. The specified archive log may be a “current” log file.
Action: Specify a completed archive log.
Cause: An attempt was made to register an archive log that already has a corresponding thread# and sequence# entry in the standby database control file. Duplicate information is not permitted.
Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log information.
Cause: An attempt was made to replace an archive log entry that was not originally created by the managed standby operation.
Action: No user action required.
Cause: An archive log destination contains a dependency to another archive log destination that has previously been archived.
Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.
Cause: An archive log destination contains a dependency to another archive log destination that is not active”
Action: The child archive log destination cannot be dependent on another invalid archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes.
Cause: An archive log destination contains a dependency to another archive log destination that is not enabled for the LGWR process”
Action: The child archive log destination cannot be dependent on another archive log destination not archived by the LGWR. Use the ALTER SYSTEM command to change the parent archive log to specify the LGWR process.
Cause: The database was shut down while an online log file archival was active.
Action: None required.
Cause: A dependent archive log destination was inactivated due to the parent archive log destination becoming inelligible for archival. This may be due to the parent destination being manually deferred by an application user.
Action: None required.
Cause: None
Action: Specify this command to switch the primary database to the physical standby role.
Cause: None
Action: Specify this command to switch the physical standby database to the primary role.
Cause: The primary database was shut down because it was operating in maximum protection mode and no suitable standby databases were available to protect the primary database from data loss.
Action: Diagnose and correct whatever errors exist in the configuration or configure the primary database for maximum availability or maximum performance mode.
Cause: The RFS process on the standby database received an internal error.
Action: Check the standby alert log and RFS trace files for more information.
Cause: This database has not been completely configured as a Logical Standby database.
Action: Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY INITIAL statement. See the Oracle8i SQL Reference manual for the statement syntax.
Cause: An SCN from which to start could not be found.
Action: Register the first log file following the backup from which this database was generated. Using the ALTER DATABASE REGISTER LOGILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this startement.
Cause: The new primary has not completed generating the necessary information for the standby to begin consuming its log stream.
Action: Verify that the database link provided references a system that is about to become a new primary. Wait a short time before retrying the command to allow the primary some time to generate the necessary information.
Cause: Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.
Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or respecify the operation.
Cause: The specified parameter is not valid.
Action: Check spelling or refer to the DBMS_LOGSTDBY PL/SQL package documentation for the correct statement syntax.
Cause: A Logical Standby apply operation is already running.
Action: None
Cause: Logical Standby coordinator was performing a scan to identify previously applied transactions.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
Cause: On the primary system, the log stream has been ended by the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command.
Action: Issue one of the following commands to make this standby a primary or resume applying changes from a new primary. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL PRIMARY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
Cause: The current database has already been made a primary database.
Action: Issue the following commands to make this primary a standby. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
Cause: Log data from previous primary could not be completely applied.
Action: Check DBA_LOGSTDBY_EVENTS for failures and take corrective action. Then, reissue command.
Cause: A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.
Action: No action necessary, this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.
Cause: This logical standby process is setting up to begin processing changes.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: This logical standby process is cleaning up and stopping Logical Standby apply.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The process is applying changes to a specific schema object.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The process is applying a DDL change that’s committed at the given SCN.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The process is loading dictionary information from the redo stream. This activity may take a few minutes.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The process is idle waiting for additional changes to be made available.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The process is performing its primary function and is not waiting on any significant event.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The transaction being committed at the given SCN is being prepared for apply.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The transaction committed at the given SCN is being analyzed for dependencies.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The transaction committed at the given SCN is being applied.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The apply process is waiting for approval to commit a transaction. This transaction may depend on another or other synchronization activity may delay the committing of a transaction.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The apply process is waiting to apply additional changes. This transaction likely depends on another.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: Information on the given table or sequence is being loaded into an in memory cache for future use.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: This process is waiting for additional memory before continuing. Additional log information cannot be read into memory until more transactions have been applied to the database, thus freeing up additional memory.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, increase available SGA or the number of apply processes.
Cause: Logical standby was shutdown in an orderly fashion.
Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes.
Cause: One or more DMLs to an unsupported table were encountered and skipped.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. Optionally, check the DBA_LOGSTDBY_EVENTS view for more information including the impacted table owner and name.
Cause: Supplemental logging is not enabled at the primary database.
Action: Issue the following command to enable supplemental logging. ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;
Cause: An error occurred during a Terminal Recovery of the standby.
Action: Check the standby alert log additional information.
Cause: An error occurred during activation of the standby database following a Terminal Recovery.
Action: Check the standby alert log additional information.
Cause: After activation of a standby database following a terminal recovery (recovery of standby using current logs), recovery of a datafile from before the activation must have completed the same terminal recovery to avoid corruption.
Action: A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery.
Cause: A mode other than NOWAIT follows the FINISH keyword in RECOVER MANAGED STANDBY DATABASE statement.
Action: Specify either nothing or NOWAIT following FINISH.
Cause: The LOG_ARCHIVE_CONFIG parameter can not be modified while any RAC instance is open in either maximum protection or maximum availability mode. Also, the parameter can not be modified in such way that would cause all destinations to fail while in maximum protection mode.
Action: Make the modification before the database is opened by any instance.
Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active.
Action: No action is necessary.
Cause: An attempt was made to explicitly change the state of a destination participating in an internally managed set of alternate destinations. For example, a destination in the ALTERNATE state was explicitly ENABLED. Doing so will thwart the internal mechanisms to manage these cooperating destinations.
Action: The destination must be reset before making this state change.
Cause: The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible.
Action: Verify that the primary log stream has been terminated. Ensure that the standby has applied all necessary redo from the primary system and, if appropriate, reissue the graceful switchover command.
Cause: An error has occurred while performing a switchover.
Action: If you were switching a primary database to the standby role, the conversion was successful, but one or more errors occurred after the conversion completed. See the alert log for more information. You can proceed with switching the target standby database to the primary role, but you must address the errors reported at the old primary database before it can protect the new primary database. If you encountered this error while switching a physical standby database to the primary role, the switchover did not succeed because additional redo must be applied. Verify that redo apply is active and wait until the SWITCHOVER_STATUS column of the V$DATABASE dynamic performance view reports TO_PRIMARY or SESSIONS_ACTIVE before retrying the switchover.
Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs.
Action: To recover the standby online logs issue the following command: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH. Then reissue the ALTER DATABASE ACTIVATE STANDBY DATABASE command. To activate the standby without recovering the online logs, issue the following command: ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE.
Cause: An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery.
Action: The primary must not attempt to archive to the standby after a terminal recovery.
Cause: The indicated archived log file is not available for recovery due to the fact that it is still being archived.
Action: Verify that archival of the indicated log file has completed and reissue the RECOVER STANDBY DATABASE command.
Cause: The control file enqueue is currently unavailable.
Action: No Action is required. We will try to re-fetch it at a later time.
Cause: Multiple archive log destinations reference the same standby database, using different service names. This is not allowed.
Action: Remove one of the duplicate archive log destinations.
Cause: The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement.
Action: No action is required.
Cause: An archive log containing a FINISH recovery indicator was received by a standby database that has received archive logs in the future of the received archive log. Because of the possibility that these future archive logs have been applied to this standby database, the received archive log must be rejected.
Action: No action is required.
Cause: The attempted operation failed because of a pending CANCEL of the managed standby recovery operation.
Action: Wait for the managed standby recovery session to end. Then retry the operation.
Cause: The attempted database operation is not allowed while the standby database is in ‘no-data-loss’ protected mode.
Action: Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement.
Cause: Use of the indicated attribute is illegal in the given context.
Action: Make the appropriate changes and reissue the statement.
Cause: The use of a LGWR archive log dependency is not allowed when the primary is protected by a standby database, as this requires use of the standby redo log files.
Action: Remove the LGWR archive log dependency and use normal LGWR archival instead.
Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed.
Action: Issue one of these operations following a FINISH recocvery: ALTER DATABASE OPEN READ ONLY or ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.
Cause: An attempt was made to change the LGWR/ARCH or SYNC/ASYNC attributes for a destination that is participating in the standby protection mode of the database.
Action: No action is required.
Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode.
Action: The standby database must be added to the configuration before the primary database is opened.
Cause: An attempt was made to add a log file member that did not match the other member types. This problem typically occurs when adding a standby log file member to an online redo log file group, or adding an online redo log file member to a standby redo log file group.
Action: Verify the log file group type using the TYPE column of the V$LOG fixed view.
Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.
Action: The standby database must be added to the configuration before the primary database is opened.
Cause: The LGWR network server could not attach to remote host
Action: The alert log contains more problem-specific information
Cause: The LGWR network server could not detach from remote host
Action: The alert log contains more problem-specific information
Cause: The LGWR lost its connection to the network server
Action: The alert log contains more problem-specific information
Cause: The LGWR network server could not communicate with the remote host
Action: The alert log contains more problem-specific information
Cause: The LGWR network server could not switch to non-blocking mode
Action: The alert log contains more problem-specific information
Cause: The LGWR network server could not switch to blocking mode
Action: The alert log contains more problem-specific information
Cause: The LGWR network server could not switch to blocking mode
Action: The alert log contains more problem-specific information
Cause: When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open.
Action: Continue standby recovery with additional log shipping from primary.
Cause: See alert log for more details
Action: Copy missing archived logs from primary or another standby. Register the logs and reissue the RECOVER…FINISH command. If the logs are not available, issue the ALTER DATABASE RECOVER MANAGED STANDBY SKIP command to ignore the standby redo log files.
Cause: An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due the existence, at the remote site, of archive logs containing REDO in the future of the Terminal EOR.
Action: n/a
Cause: One of two situations can cause this error: 1) An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected. 2) An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to an active Remote File Server process at the remote site. An active Remote File Server (RFS) process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented.
Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation.
Cause: The managed standby database recovery operation has been terminated per user specified THROUGH THREAD/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement.
Action: No action is required.
Cause: An attempt was made to shut down a standby database while media recovery was active.
Action: Cancel media recovery to proceed with the shutdown.
Cause: The background process dedicated to dictionary build is active.
Action: wait and try it later.
Cause: The THROUGH LAST SWITCHOVER clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE was specified and the database has been recovered to the most recent End-Of-Redo marker. All known archived logs have been applied. Managed recovery is not required.
Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby.
Cause: The database is operating in manual archiving mode. Remote archivelog destinations are not allowed in this mode.
Action: Use the ALTER DATABASE ARCHIVELOG command to place the database in automatic ARCHIVELOG mode, or defer the archivelog destinations that specify the SERVICE= attribute.
Cause: Incremental changes to a log_archive_dest_n parameter cannot be made when using an SPFILE.
Action: Specify either LOCATION or SERVICE plus all other attributes to be set in one ALTER SYSTEM/SESSION SET command.
Cause: The number of server processes available for Logical Standby is currently limited to 1024 LogMiner processes and 1024 apply processes or a total of 2048.
Action: Retry with a lower value.
Cause: MAX_SGA is larger than 75% of the larger of initialization parameters SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.
Action: Specify the value of MAX_SGA to be less than 75% of the maximum of SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.
Cause: An internal error was encountered on the internal channel between LGWR and Network Server.
Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival.
Cause: The internal hash value generated for one DB_UNIQUE_NAME collided with the hash value of another DB_UNIQUE_NAME.
Action: Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a different value.
Cause: Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG parameters are defined in the initialization file and they are mutually exclusive.
Action: The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use only the LOG_ARCHIVE_CONFIG parameter.
Cause: The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly the same on all RAC instances so the SID=’*’ qualifier is required.
Action: Re-enter the command using the SID=’*’ qualifier.
Cause: The LOG_ARCHIVE_CONFIG parameter was specified with duplicate, conflicting or invalid attributes.
Action: Check the documentation regarding the correct specification of the LOG_ARCHIVE_CONFIG parameter.
Cause: The settings for the LOG_ARCHIVE_CONFIG parameter were inconsistent with the settings of a previously started instance. The settings for this parameter must be exactly the same for all instances.
Action: Ensure that all instances use the exact same LOG_ARCHIVE_CONFIG settings.
Cause: An attempt to ship redo to standby without logging on to standby or with invalid user credentials.
Action: Check that primary and standby are using password files and that both primary and standby have the same SYS password. Restart primary and/or standby after ensuring that password file is accessible and REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED or EXCLUSIVE.
Cause: Standby wants sqlnet network integrity for redo shipment which is not configured properly at the primary.
Action: Check sqlnet.ora documentation regarding how to setup network integrity and set it up identically on both primary and standby. Restart primary and/or standby.
Cause: Standby wants sqlnet network encryption for redo shipment which is not configured properly at the primary.
Action: Check sqlnet.ora documentation regarding how to setup network encryption and set it up identically on both primary and standby. Restart primary and/or standby.
Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the same on all RAC instances so the SID=’*’ qualifier is required.
Action: Re-enter the command using the SID=’*’ qualifier.
Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can only be used if the DB_UNIQUE_NAME parameter has been explicitly defined.
Action: Explicitly define a valid DB_UNIQUE_NAME.
Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime.
Action: Shut down the instance.
Cause: The DB_UNIQUE_NAME parameter has an invalid specification. The DB_UNIQUE_NAME parameter has a maximum length of 30 characters and the only characters allowed are alpha-numeric characters and “_”, “$” and “#”.
Action: Check the documentation and re-enter the parameter.
Cause: A timeout was incurred during remote archival.
Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival.
Cause: See alert log for more details
Action: Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, call Oracle support.
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.