LISTE CODE ERREURS ORACLE.

 

ORA-16019	ORA-16019: cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
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...10) 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.

 

ORA-16020	ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
Cause	With automatic archiving enabled, the number of archive log destinations that could be used for the database was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.
Action	Either adjust the settings of the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.

 

ORA-16021	ORA-16021: session string destination cannot be the same as session string destination
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.

 

ORA-16022	ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL
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.

 

ORA-16023	ORA-16023: system string destination cannot be the same as session string destination
Cause	An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1...10) 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.

 

ORA-16024	ORA-16024: parameter string cannot be parsed
Cause	The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) 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.

 

ORA-16025	ORA-16025: parameter string contains repeated or conflicting attributes
Cause	The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained either repeated attributes or attributes that conflicted with each other.
Action	Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

 

ORA-16026	ORA-16026: parameter string contains an invalid attribute value
Cause	The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained an attribute with an invalid value.
Action	Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

 

ORA-16027	ORA-16027: parameter string is missing a destination option
Cause	The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) 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.

 

ORA-16028	ORA-16028: new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
Cause	With automatic archiving enabled, an attempt was made to change the indicated LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...10) 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.

 

ORA-16029	ORA-16029: cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations
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...10). Then, change the value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.

 

ORA-16030	ORA-16030: session specific change 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...10) parameters.

 

ORA-16031	ORA-16031: parameter string destination string exceeds string character limit
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.

 

ORA-16032	ORA-16032: parameter string destination string cannot be translated
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.

 

ORA-16033	ORA-16033: parameter string destination cannot be the same as parameter string destination
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.

 

ORA-16034	ORA-16034: FROM parameter is incompatible with MANAGED recovery
Cause	Use of the FROM "location" parameter is not allowed when MANAGED recovery has been specified.
Action	Correct the syntax and retry the command.

 

ORA-16035	ORA-16035: missing required keyword string
Cause	The indicated keyword is required but was not specified.
Action	Correct the syntax and retry the command.

 

ORA-16036	ORA-16036: invalid MANAGED recovery CANCEL option
Cause	A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.
Action	Specify either nothing or IMMEDIATE following CANCEL.

 

ORA-16037	ORA-16037: user requested cancel of managed recovery operation
Cause	The managed standby database recovery operation has been canceled per user request.
Action	No action is required.

 

ORA-16038	ORA-16038: log string sequence# string cannot be archived
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.

 

ORA-16039	ORA-16039: RFS request version mismatch
Cause	A request to archive a redo log to a standby site failed because the request was incompatible with the Remote File Server (RFS) at the standby site.
Action	Verify that compatible versions of Oracle are running on the primary and all standby sites.

 

ORA-16040	ORA-16040: standby destination archive log file is locked
Cause	The target standby destination archive log file is currently locked. This indicates that the file is being archived to by another Remote File Server (RFS) process.
Action	Check for and eliminate duplicate standby destination archive log service names defined for the primary database.

 

ORA-16041	ORA-16041: Remote File Server fatal error
Cause	The Remote File Server (RFS) process at the standby destination archive log site has encountered a disabling error and is no longer available. Further archiving to the standby site may not be possible.
Action	Refer to the appropriate RFS trace file located at the standby site for details regarding the error encountered and if possible take corrective action.

 

ORA-16042	ORA-16042: user requested cancel immediate of managed recovery operation
Cause	The managed standby database recovery operation has been 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.

 

ORA-16043	ORA-16043: managed recovery session canceled
Cause	The standby database managed recovery operation has been canceled per user request or operation timeout.
Action	More specific messages will accompany this message.

 

ORA-16044	ORA-16044: destination string attribute cannot be specified at session level
Cause	An archive log destination attribute was attempted to be modified at the session level.
Action	Use the ALTER SYSTEM command to modify the destination attribute.

 

ORA-16045	ORA-16045: circular archive log destination dependency chain
Cause	An archive log destination contains a dependency to another archive log destination that also contains a dependency.
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.

 

ORA-16046	ORA-16046: Archive log destination failed due to failed dependent destination
Cause	The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails.
Action	No action required.

 

