{"id":1935,"date":"2016-04-30T10:24:56","date_gmt":"2016-04-30T07:24:56","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=1935"},"modified":"2016-10-26T10:26:16","modified_gmt":"2016-10-26T07:26:16","slug":"oracle-11g-error-codes-and-solution-suggestions-from-ora-16100-to-ora-16200","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-11g-error-codes-and-solution-suggestions-from-ora-16100-to-ora-16200\/","title":{"rendered":"Oracle 11g Error Codes and Solution Suggestions from ORA-16100 to ORA-16200"},"content":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-16100 to ORA-16200<\/strong><\/p>\n

\n
ORA-16100: not a valid Logical Standby database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This database has not been completely configured as a Logical Standby database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16101: a valid start SCN could not be found<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An SCN from which to start could not be found.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Register 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16102: remote information is not available on the specified primary<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The new primary has not completed generating the necessary information for the standby to begin consuming its log stream.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16103: Logical Standby apply must be stopped to allow this operation<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or respecify the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16104: Invalid Logical Standby parameter<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified parameter is not valid.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check spelling or refer to the DBMS_LOGSTDBY PL\/SQL package documentation for the correct statement syntax.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16105: Logical Standby is already running in background<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A Logical Standby apply operation is already running.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0None<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16106: loading previously applied transaction information<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical Standby coordinator was performing a scan to identify previously applied transactions.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary. This informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16107: all log data from primary has been processed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0On the primary system, the log stream has been ended by the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Issue 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;<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16108: database is no longer a standby database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The current database has already been made a primary database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Issue 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;<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16109: failed to apply log data from previous primary<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Log data from previous primary could not be completely applied.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0. Then, reissue command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16110: user procedure processing of logical standby apply DDL<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16111: log mining and apply setting up<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This logical standby process is setting up to begin processing changes.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n

<\/p>\n

