{"id":2046,"date":"2016-08-04T11:10:35","date_gmt":"2016-08-04T08:10:35","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=2046"},"modified":"2016-12-12T09:24:05","modified_gmt":"2016-12-12T06:24:05","slug":"oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-00300-to-ora-00400","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-00300-to-ora-00400\/","title":{"rendered":"Oracle 12c R2 Error Codes and Solution Suggestions from ORA-00300 to ORA-00400"},"content":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-00300 to ORA-00400<\/strong><\/p>\n

\n
ORA-00300: illegal redo log block size\u00a0string\u00a0specified – exceeds limit of\u00a0string<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified block size of the redo log is greater than the maximum block size for the operating system.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Create the redo log on a device with a smaller block size<\/span><\/span><\/p>\n

\n
<\/a> ORA-00301: error in adding log file ‘string<\/i>‘ – file cannot be created<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The creation of the redo log file failed<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check: 1) there is enough storage space on the device 2) the name of the file is valid 3) the device is online 4) an IO error occurred Also, it is possible REUSE was specified on the command line and a file of the incorrect size exists. Either do not specify REUSE or use a file of the correct size.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00302: limit of\u00a0string<\/i>\u00a0logs exceeded<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The maximum number of redo log files has been exceeded.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES if the compatibility is lower than 10.2.0. Otherwise, allocate more storage space for the control file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00303: cannot process Parallel Redo<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A redo log containing Parallel Redo has been detected. The current Oracle release cannot process this format of redo.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a later release that supports Parallel Redo. to process this log.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00304: requested INSTANCE_NUMBER is busy<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either a) specify another INSTANCE_NUMBER, b) shut down the running instance with this number c) wait for instance recovery to complete on the instance with this number.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00305: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>\u00a0inconsistent; belongs to another database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database ID in the redo log file does not match the database ID in the control file. This redo log file is not from the current database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the correct redo log file, then retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00306: limit of\u00a0string<\/i>\u00a0instances in this database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0You cannot start more than the lower of a) port-specific limit as to the number of instances b) the number of instances specified at create-database time<\/span><\/span><\/p>\n

\n
<\/a> ORA-00307: requested INSTANCE_NUMBER out of range, maximum is\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The initialization parameter INSTANCE_NUMBER specified a number that was out of range.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Change INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is one and the maximum value is the lower of the operating system-specific maximum or the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation.<\/span><\/span>
\n<\/p>\n

