LISTE CODE ERREURS ORACLE.

 

ORA-16140	ORA-16140: standby online logs have not been recovered
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 re-issue 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.

 

ORA-16143	ORA-16143: RFS connections not allowed during or after terminal recovery
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.

 

ORA-16145	ORA-16145: archival for thread# string sequence# string in progress
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.

 

ORA-16146	ORA-16146: standby destination control file enqueue unavailable
Cause	The target standby destination control file is currently unavailable to the Remote File Server (RFS) process. This indicates that the target destination is the primary database itself.
Action	Check for and eliminate the standby destination archive log parameter in question.

 

ORA-16147	ORA-16147: standby database referenced by multiple archive log destinations
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.

 

ORA-16148	ORA-16148: user requested expiration of managed recovery operation
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.

 

ORA-16150	ORA-16150: FINISH recovery performed on another, older standby database
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.

 

ORA-16151	ORA-16151: Managed Standby Recovery not available
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.

 

ORA-16152	ORA-16152: standby database is in "no-data-loss" protected mode
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.

 

ORA-16154	ORA-16154: suspect attribute: string
Cause	Use of the indicated attribute is illegal in the given context.
Action	Make the appropriate changes and reissue the statement.

 

ORA-16156	ORA-16156: LGWR archive log dependency not allowed if database is standby protected
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.

 

ORA-16157	ORA-16157: media recovery not allowed following successful FINISH recovery
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.

 

ORA-16159	ORA-16159: Cannot change protected standby destination attributes
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.

 

ORA-16160	ORA-16160: Cannot change protected standby database configuration
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.

 

ORA-16161	ORA-16161: Cannot mix standby and online redo log file members for group string
Cause	An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile 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.

 

ORA-16162	ORA-16162: Cannot add new standby databases to protected configuration
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.

 

ORA-16163	ORA-16163: LGWR network server host attach error
Cause	The LGWR network server could not attach to remote host
Action	The alert log contains more problem-specific information

 

ORA-16164	ORA-16164: LGWR network server host detach error
Cause	The LGWR network server could not detach from remote host
Action	The alert log contains more problem-specific information

 

ORA-16165	ORA-16165: LGWR failed to hear from network server
Cause	The LGWR lost its connection to the network server
Action	The alert log contains more problem-specific information

 

ORA-16166	ORA-16166: LGWR network server failed to send remote message
Cause	The LGWR network server could not communicate with the remote host
Action	The alert log contains more problem-specific information

 

ORA-16167	ORA-16167: LGWR network server could not switch to non-blocking mode
Cause	The LGWR network server could not switch to non-blocking mode
Action	The alert log contains more problem-specific information

 

ORA-16168	ORA-16168: LGWR network server could not switch to blocking mode
Cause	The LGWR network server could not switch to blocking mode
Action	The alert log contains more problem-specific information

 

ORA-16169	ORA-16169: LGWR network server invalid parameters
Cause	The LGWR network server could not switch to blocking mode
Action	The alert log contains more problem-specific information

 

ORA-16170	ORA-16170: Terminal recovery may have left the database in an inconsistent state
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.

 

ORA-16171	ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq string-string
Cause	See alert log for more details
Action	Copy missing archived logs from primary or another standby. Register the logs and re-issue 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.

 

ORA-16172	ORA-16172: archive logs detected beyond Terminal End-Of-Redo
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	none

 

ORA-16173	ORA-16173: incompatible archival network connections active
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.

 

ORA-16174	ORA-16174: user requested thread/sequence termination of managed recovery
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.

 

ORA-16175	ORA-16175: cannot shut down database when media recovery is active
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.

 

ORA-16176	ORA-16176: background dictionary build cannot be running
Cause	The background process dedicated to dictionary build is active.
Action	wait and try it later.

 

ORA-16177	ORA-16177: media recovery is not required
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.

 

ORA-16178	ORA-16178: Cannot specify remote destinations in archivelog manual mode
Cause	The database is operating in ARCHIVELOG MANUAL 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.

 

ORA-16179	ORA-16179: incremental changes to "string" not allowed with SPFILE
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.

 

ORA-16180	ORA-16180: number processes specified for MAX_PARALLEL_SERVERS is too small
Cause	The max number of parallel servers available for Logical Standby is less than 5 becase of the limit imposed by the too small value of MAX_PARALLEL_SERVERS.
Action	Adjust the values of the initialization parameters PARALLEL_MAX_SERVERS to be at least 5.

 

ORA-16181	ORA-16181: SGA specified for Logical Standby is too large
Cause	MAX_SGA is larger than the larger of initialization parameters SHARED_POOL_SIZE and SGA_TARGET.
Action	Specify the value of MAX_SGA to be less than the maximum of SHARED_POOL_SIZE and SGA_TARGET. Likely only 75% or lower.

 