ORA-16047	ORA-16047: DGID mismatch between destination setting and standby
Cause	The DB_UNIQUE_NAME specified for the destination does not match the DB_UNIQUE_NAME at the destination.
Action	Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter defined for the destination matches the DB_UNIQUE_NAME parameter defined at the destination.

 

ORA-16050	ORA-16050: destination exceeded specified quota size
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.

 

ORA-16051	ORA-16051: parameter string contains an invalid delay time
Cause	The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) 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.

 

ORA-16052	ORA-16052: DB_UNIQUE_NAME attribute is required
Cause	The DB_UNIQUE_NAME attribute is required when DG_CONFIG is enabled.
Action	Use the DB_UNIQUE_NAME attribute to specify a valid Data Guard Name for the destination. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view.

 

ORA-16053	ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration
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.

 

ORA-16055	ORA-16055: FAL request rejected
Cause	FAL server rejects the FAL request from the FAL client. This may be caused by different reasons.
Action	to solve the problem.

 

ORA-16056	ORA-16056: backup control file archival requires proper syntax
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	If the archival operation is correct when using a backup control file, then the USING BACKUP CONTROLFILE syntax is required.

 

ORA-16057	ORA-16057: DGID from server not in Data Guard configuration
Cause	The Data Guard name of the primary database or the FAL server is not in the Data Guard configuration of the standby.
Action	In order for the primary database or the FAL server to archive logs to the standby database, the Data Guard name of the primary or FAL server must be in the Data Guard configuration of the standby.

 

ORA-16058	ORA-16058: standby database instance is not mounted
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.

 

ORA-16059	ORA-16059: Log file is empty or invalid next available block
Cause	Archiving not allowed of an empty or invalid log file.
Action	No action is required.

 

ORA-16060	ORA-16060: Log file is current
Cause	The current log file cannot be archived using its file name.
Action	No action is required.

 

ORA-16061	ORA-16061: Log file status has changed
Cause	It is possible 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.

 

ORA-16062	ORA-16062: DGID from standby not in Data Guard configuration
Cause	The Data Guard name from the standby is not in the Data Guard configuration of the server.
Action	In order for the server to be allowed to archive logs to the standby, the Data Guard name of the standby must be in the Data Guard configuration of the server.

 

ORA-16063	ORA-16063: remote archival is enabled by another instance
Cause	Remote archival of database REDO log files has been enabled by another instance, and cannot be disabled for this instance.
Action	Set the REMOTE_ARCHIVE_ENABLE parameter to TRUE and restart this instance.

 

ORA-16064	ORA-16064: remote archival is disabled by another instance
Cause	Remote archival of database REDO log files has been disabled by another instance, and cannot be enabled for this instance.
Action	Set the REMOTE_ARCHIVE_ENABLE parameter to FALSE and restart this instance.

 

ORA-16065	ORA-16065: remote archival disabled at standby destination
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.

 

ORA-16066	ORA-16066: remote archival disabled
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.

 

ORA-16067	ORA-16067: activation identifier mismatch in archive log string
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.

 

ORA-16068	ORA-16068: redo log file activation identifier mismatch
Cause	The activation identifier of the indicated redo log file does not match the activation identifier of the database.
Action	none

 

ORA-16069	ORA-16069: Archive Log standby database activation identifier mismatch
Cause	The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database.
Action	Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

 

ORA-16070	ORA-16070: parameter string contains an invalid REGISTER attribute value
Cause	The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) 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.

 

ORA-16071	ORA-16071: dependency archived log file not found string
Cause	The specified archived log file was not found at the indicated standby destination.
Action	Verify the correctness of the dependency archived log file name template specified for the indicated standby destination against the actual dependency archived log file.

 

ORA-16072	ORA-16072: a minimum of one standby database destination is required
Cause	No standby database archive log destinations were specified.
Action	Specify a standby archive log destination in the initialization parameter file.

 

ORA-16073	ORA-16073: archiving must be enabled
Cause	Online log file archiving is disabled.
Action	Enable log file archiving.

 

ORA-16074	ORA-16074: ARCH processes must be active
Cause	There are no active ARCH processes.
Action	It is required that at least one ARCH process be active.

 