\n
<\/a> ORA-00308: cannot open archived log ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The system cannot access a required archived redo log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check that the off line log exists, the storage device is online, and the archived file is in the correct location. Then attempt to continue recovery or restart the recovery session.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00309: log belongs to wrong database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The system cannot access the archived redo log because it belongs to another database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the correct redo log file, then retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00310: archived log contains sequence\u00a0string<\/i>; sequence\u00a0string<\/i>\u00a0required<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archived log was out of sequence, probably because it was corrupt or the wrong redo log file name was specified during recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the correct redo log file; then retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00311: cannot read header from archived log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An I\/O error occurred when attempting to read the log file header from the specified archived redo log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Other messages will accompany this message. See the associated messages for the appropriate action to take.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00312: online log\u00a0string<\/i>\u00a0thread\u00a0string<\/i>: ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This message reports the filename for details of another message.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Other messages will accompany this message. See the associated messages for the appropriate action to take.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00313: open failed for members of log group\u00a0string<\/i>\u00a0of thread\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The online log cannot be opened. May not be able to find file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See accompanying errors and make log available.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00314: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>, expected sequence#\u00a0string<\/i>\u00a0doesn’t match\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The online log is corrupted or is an old version.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find and install correct version of log or reset logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00315: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>, wrong thread #\u00a0string<\/i>\u00a0in header<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The online log is corrupted or is an old version.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find and install correct version of log or reset logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00316: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>, type\u00a0string<\/i>\u00a0in header is not log file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The online log is corrupted or is an old version.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find and install correct version of log or reset logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00317: file type\u00a0string<\/i>\u00a0in header is not log file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This is not an archived log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find the correct file and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00318: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>, expected file size\u00a0string<\/i>\u00a0doesn’t match\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0On header read the file size indicated in the control file did not match the file size contained in the log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore correct file or reset logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00319: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>\u00a0has incorrect log reset status<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Check of log file header at database open found that an online log has log reset data that is different from the control file. The log is probably an incorrectly restored backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore correct file or reset logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00320: cannot read file header from log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The file is not available.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the log file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00321: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>, cannot update log file header<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Cannot write to the log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the access to the file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00322: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>\u00a0is not current copy<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Check of log file header at database open found that an online log appears to be an incorrectly restored backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore correct file or reset logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00323: Current log of thread\u00a0string<\/i>\u00a0not useable and all others need archiving<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs need to be archived before they can be used.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Archive the logs for the thread then retry open.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00324: log file ‘string<\/i>‘ translated name ‘string<\/i>‘ too long,\u00a0string<\/i>\u00a0characters exceeds\u00a0string<\/i>\u00a0limit<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0the translated name for a log file is too long.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Choose a untranslated name that yields a shorter translated name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00325: archived log for thread\u00a0string<\/i>, wrong thread #\u00a0string<\/i>\u00a0in header<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archived log is corrupted or for another thread. Can not use the log for applying redo.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find correct archived log.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00326: log begins at change\u00a0string<\/i>, need earlier change\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archived log supplied for recovery was generated after the log that is needed. Can not yet use the log for applying redo.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find correct archived log.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00327: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>, physical size\u00a0string<\/i>\u00a0less than needed\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A log file has shrunk in size. This is likely to have been caused by operator or operating system error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the log file from backup. If backup is not available, drop this log and re-create. If the database was shut down cleanly, no further action should be required; otherwise incomplete recovery may be required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00328: archived log ends at change\u00a0string<\/i>, need later change\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archived log supplied for recovery was generated before the log that is needed. Can not use the log for applying redo.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find correct archived log.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00329: archived log begins at change\u00a0string<\/i>, need change\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archived log is not the correct log. An earlier log is needed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the correct log file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00330: archived log ends at change\u00a0string<\/i>, need change\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archived log is not the correct log. A later log is needed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the correct log file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00331: log version\u00a0string<\/i>\u00a0incompatible with ORACLE version\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The log was written by incompatible version of Oracle.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Recover the database with the compatible software, shut it down cleanly, then restart with current software.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00332: archived log is too small – may be incompletely archived<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The log is smaller than the space allocated in it. May be the result of a shutdown abort while it was being written by the archiver.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Get a complete version of this log and use it for recovery. There should either be an online version of it or a copy that was successfully archived.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00333: redo log read error block\u00a0string<\/i>\u00a0count\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An IO error occurred while reading the log described in the accompanying error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore accessibility to file, or get another copy of the file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00334: archived log: ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Reporting filename for details of another error<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See associated error messages<\/span><\/span><\/p>\n

\n
<\/a> ORA-00335: online log\u00a0string<\/i>: No log with this number, log does not exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Reporting filename for details of another error<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See associated error messages<\/span><\/span><\/p>\n