ORA-16182	ORA-16182: Internal error on internal channel during remote archival
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.

 

ORA-16184	ORA-16184: DB_UNIQUE_NAME string hashes to the same value as DB_UNIQUE_NAME string
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.

 

ORA-16185	ORA-16185: REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive
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.

 

ORA-16186	ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID="*" qualifier
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.

 

ORA-16187	ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
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.

 

ORA-16188	ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
Cause	The settings for the LOG_ARCHIVE_CONFIG parameter are inconsistent with the settings of a previously started instance. The settings for this parameter must be exactly the same for all instances.
Action	Make sure all instances use the exact same LOG_ARCHIVE_CONFIG settings.

 

ORA-16191	ORA-16191: Primary log shipping client not logged on standby
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.

 

ORA-16192	ORA-16192: Primary and standby network integrity mismatch
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.

 

ORA-16193	ORA-16193: Primary and standby network encryption mismatch
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.

 

ORA-16194	ORA-16194: Modifying DB_UNIQUE_NAME requires SID="*" qualifier
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.

 

ORA-16195	ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
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.

 

ORA-16196	ORA-16196: database has been previously opened and closed
Cause	The instance has already opened and closed the database, which is allowed only once in its lifetime.
Action	Shut down the instance.

 

ORA-16197	ORA-16197: Invalid DB_UNIQUE_NAME parameter specification
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.

 

ORA-16198	ORA-16198: Timeout incurred on internal channel during remote archival
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.

 

ORA-16199	ORA-16199: Terminal recovery failed to recover to a consistent point
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.

 

ORA-16200	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.

 

ORA-16201	ORA-16201: Skip procedure requested to apply statement
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.

 

ORA-16202	ORA-16202: Skip procedure requested to replace statement
Cause	Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16203	ORA-16203: Unable to interpret skip procedure return values
Cause	The skip procedure returned conflicting or invalid values.
Action	Ensure that the new_statement output parameter is non-NULL when returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE and NULL otherwise. Also ensure SKIP_ACTION is specified correctly.

 

ORA-16204	ORA-16204: DDL successfully applied
Cause	A DDL statement has successfully commited on the logical standby database.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16205	ORA-16205: DDL skipped due to skip setting
Cause	A setting in the logical standby skip table indicates that this type of DDL should always be skipped.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16206	ORA-16206: database already configured as Logical Standby database
Cause	This database has been previously configured as a Logical Standby database. A Logical Standby database is not capable of processing the requested operation.
Action	Ensure that you entered the command on the correct database as this database is a Logical Standby and is not capable of servicing the request.

 

ORA-16207	ORA-16207: Logical standby dictionary build not permitted.
Cause	A dictionary build is currently in progress. Only one build can be active at a time.
Action	Wait for the active build to complete before invoking a new build.

 

ORA-16208	ORA-16208: Logical standby dictionary build failed to start.
Cause	Failure to start the logical standby dictionary build process (LSP1)"
Action	Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

 

ORA-16209	ORA-16209: Logical standby dictionary build failed to complete.
Cause	The logical standby dictionary build process terminated abnormally."
Action	Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

 

ORA-16210	ORA-16210: Logical standby coordinator process terminated with error
Cause	The logical standby coordinator process terminated abnormally."
Action	Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

 

ORA-16211	ORA-16211: unsupported record found in the archived redo log
Cause	Log apply services encountered a record in the archived redo log that could not be interpreted.
Action	1. Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table on the standby database or simply drop the table if it"s unimportant.

 

ORA-16212	ORA-16212: number processes specified for APPLY is too great
Cause	Logical standby apply engine was started with more processes requested than are available.
Action	Adjust the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.

 

ORA-16213	ORA-16213: ddl encountered, stopping apply engine
Cause	stop_on_ddl callout specified and DDL was encountered.
Action	Either disable stop_on_ddl callout or remove DDL.

 

ORA-16214	ORA-16214: apply stalled for apply delay
Cause	A delay has been specified on the primary database for this destination.
Action	Either turn off the delay on the primary or use DBMS_LOGSTDBY.APPLY_UNSET("APPLY_DELAY"); to override.

 

ORA-16215	ORA-16215: history metadata inconsistency
Cause	internal error.
Action	This is an internal error. Contact Oracle support.

 

ORA-16216	ORA-16216: Log stream sequence error
Cause	The log stream being processed did not follow the last processed stream.
Action	If the database is in an active configuration, issue an ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY command to synchronize log stream data with the current primary database. If the database is not in an active configuration, manually add the next dictionary-begin logfile that followed the previous log stream.

 