ORA-16075	ORA-16075: standby database destination mismatch
Cause	A standby database destination was specified that is not accessed by another instance.
Action	All database instances must access the same standby databases.

 

ORA-16076	ORA-16076: unknown standby database destination
Cause	A standby database destination was specified that is not accessed by another instance.
Action	All database instances must access the same standby databases.

 

ORA-16078	ORA-16078: media recovery disabled
Cause	The database is not in ARCHIVELOG mode.
Action	Place the database in ARCHIVELOG mode.

 

ORA-16079	ORA-16079: standby archival not enabled
Cause	The standby database does not have archival enabled.
Action	In order to allow the standby database to access the standby log files, the ARCH process must be enabled and active.

 

ORA-16080	ORA-16080: invalid LogMiner session string for APPLY
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.

 

ORA-16081	ORA-16081: insufficient number of processes for APPLY
Cause	Logical standby apply engine was started with fewer processes available than needed.
Action	Increase the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.

 

ORA-16082	ORA-16082: logical standby is not initialized correctly
Cause	Logical standby apply engine was started but it found inconsistencies in its metadata.
Action	Look in the trace file for more information.

 

ORA-16083	ORA-16083: LogMiner session has not been created
Cause	Logical standby apply engine was started without creating a LogMiner session.
Action	Create a LogMiner session and restart the apply engine.

 

ORA-16084	ORA-16084: an apply engine is already running
Cause	A logical standby apply engine was running when another was created.
Action	Shut down the previous apply engine before starting a new one.

 

ORA-16086	ORA-16086: standby database does not contain available standby log files
Cause	The primary database is in "no data loss" mode, but the standby database does not contain any "standby log files".
Action	Add one or more standby log files to the standby database. This can be done while the standby database is mounted.

 

ORA-16087	ORA-16087: graceful switchover requires standby or current control file
Cause	An attempt was made to perform a graceful switchover operation using a backup or clone control file.
Action	Convert the backup control file into a current control file prior to attempting a graceful switchover operation. A clone control file cannot be used for a graceful switchover operation.

 

ORA-16088	ORA-16088: archive log has not been completely archived
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.

 

ORA-16089	ORA-16089: archive log has already been registered
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.

 

ORA-16090	ORA-16090: archive log to be replaced not created by managed standby process
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.

 

ORA-16091	ORA-16091: dependent archive log destination already archived
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.

 

ORA-16092	ORA-16092: dependent archive log destination is not active
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.

 

ORA-16093	ORA-16093: dependent archive log destination is not LGWR-enabled
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.

 

ORA-16094	ORA-16094: database shutdown during archival operation
Cause	The database was shut down while an online log file archival was active.
Action	None required. The ARCH process is terminated.

 

ORA-16095	ORA-16095: Dependent destination removal for inactivation
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.

 

ORA-16096	ORA-16096: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY
Cause	None
Action	Specify this command to prepare the primary database for switchover

 

ORA-16097	ORA-16097: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
Cause	None
Action	Specify this command to prepare the standby database for switchover

 

ORA-16098	ORA-16098: inaccessible standby database forced shutdown to protect primary
Cause	No standby database archive log destinations remain accessible and the primary database is in "protected" no-data-loss mode.
Action	Specify an alternate standby archive log destination in the initialization parameter file.

 

ORA-16099	ORA-16099: internal error ORA-00600 occurred at standby database
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.

 

ORA-16100	ORA-16100: not a valid Logical Standby database
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.

 

ORA-16101	ORA-16101: a valid start SCN could not be found
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.

 

ORA-16102	ORA-16102: remote information is not available on the specified primary
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.

 

ORA-16103	ORA-16103: Logical Standby apply must be stopped to allow this operation
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.

 

ORA-16104	ORA-16104: invalid Logical Standby option requested
Cause	The option requested is not valid.
Action	Check spelling or refer to the Oracle8i SQL Reference manual for the correct statement syntax, then re-enter the request.

 

ORA-16105	ORA-16105: Logical Standby is already running in background
Cause	A Logical Standby apply operation is already running.
Action	none

 

ORA-16107	ORA-16107: all log data from primary has been processed
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;

 