\n
<\/a> ORA-00336: log file size\u00a0string<\/i>\u00a0blocks is less than minimum\u00a0string<\/i>\u00a0blocks<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The log file size as specified in create database is too small.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase the log file size.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00337: log file ‘string<\/i>‘ does not exist and no size specified<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to add a log found neither an existing file nor a size for creating the file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a size for the log file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00338: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>\u00a0is more recent than control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The control file change sequence number in the log file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00339: archived log does not contain any redo<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The archived log is not the correct log. It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the correct log file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00340: IO error processing online log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An IO error occurred on the named online log.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore accessibility to file, or restore file from backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00341: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>, wrong log #\u00a0string<\/i>\u00a0in header<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The internal information in an online log file does not match the control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore correct file or reset logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00342: archived log does not have expected resetlogs SCN\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Recovery was given a log that does not belong to current incarnation or one of the parent incarnation. There should be another log that contains the correct redo.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply the correct log file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00344: unable to re-create online log ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An I\/O failure occurred when attempting to re-create an online as part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the file\/device as indicated by accompanying errors.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00345: redo log write error block\u00a0string<\/i>\u00a0count\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An IO error has occurred while writing the log<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the cause of the error, and then restart the system. If the log is lost, apply media\/incomplete recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00346: log member marked as STALE and closed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A log file member was no longer complete.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the underlying problem by referring to the other error messages found with this one.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00347: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>, expected block size\u00a0string<\/i>\u00a0doesn’t match\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0On header read the blocksize indicated in the control file did not match the blocksize contained in the log file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore correct file or reset logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00348: single-process redo failure. Must abort instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown abort and warmstart the database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00349: failure obtaining block size for ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The operating system was unable to determine the blocksize for the given filename.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Consult the accompanying error message, and correct the device or specify another filename.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00350: log\u00a0string<\/i>\u00a0of instance\u00a0string<\/i>\u00a0(thread\u00a0string<\/i>) needs to be archived<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The command cannot be done because the log has not been archived, and media recovery has been enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Archive the log or disable media recovery. If the command supports an UNARCHIVED option then it can be used. However this may result in making backups unuseable, and forcing the drop of some offline files.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00351: recover-to time invalid<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The time specified in a recover-until statement must be after January 1st 1988.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a time after January 1st 1988.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00352: all logs for thread\u00a0string<\/i>\u00a0need to be archived – cannot enable<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempting to enable a thread with all logs needing to be archived, and media recovery has been enabled. There is no log that can be made the new current log for the thread.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Archive a log for the thread or disable media recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00353: log corruption near block\u00a0string<\/i>\u00a0change\u00a0string<\/i>\u00a0time\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do recovery with a good version of the log or do incomplete recovery up to the indicated change or time.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00354: corrupt redo log block header<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The block header on the redo block indicated by the accompanying error, is not reasonable.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do recovery with a good version of the log or do time based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00355: change numbers out of order<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A change number found in the redo log is lower than a previously encountered change number. The log is corrupted in some way. The corruption may be at the earlier change or at this one.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do recovery with a good version of the log or do time based recovery up to the indicated time.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00356: inconsistent lengths in change description<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A change record in the redo log contains lengths that do not add up to a consistent value. The log is corrupted in some way.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do recovery with a good version of the log or do time based recovery up to the indicated time.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00357: too many members specified for log file, the maximum is\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An add logfile or add logfile member command would result in a log with too many members. The number of members is set when the database is created.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use fewer log file members.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00358: Too many file members specified, the maximum is\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A create or alter statement specified too many members in a parenthesised file list.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a number of file members that is within the port-defined limit.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00359: logfile group\u00a0string<\/i>\u00a0does not exist<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An add logfile member or drop logfile request specified a logfile group number that does not exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the configuration of the log files and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00360: not a logfile member:\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A filename was given to drop logfile member that is not a part of the database, or which is a data file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply a valid logfile member name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00361: cannot remove last log member\u00a0string<\/i>\u00a0for group\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt has been made to remove the last member of a log file group.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If desired, delete the entire log, by using DROP LOGFILE.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00362: member is required to form a valid logfile in group\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A request to drop a logfile member was denied because it would remove data required to form a complete logfile.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If desired, delete the entire log (after archiving if required), by using DROP LOGFILE;<\/span><\/span><\/p>\n