ORA-16217	ORA-16217: prepare to switchover has not completed
Cause	An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but the prepare activity did not complete.
Action	Verify that the standby was prepared properly. You may cancel the prepare and perform an unprepared switchover which requires a database link to complete. Or reissue the prepare operation on the standby.

 

ORA-16218	ORA-16218: This database is already preparing to switch over.
Cause	The database was already preparing to switch over and was not able to accomodate another prepare attempt.
Action	Cancel the current prepare attempt with the ALTER DATABASE PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare request.

 

ORA-16219	ORA-16219: This database is not preparing to switch over.
Cause	The database was not preparing to switch over. Therefore, it was not possible to cancel the SWITCHOVER command.
Action	Preparing for the SWITCHOVER command can be accomplished with the ALTER DATABASE PREPARE TO SWITCHOVER command.

 

ORA-16220	ORA-16220: no failed transaction found
Cause	No failed transaction was found.
Action	Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command without the SKIP FAILED TRANSACTION option.

 

ORA-16221	ORA-16221: history table synchronization error
Cause	internal error.
Action	This is an internal error. Contact Oracle support.

 

ORA-16222	ORA-16222: automatic Logical Standby retry of last action
Cause	A failure occurred while running Logical Standby apply. A new attempt is automatically being made by Logical Standby apply.
Action	No action is necessary. This informational statement is provided to record the event for diagnostic purposes.

 

ORA-16223	ORA-16223: DDL skipped, unsupported in current version
Cause	The given DDL statement was not supported in the current version of Logical Standby and was skipped.
Action	No action is necessary. This informational statement is provided to record the event for diagnostic purposes.

 

ORA-16224	ORA-16224: Database Guard is enabled
Cause	Operation could not be performed because database guard is enabled
Action	Verify operation is correct and disable database guard

 

ORA-16225	ORA-16225: Missing LogMiner session name for Streams
Cause	An attempt was made to register the log file for Streams without a specified LogMiner session name.
Action	Specify a valid LogMiner session name to which the log file will be registered.

 

ORA-16226	ORA-16226: DDL skipped due to lack of support
Cause	Logical Standby does not support this type of DDL in this version, so the DDL is skipped.
Action	The DBA may apply the DDL explicitly at a later time or a procedure to handle this type of DDL can be created. see DBMS_LOGSTDBY.SKIP procedure for details.

 

ORA-16227	ORA-16227: DDL skipped due to missing object
Cause	A table or other database object upon which this DDL depends is not defined on the Logical Standby database.
Action	No action is necessary, this infomational statement is provided to record the event for diagnostic purposes.

 

ORA-16228	ORA-16228: Insufficient recovery for logical standby
Cause	Insufficient amount of recovery was run for logical standby instantiation.
Action	Continue to recover the database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE.

 

ORA-16229	ORA-16229: PDML child string string string for parent string string string cannot be skipped.
Cause	A request was made to skip a parallel DML child transaction id. This is not supported.
Action	Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove the child transaction id, then specify the parent transaction id using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate.

 

ORA-16230	ORA-16230: committing transaction string string string
Cause	Logical Standby apply was committing changes for the given transaction.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16231	ORA-16231: DDL barrier
Cause	Logical Standby was holding back changes until dependent changes were applied.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16232	ORA-16232: adding Logical Standby skip entry for table string.string
Cause	Table was previously unsupported due to datatype or storage attribute definitions. Table is now capable of being supported.
Action	To have Logical Standby maintain the table, import that table directly from the primary.

 

ORA-16233	ORA-16233: The table string.string is unsupported now
Cause	Table was previously supported but now is unsupported due to altered datatype or storage attribute definitions.
Action	None.

 

ORA-16234	ORA-16234: restarting to reset Logical Standby apply
Cause	Logical Standby encountered a work load that required a restart to properly reschedule.
Action	No action necessary. This informational statement is provided to record the event for diagnostic purposes.

 

ORA-16235	ORA-16235: DDL skipped because import has occurred
Cause	An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export.
Action	No action necessary. This informational statement is provided to record the event for diagnostic purposes.

 

ORA-16236	ORA-16236: Logical Standby metadata operation in progress
Cause	The requested operation failed because a Logical Standby metadata operation, such as DBMS_LOGSTDBY.SET_TABLESPACE or DBMS_LOGSTDBY.INSTANTIATE_TABLE, has not finished.
Action	Wait for the Logical Standby metadata operation to finish, then re-enter or respecify the operation.

 

ORA-16237	ORA-16237: SGA specified for Logical Standby is too small
Cause	MAX_SGA must be at least 10 Megabytes for proper functioning of Logical Standby.
Action	Specify the value of MAX_SGA to be greater than or equal to 10Mb. Alternatively, increase the shared_pool_size/sga_target so that 1/4 of it will amount to 10 Megabytes.

 