ORA-16108	ORA-16108: database is no longer a standby database
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;

 

ORA-16109	ORA-16109: failed to apply log data from previous primary
Cause	Log data from previous primary could not be completely applied.
Action	. Then, re-issue command.

 

ORA-16110	ORA-16110: user procedure processing of logical standby apply DDL
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.

 

ORA-16111	ORA-16111: log mining and apply setting up
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.

 

ORA-16112	ORA-16112: log mining and apply stopping
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.

 

ORA-16113	ORA-16113: applying change to table or sequence string
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.

 

ORA-16114	ORA-16114: applying DDL transaction with commit SCN string
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.

 

ORA-16115	ORA-16115: %s\% of LogMiner dictionary loading is done
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.

 

ORA-16116	ORA-16116: no work available
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.

 

ORA-16117	ORA-16117: processing
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.

 

ORA-16119	ORA-16119: building transaction at SCN string
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.

 

ORA-16120	ORA-16120: dependencies being computed for transaction at SCN string
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.

 

ORA-16121	ORA-16121: applying transaction with commit SCN string
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.

 

ORA-16122	ORA-16122: applying large dml transaction at SCN string
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.

 

ORA-16123	ORA-16123: transaction string string string is waiting for commit approval
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.

 

ORA-16124	ORA-16124: transaction string string string is waiting on another transaction
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.

 

ORA-16125	ORA-16125: large transaction string string string is waiting for more data
Cause	The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16126	ORA-16126: loading table or sequence string
Cause	Information on the given table or sequence is being loaded into an in memory cache for future use.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16127	ORA-16127: stalled waiting for additional transactions to be applied
Cause	This process is waiting for additional memory before continuing. Additional log information cannot be read into memory until more transactions have been applied to the database, thus freeing up additional memory.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, increase available SGA or the number of apply processes.

 

ORA-16128	ORA-16128: User initiated stop apply successfully completed
Cause	Logical standby was shutdown in an orderly fashion.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16129	ORA-16129: unsupported dml encountered
Cause	DML to tables in the SYS schema have been updated and are not part of a DDL operation. This may be due to some DBA activity or DML associated with a kernel PL/SQL request that Logical Standby does not yet support.
Action	Check the DBA_LOGSTDBY_EVENTS table for the name of the table being processed. Possibly use Log Miner to understand the transaction, and provide a compensating transaction on the standby system. Once complete, call DBMS_LOGSTDBY.SKIP_TRANSACTION with the associated transaction id, and resume apply.

 

ORA-16130	ORA-16130: supplemental log information is missing from log stream
Cause	Supplemental logging is not enabled at the primary database.
Action	Issue the following command to enable supplemental logging. ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;

 

ORA-16131	ORA-16131: An error occurred during a Terminal Recovery of the standby.
Cause	An error occurred during a Terminal Recovery of the standby.
Action	Check the standby alert log additional information.

 

ORA-16132	ORA-16132: An error occurred during activation of the standby.
Cause	An error occurred during activation of the standby database following a Terminal Recovery.
Action	Check the standby alert log additional information.

 

ORA-16133	ORA-16133: Datafile string has incorrect terminal recovery stamp.
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.

 

ORA-16134	ORA-16134: invalid MANAGED recovery FINISH option
Cause	A mode other than NOWAIT follows the FINISH keyword in RECOVER MANAGED STANDBY DATABASE statement.
Action	Specify either nothing or NOWAIT following FINISH.

 

ORA-16135	ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
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.

 

ORA-16136	ORA-16136: Managed Standby Recovery not active
Cause	An attempt was made to cancel a managed recovery session but no managed recovery session was active.
Action	No action is necessary.

 

ORA-16137	ORA-16137: No terminal recovery is required
Cause	All archived logs have been applied, and there are no current logs to be applied. Terminal 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.

 

ORA-16138	ORA-16138: end of log stream not received from primary
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.

 

ORA-16139	ORA-16139: media recovery required
Cause	The database has not been recovered through the end of log stream. Graceful switchover is not possible.
Action	Ensure that the entire log stream has been applied. If appropriate, reissue the graceful switchover command.