\n
<\/a> ORA-00363: log is not the archived version<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The log given to recovery is a backup of the online version from the time it was the current log. The archived version of the log would not be marked as end of thread. This error can also be caused by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find the archived version of the log and supply its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00364: cannot write header to new log member<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An i\/o error occurred when attempting to write the header to a log member that is being added to an existing group.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See accompanying errors. Fix problem or use another file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00365: the specified log is not the correct next log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified log failed to pass checks to ensure it corresponds to the log that was just applied. This is probably the result of using a log that was generated against a cold backup image of the database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find the log that was generated by this copy of the database and give that filename to recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00366: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>, checksum error in the file header<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find and install correct version of log or reset logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00367: checksum error in log file header<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Find the correct file and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00368: checksum error in redo log block<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The redo block indicated by the accompanying error, is not vaild. It has a checksum that does not match the block contents.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do recovery with a good version of the log or do time based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database. Restore correct file or reset logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00369: Current log of thread\u00a0string<\/i>\u00a0not useable and other log being cleared<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs are being cleared or need to be archived before they can be used.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If the ALTER DATABASE CLEAR LOGFILE command is still active then wait for it to complete. Otherwise reissue the CLEAR command. If there are other online logs for the thread, that are not being cleared, then archive the logs.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00370: potential deadlock during kcbchange operation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Error code used internally by software. Should never be reported<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Treat as internal error. See error 600.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00371: not enough shared pool memory, should be at least\u00a0string<\/i>\u00a0bytes<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The SHARED_POOL_SIZE initialization parameter was too small.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase the parameter value.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00372: file\u00a0string<\/i>\u00a0cannot be modified at this time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0attempting to modify the contents of a file that cannot be modified. The file is most likely part of a read only tablespace but may be in the process of going offline, or the database may be in the process of closing.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0check the status of the file and its tablespace<\/span><\/span><\/p>\n

\n
<\/a> ORA-00373: online log version\u00a0string<\/i>\u00a0incompatible with ORACLE version\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The online log was written by incompatible version of Oracle. Can occur when the log file was created by either a new or older version of Oracle.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Recover the database with the compatible software, shut it down cleanly, then restart with current software.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00374: parameter db_block_size =\u00a0string<\/i>\u00a0invalid ; must be a multiple of\u00a0string<\/i>\u00a0in the range [string<\/i>..string<\/i>]<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0invalid value for db_block_size parameter<\/span><\/span><\/p>\n

Action:<\/b>\u00a0adjust parameter and restart<\/span><\/span><\/p>\n

\n
<\/a> ORA-00376: file\u00a0string<\/i>\u00a0cannot be read at this time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0attempting to read from a file that is not readable. Most likely the file is offline.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the state of the file. Bring it online<\/span><\/span><\/p>\n

\n
<\/a> ORA-00377: Frequent backups of file\u00a0string<\/i>\u00a0causing write operation to stall<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Backups are occurring too frequently on this file. Each time a new backup is started for a file, any writes which have been previously issued (but not completed) have to be re-issued. If hot backups are started very, very frequently, it is possible that some writes will be re-issued repeatedly and never complete.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase the interval between begin hot-backup commands for this file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00378: buffer pools cannot be created as specified<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Either the number of buffers or the number of lru latches is too small to satisfy the specified buffer pool configuration.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either increase the number of buffers and\/or number of lru latches or configure smaller buffer pools.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00379: no free buffers available in buffer pool\u00a0string<\/i>\u00a0for block size\u00a0string<\/i>K<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0All buffers in the specified buffer pool for the specified block size are in use and no free buffers are available.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase the number of buffers in the specified pool for the specified block size<\/span><\/span><\/p>\n