ORA-16238	ORA-16238: attempt to use version 9 log
Cause	Version 9 log files are not supported.
Action	Use log files of a supported version.

 

ORA-16239	ORA-16239: IMMEDIATE option not available without standby redo logs
Cause	The IMMEDIATE option cannot be used without standby redo logs.
Action	Do not specify the IMMEDIATE option unless standby redo logs are being used."

 

ORA-16240	ORA-16240: Waiting for logfile (thread# string, sequence# string)
Cause	Reader process is idle waiting for additional logfile to be available.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16241	ORA-16241: Waiting for gap logfile (thread# string, sequence# string)
Cause	Reader process is idle waiting for the logfile to fill the log sequence gap.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16242	ORA-16242: Processing logfile (thread# string, sequence# string)
Cause	Reader process is processing the logfile.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16243	ORA-16243: paging out string bytes of memory to disk
Cause	Builder process is paging out momery to free up space in lcr cache.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16244	ORA-16244: taking checkpoint and paging out string bytes to disk
Cause	Builder process is taking a checkpoint to advance restart_scn
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16245	ORA-16245: paging in transaction string, string, string
Cause	Builder process is paging in transactions from disk.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16246	ORA-16246: User initiated abort apply successfully completed
Cause	SQL Apply was stopped using the abort option.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16247	ORA-16247: DDL skipped on internal schema
Cause	Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM. For a complete list of internal schemas ignored by Logical Standby perform the following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt = "INTERNAL SCHEMA".
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16248	ORA-16248: RFS connections not permitted during Terminal Apply
Cause	Writes by RFS are not permitted while Logical Standby is performing Terminal Apply.
Action	Permit any outstanding Logical Standby operations to complete.

 

ORA-16249	ORA-16249: Terminal apply failed to complete during failover
Cause	The logical standby coordinator process terminated abnormally."
Action	Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the abnormal shutdown, and resolve accordingly. Once the problem has been rectified, reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE command to complete the failover.

 

ORA-16250	ORA-16250: Failed to acquire starting scn of new log stream
Cause	The starting SCN for the new log stream could not be determined.
Action	Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command.

 

ORA-16251	ORA-16251: LSP1 Background Build not permitted
Cause	The LSP1 background process is not permitted to start because it had previously been attempted.
Action	This is an internal error. Contact Oracle support.

 

ORA-16252	ORA-16252: Rebuild operation not permitted
Cause	The REBUILD operation is not permitted.
Action	Only on a primary database that has failed to complete the LogMiner dictionary build may the REBUILD operation take place. Reissue the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed to complete.

 

ORA-16253	ORA-16253: Logical Standby cannot start due to incomplete terminal apply
Cause	A previous ACTIVATE of the logical standby failed to complete.
Action	Reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE FINISH APPLY command.

 

ORA-16254	ORA-16254: change db_name to string in the client-side parameter file (pfile)
Cause	An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a server parameter file (spfile).
Action	The client-side parameter file must be edited so that db_name is set to the given name before mounting the database again.

 

ORA-16255	ORA-16255: Log Auto Delete conflicts with another LogMiner session
Cause	Log Auto Delete cannot be on while another LogMiner session is running on the same database.
Action	Start Logical Standby without Log Auto Delete or destroy other LogMiner sessions first.

 

ORA-16256	ORA-16256: Failure to complete standby redo logfile archival after failover
Cause	The standby redo logfiles processed during the failover of a logical standby were not archived.
Action	Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival.

 

ORA-16257	ORA-16257: Switchover initiated stop apply successfully completed
Cause	SQL Apply was stopped because of a switchover.
Action	No action necessary, this informational statement is provided to record the event for diagnostic purposes.

 

ORA-16258	ORA-16258: marking index unusable due to a constraint violation
Cause	A constraint violation occurred during the apply of a direct path load. The index will be marked unusable and the apply will be restarted.
Action	No action necessary. See alert log for index schema and name.

 

ORA-16259	ORA-16259: Switchover to logical standby requires a log archive destination
Cause	A valid log archive destination was not found to which the local system could archive the EOR logfile. A minimum of one destination is required.
Action	Ensure all log archive destinations are properly configured and, if applicable, have network connectivity before re-issuing the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY DDL operation.

 

ORA-16260	ORA-16260: Waiting to replace partial or corrupt logfile (thread# string, sequence# string)
Cause	LogMiner Reader process reached end of a partial logfile or encountered a corrupted block. It is now waiting for the logfile to be recovered and re-registered.
Action	No action necessary. Once the FAL archiver replaces the logfile, standby will automatically restart to process the replaced file.