<\/a><\/a>ORA-16112: log mining and apply stopping<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This logical standby process is cleaning up and stopping Logical Standby apply.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16113: applying change to table or sequence\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The process is applying changes to a specific schema object.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16114: applying DDL transaction with commit SCN\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The process is applying a DDL change that’s committed at the given SCN.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16115:\u00a0string<\/i>\\% of LogMiner dictionary loading is done<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The process is loading dictionary information from the redo stream. This activity may take a few minutes.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16116: no work available<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The process is idle waiting for additional changes to be made available.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16117: processing<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The process is performing its primary function and is not waiting on any significant event.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16119: building transaction at SCN\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The transaction being committed at the given SCN is being prepared for apply.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16120: dependencies being computed for transaction at SCN\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The transaction committed at the given SCN is being analyzed for dependencies.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16121: applying transaction with commit SCN\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The transaction committed at the given SCN is being applied.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16122: applying large dml transaction at SCN\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16123: transaction\u00a0string<\/i>\u00a0string<\/i>\u00a0string<\/i>\u00a0is waiting for commit approval<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16124: transaction\u00a0string<\/i>\u00a0string<\/i>\u00a0string<\/i>\u00a0is waiting on another transaction<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The apply process is waiting to apply additional changes. This transaction likely depends on another.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16125: large transaction\u00a0string<\/i>\u00a0string<\/i>\u00a0string<\/i>\u00a0is waiting for more data<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16126: loading table or sequence\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Information on the given table or sequence is being loaded into an in memory cache for future use.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16127: stalled waiting for additional transactions to be applied<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16128: User initiated stop apply successfully completed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby was shutdown in an orderly fashion.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16129: unsupported DML encountered<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0One or more DMLs to an unsupported table were encountered and skipped.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16130: supplemental log information is missing from log stream<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Supplemental logging is not enabled at the primary database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Issue the following command to enable supplemental logging. ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16131: An error occurred during a Terminal Recovery of the standby.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An error occurred during a Terminal Recovery of the standby.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the standby alert log additional information.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16132: An error occurred during activation of the standby.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An error occurred during activation of the standby database following a Terminal Recovery.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the standby alert log additional information.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16133: Datafile\u00a0string<\/i>\u00a0has incorrect terminal recovery stamp.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0After 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16134: invalid MANAGED recovery FINISH option<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A mode other than NOWAIT follows the FINISH keyword in RECOVER MANAGED STANDBY DATABASE statement.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify either nothing or NOWAIT following FINISH.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected mode<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Make the modification before the database is opened by any instance.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16136: Managed Standby Recovery not active<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to cancel a managed recovery session but no managed recovery session was active.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is necessary.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16138: end of log stream not received from primary<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16139: media recovery required<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An error has occurred while performing a switchover.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16140: standby online logs have not been recovered<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0To 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16143: RFS connections not allowed during or after terminal recovery<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The primary must not attempt to archive to the standby after a terminal recovery.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16145: archival for thread#\u00a0string<\/i>\u00a0sequence#\u00a0string<\/i>\u00a0in progress<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The indicated archived log file is not available for recovery due to the fact that it is still being archived.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify that archival of the indicated log file has completed and reissue the RECOVER STANDBY DATABASE command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16146:\u00a0string<\/i>control file enqueue unavailable<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The control file enqueue is currently unavailable.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No Action is required. We will try to re-fetch it at a later time.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16147: standby database referenced by multiple archive log destinations<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Multiple archive log destinations reference the same standby database, using different service names. This is not allowed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Remove one of the duplicate archive log destinations.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16148: user requested expiration of managed recovery operation<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16150: FINISH recovery performed on another, older standby database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16151: Managed Standby Recovery not available<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The attempted operation failed because of a pending CANCEL of the managed standby recovery operation.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Wait for the managed standby recovery session to end. Then retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16152: standby database is in ‘no-data-loss’ protected mode<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The attempted database operation is not allowed while the standby database is in ‘no-data-loss’ protected mode.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16154: suspect attribute:\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Use of the indicated attribute is illegal in the given context.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Make the appropriate changes and reissue the statement.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16156: LGWR archive log dependency not allowed if database is standby protected<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Remove the LGWR archive log dependency and use normal LGWR archival instead.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16157: media recovery not allowed following successful FINISH recovery<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Issue one of these operations following a FINISH recocvery: ALTER DATABASE OPEN READ ONLY or ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16159: Cannot change protected standby destination attributes<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16160: Cannot change protected standby database configuration<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to change the standby database configuration when the primary database is in standby protected mode.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The standby database must be added to the configuration before the primary database is opened.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16161: Cannot mix standby and online redo log file members for group\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify the log file group type using the TYPE column of the V$LOG fixed view.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16162: Cannot add new standby databases to protected configuration<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The standby database must be added to the configuration before the primary database is opened.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16163: LGWR network server host attach error<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The LGWR network server could not attach to remote host<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16164: LGWR network server host detach error<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The LGWR network server could not detach from remote host<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16165: LGWR failed to hear from network server<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The LGWR lost its connection to the network server<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16166: LGWR network server failed to send remote message<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The LGWR network server could not communicate with the remote host<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16167: LGWR network server could not switch to non-blocking mode<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The LGWR network server could not switch to non-blocking mode<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16168: LGWR network server could not switch to blocking mode<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The LGWR network server could not switch to blocking mode<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16169: LGWR network server invalid parameters<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The LGWR network server could not switch to blocking mode<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The alert log contains more problem-specific information<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16170: Terminal recovery may have left the database in an inconsistent state<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0When 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Continue standby recovery with additional log shipping from primary.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16171: RECOVER…FINISH not allowed due to gap for thr\u00a0string<\/i>, seq\u00a0string<\/i>–string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0See alert log for more details<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Copy 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16172: archive logs detected beyond Terminal End-Of-Redo<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0None<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16173: incompatible archival network connections active<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0One 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16174: user requested thread\/sequence termination of managed recovery<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The managed standby database recovery operation has been terminated per user specified THROUGH THREAD\/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16175: cannot shut down database when media recovery is active<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to shut down a standby database while media recovery was active.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Cancel media recovery to proceed with the shutdown.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16176: background dictionary build cannot be running<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The background process dedicated to dictionary build is active.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0wait and try it later.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16177: media recovery is not required<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is necessary. The standby database may be activated as a new primary or may continue as a standby.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16178: Cannot specify remote destinations in manual archiving mode<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database is operating in manual archiving mode. Remote archivelog destinations are not allowed in this mode.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use the ALTER DATABASE ARCHIVELOG command to place the database in automatic ARCHIVELOG mode, or defer the archivelog destinations that specify the SERVICE= attribute.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16179: incremental changes to “string<\/i>” not allowed with SPFILE<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Incremental changes to a log_archive_dest_n parameter cannot be made when using an SPFILE.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify either LOCATION or SERVICE plus all other attributes to be set in one ALTER SYSTEM\/SESSION SET command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16180: number of processes specified is too large<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The number of server processes available for Logical Standby is currently limited to 1024 LogMiner processes and 1024 apply processes or a total of 2048.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Retry with a lower value.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16181: SGA specified for Logical Standby is too large<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0MAX_SGA is larger than 75% of the larger of initialization parameters SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify the value of MAX_SGA to be less than 75% of the maximum of SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16182: Internal error on internal channel during remote archival<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An internal error was encountered on the internal channel between LGWR and Network Server.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required, as an attempt will be made to re-archive the file that had this failure during archival.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16184: DB_UNIQUE_NAME\u00a0string<\/i>\u00a0hashes to the same value as DB_UNIQUE_NAME\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The internal hash value generated for one DB_UNIQUE_NAME collided with the hash value of another DB_UNIQUE_NAME.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a different value.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16185: REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG parameters are defined in the initialization file and they are mutually exclusive.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use only the LOG_ARCHIVE_CONFIG parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID=’*’ qualifier<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly the same on all RAC instances so the SID=’*’ qualifier is required.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Re-enter the command using the SID=’*’ qualifier.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The LOG_ARCHIVE_CONFIG parameter was specified with duplicate, conflicting or invalid attributes.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the documentation regarding the correct specification of the LOG_ARCHIVE_CONFIG parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Make sure all instances use the exact same LOG_ARCHIVE_CONFIG settings.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16191: Primary log shipping client not logged on standby<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt to ship redo to standby without logging on to standby or with invalid user credentials.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16192: Primary and standby network integrity mismatch<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Standby wants sqlnet network integrity for redo shipment which is not configured properly at the primary.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check sqlnet.ora documentation regarding how to setup network integrity and set it up identically on both primary and standby. Restart primary and\/or standby.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16193: Primary and standby network encryption mismatch<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Standby wants sqlnet network encryption for redo shipment which is not configured properly at the primary.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check sqlnet.ora documentation regarding how to setup network encryption and set it up identically on both primary and standby. Restart primary and\/or standby.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16194: Modifying DB_UNIQUE_NAME requires SID=’*’ qualifier<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The setting for the DB_UNIQUE_NAME parameter must be exactly the same on all RAC instances so the SID=’*’ qualifier is required.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Re-enter the command using the SID=’*’ qualifier.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can only be used if the DB_UNIQUE_NAME parameter has been explicitly defined.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Explicitly define a valid DB_UNIQUE_NAME.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16196: database has been previously opened and closed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The instance has already opened and closed the database, which is allowed only once in its lifetime.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Shut down the instance.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16197: Invalid DB_UNIQUE_NAME parameter specification<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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 “#”.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the documentation and re-enter the parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16198: Timeout incurred on internal channel during remote archival<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A timeout was incurred during remote archival.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action is required, as an attempt will be made to re-archive the file that had this failure during archival.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16199: Terminal recovery failed to recover to a consistent point<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0See alert log for more details<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, call Oracle support.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-16200: Skip procedure requested to skip statement<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logical standby called a skip procedure that requested for a particular statement not to be applied.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action necessary, this informational statement is provided to record the event for diagnostic purposes.<\/span><\/span><\/span><\/dd>\n
<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-16100 to ORA-16200 ORA-16100: not a valid Logical Standby database Cause:\u00a0This database has not been completely configured as a Logical Standby database. Action:\u00a0Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY…<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[14,32,54],"class_list":["post-1935","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-database-administration","tag-oracle-administration","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-vd","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1935","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/comments?post=1935"}],"version-history":[{"count":1,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1935\/revisions"}],"predecessor-version":[{"id":1936,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1935\/revisions\/1936"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=1935"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=1935"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=1935"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}