\n
<\/a> ORA-00380: cannot specify db_string<\/i>k_cache_size since\u00a0string<\/i>K is the standard block size<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0User specified the parameter db_nk_cache_size (where n is one of 2,4,8,16,32), while the standard block size for this database is equal to n Kbytes. This is illegal.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the standard block size cache using db_cache_size (DEFAULT pool) (and db_recycle_cache_size, db_keep_cache_size if additional buffer pools are required). Do NOT use the corresponding db_nk_cache_size parameter for the standard block size.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00381: cannot use both new and old parameters for buffer cache size specification<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0User specified one or more of { db_cache_size , db_recycle_cache_size, db_keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32), db_cache_advice } AND one or more of { db_block_buffers, buffer_pool_keep , buffer_pool_recycle }. This is illegal.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use EITHER the old (pre-Oracle_8.2) parameters OR the new ones. Don’t specify both. If old size parameters are specified in the parameter file, you may want to replace them with new parameters since the new parameters can be modified dynamically and allow you to configure additional caches for additional block sizes. Cache advisory can only be enabled with the new cache parameters.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00382:\u00a0string<\/i>\u00a0not a valid block size, valid range [string<\/i>..string<\/i>]<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0User specified a value for db_nk_cache_size where n is one of {2, 4, 8, 16, 32}, but nk is not a valid block size for this platform.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Remove corresponding parameter from the “init.ora” file and restart the instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00383: DEFAULT cache for blocksize\u00a0string<\/i>\u00a0cannot be reduced to zero<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0User attempted to reduce db_cache_size to zero, or attempted to to reduce db_n<\/i>K_cache_size to zero while there were still online tablespaces with blocksize\u00a0n<\/i>K. Note that since the SYSTEM tablespace cannot be taken offline, it is always illegal to set db_cache_size to zero.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Offline any tablespaces with the corresponding blocksize and then perform the operation again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00384: Insufficient memory to grow cache<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The system could not allocate sufficient memory to grow the cache to the specified size.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Attempt a smaller increase in the value of the parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00388: dependent redo for buffers is lost<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The instance contained buffers that had non-durable changes and depended on redo in another thread that was lost because of that thread crash. No data are lost because changes to such buffers cannot be commited while they are non-durable.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restart the instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00390: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>\u00a0is being cleared, cannot become current log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be useable when the clearing completes. The command that began the clearing may have terminated without completing the clearing.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00391: All threads must switch to new log format at the same time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to switch the current log of a single thread is not allowed because the compatiblity requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Open the database to cause the coordinated log switch. If that is not possible then return to the same software version and compatibility setting last used to open the database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00392: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>\u00a0is being cleared, operation not allowed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00393: log\u00a0string<\/i>\u00a0of thread\u00a0string<\/i>\u00a0is needed for recovery of offline datafiles<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared the tablespaces containing the files will have to be dropped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Archive the log then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptible, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00394: online log reused while attempting to archive it<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0It has been detected that an online log that is being archived has been reused<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Cannot archive the logfile anymore since it has been overwritten<\/span><\/span><\/p>\n

\n
<\/a> ORA-00395: online logs for the clone database must be renamed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A clone database open forces logfile renaming to avoid overwriting the primary logfiles<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Rename the logfiles manually or using the log_file_name_convert initialization parameter<\/span><\/span><\/p>\n

\n
<\/a> ORA-00396: error\u00a0string<\/i>\u00a0required fallback to single-pass recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the cause of the indicated error (also recorded) so that future instance or crash recovery can succeed with the two-pass algorithm. This usually requires making more main memory available to the recovery process.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00397: instance recovery process terminated with error<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The foreground process doing instance recovery died.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the foreground trace file for the cause of recovery failure.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00398: abort thread recovery due to reconfiguration<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Global enqueue service reconfiguration occurred during instance\/crash recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is used internally, no action is required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00399: corrupt change description in redo log<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A change vector in the redo log failed validation checks.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do recovery with a good version of the log or do time based recovery up to the indicated time.<\/span><\/span><\/p>\n

\n
<\/a> ORA-00400: invalid release value\u00a0string<\/i>\u00a0for parameter\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The release level given for the specified init parameter is invalid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the parameter value in the parameter file and retry.<\/span><\/span><\/p>\n

\n
<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-00300 to ORA-00400 ORA-00300: illegal redo log block size\u00a0string\u00a0specified – exceeds limit of\u00a0string Cause:\u00a0The specified block size of the redo log is greater than the maximum block size for the operating system. Action:\u00a0Create the redo log on a device with a smaller block size ORA-00301: error…<\/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":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[54],"class_list":["post-2046","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-x0","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2046","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=2046"}],"version-history":[{"count":2,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2046\/revisions"}],"predecessor-version":[{"id":2111,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2046\/revisions\/2111"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=2046"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=2046"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=2046"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}