Below are the list of Oracle ORA message from ORA-00301 to ORA-00400. You can find the cause and actions from each of the message accordingly.
| ORA MESSAGE | CAUSE / ACTION |
|---|---|
| ORA-00301 error in adding log file 'string' – file cannot be created | Cause: The creation of the redo log file failed Action: Check whether: - There is enough storage space on the device - The name of the file is valid - The device is online - An I/O 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. |
| ORA-00302 limit of string logs exceeded | Cause: The maximum number of redo log files has been exceeded. There is a limit set at database creation on the number of redo log files (typically 16). Action: Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES. |
| ORA-00303 cannot process Parallel Redo | Cause: A redo log containing Parallel Redo has been detected. The current Oracle release cannot process this format of redo. Action: Use a later release that supports Parallel Redo. |
| ORA-00304 requested INSTANCE_NUMBER is busy | Cause: An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use. Action: Either: - Specify another INSTANCE_NUMBER - Shut down the running instance with this number - Wait for instance recovery to complete on the instance with this number. |
| ORA-00305 log string of thread string inconsistent; belongs to another database | Cause: The 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. Action: Specify the correct redo log file and then retry the operation. |
| ORA-00306 limit of string instances in this database | Cause: Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances. Action: You cannot start more than the lower of: - the operating system-specific maximum or - the number of instances specified by the MAXINSTANCES option specified in the CREATE DATABASE statement |
| ORA-00307 requested INSTANCE_NUMBER out of range maximum is string | Cause: The initialization parameter INSTANCE_NUMBER specified a number that was out of range. Action: Change the value of INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is 1 and the maximum value is the lower of the operating system-specific maximum or the value of the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation. |
| ORA-00308 cannot open archived log 'string' | Cause: The system cannot access a required archived redo log file. Action: Check that the offline 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. |
| ORA-00309 log belongs to wrong database | Cause: The system cannot access the archived redo log because it belongs to another database. Action: Specify the correct redo log file and then retry the operation. |
| ORA-00310 archived log contains sequence string; sequence string required | Cause: The archived log is out of sequence probably because it is corrupted or the wrong redo log file name was specified during recovery. Action: Specify the correct redo log file and then retry the operation. |
| ORA-00311 cannot read header from archived log | Cause: An I/O error occurred when attempting to read the log file header from the specified archived redo log file. Action: Other messages will accompany this message. See the associated messages for the appropriate action to take. |
| ORA-00312 online log string thread string: 'string' | Cause: This message reports the file name for details of another message. Action: Other messages will accompany this message. See the associated messages for the appropriate action to take. |
| ORA-00313 open failed for members of log group string of thread string | Cause: The online log cannot be opened. The file may not be in the expected location. Action: Specify the correct redo log file or make the log available if necessary. Also see the accompanying messages. |
| ORA-00314 log string of thread string expected sequence# string doesn't match string | Cause: The online log is corrupted or is an old version. Action: Find and install the correct version of the log or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures. |
| ORA-00315 log string of thread string wrong thread # string in header | Cause: The online log is corrupted or is an old version. Action: Find and install the correct version of the log or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures. |
| ORA-00316 log string of thread string type string in header is not log file | Cause: The online log is corrupted or is an old version. Action: Find and install the correct version of the log or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures. |
| ORA-00317 file type string in header is not log file | Cause: This is not an archived log file. Action: Find the correct file and try again. Refer to the Oracle9i Database Administrator's Guide for recovery procedures. |
| ORA-00318 log string of thread string expected file size string doesn't match string | Cause: The file size indicated in the control file did not match the file size contained in the log file. Action: Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures. |
| ORA-00319 log string of thread string has incorrect log reset status | Cause: An online redo log has log reset data that is different from the log reset data in the control file. The log is probably an incorrectly restored backup. Action: Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures. |
| ORA-00320 cannot read file header from log string of thread string | Cause: The file is not available. Action: Restore the log file. |
| ORA-00321 log string of thread string cannot update log file header | Cause: Cannot write to the log file. Action: Restore access to the file. |
| ORA-00322 log string of thread string is not current copy | Cause: An online log appears to be an incorrectly restored backup. Action: Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures. |
| ORA-00323 Current log of thread string not useable and all others need archiving | Cause: An attempt to open the 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. Action: Archive the logs for the thread and then retry the open. |
| ORA-00324 log file 'string' translated name 'string' too long string characters exceeds string limit | Cause: The translated name for a log file is too long. Action: Choose an untranslated name that yields a shorter translated name. |
| ORA-00325 archived log for thread string wrong thread # string in header | Cause: The archived log is corrupted or for another thread. Cannot use the log for applying the redo. Action: Find the correct archived log. |
| ORA-00326 log begins at change string need earlier change string | Cause: The archived log supplied for recovery was generated after the log that is needed. Cannot yet use the log for applying redo. Action: Find the correct archived log. |
| ORA-00327 log string of thread string physical size string less than needed string | Cause: A log file has shrunk in size. This is likely to have been caused by a computer operator's mistake or an operating system error. Action: Restore the log file from backup. If a backup is not available drop this log and re-create it. If the database was shut down cleanly no further action should be required; otherwise incomplete recovery may be required. |
| ORA-00328 archived log ends at change string need later change string | Cause: The archived log supplied for recovery was generated before the log that is needed. Cannot use the log for applying redo. Action: Find the correct archived log. |
| ORA-00329 archived log begins at change string need change string | Cause: The archived log is not the correct log. An earlier log is needed. Action: Restore the correct log file. |
| ORA-00330 archived log ends at change string need change string | Cause: The archived log is not the correct log. A later log is needed. Action: Restore the correct log file. |
| ORA-00331 log version string incompatible with ORACLE version string | Cause: The log was written by an incompatible version of Oracle. Action: Recover the database with the compatible software shut it down cleanly and then restart Oracle with the current software. |
| ORA-00332 archived log is too small – may be incompletely archived | Cause: The 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. Action: Get 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. |
| ORA-00333 redo log read error block string count string | Cause: An I/O error occurred while reading the log described in the accompanying error. Action: Restore accessibility to file or get another copy of the file. |
| ORA-00334 archived log: 'string' | Cause: This message reports the file name involved with other errors. Action: See associated error messages. |
| ORA-00335 online log string: No log with this number log does not exist | Cause: This message reports the file name involved with other errors. Action: See associated error messages. |
| ORA-00336 log file size string blocks is less than minimum string blocks | Cause: The log file size as specified in the CREATE DATABASE statement is too small. Action: Increase the log file size. |
| ORA-00337 log file 'string' does not exist and no size specified | Cause: An attempt to add a log found neither an existing file nor a size for creating the file. Action: Specify a size for the log file. |
| ORA-00338 log string of thread string is more recent than controlfile | Cause: The 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. Action: Use 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. |
| ORA-00339 archived log does not contain any redo | Cause: The 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. Action: Restore the correct log file. |
| ORA-00340 IO error processing online log string of thread string | Cause: An I/O error occurred on the named online log. Action: Restore accessibility to the file or restore the file from backup. |
| ORA-00341 log string of thread string wrong log # string in header | Cause: The internal information in an online log file does not match the control file. Action: Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures. |
| ORA-00342 archived log was created before last RESETLOGS | Cause: Recovery was given a log that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another log created since then that contains the correct redo. Action: Supply the correct log file. |
| ORA-00343 too many errors log member closed | Cause: The maximum number of errors on this log member has been exceeded. Action: Correct the underlying problem by referring to the other error messages found with this one. |
| ORA-00344 unable to re-create online log 'string' | Cause: An I/O failure occurred when attempting to re-create an online log as part of either an ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command. Action: Correct the file/device as indicated by accompanying errors. |
| ORA-00345 redo log write error block string count string | Cause: An I/O error occurred while writing the log. Action: Correct the cause of the error and then restart the system. If the log is lost apply media/incomplete recovery. |
| ORA-00346 log member marked as STALE | Cause: A log file member no longer is complete. Action: Correct the underlying problem by referring to the other error messages found with this one. |
| ORA-00347 log string of thread string expected block size string doesn't match string | Cause: During online recovery the block size specified in the control file did not match the block size contained in the redo log file. Action: Restore the correct redo file from a backup or reset the online redo log files. |
| ORA-00348 single-process redo failure. Must abort instance | Cause: A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation. Action: SHUTDOWN ABORT and restart the database. |
| ORA-00349 failure obtaining block size for 'string' | Cause: The operating system was unable to determine the block size for the given file name. Action: Consult the accompanying error message and correct the device or specify another file name. |
| ORA-00350 log string of thread string needs to be archived | Cause: The command cannot be done because the log has not been archived and media recovery has been enabled. Action: Archive 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 unusable and forcing the drop of some offline files. |
| ORA-00351 recover-to time invalid | Cause: The time specified in a recover-until statement must be after January 1st 1988. Action: Specify a time after January 1st 1988. |
| ORA-00352 all logs for thread string need to be archived – cannot enable | Cause: An attempt was made 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. Action: Archive a log for the thread or disable media recovery. |
| ORA-00353 log corruption near block string change string time string | |
| Cause: Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption. Action: Perform recovery with a good version of the redo log or do incomplete recovery up to the indicated change or time. | |
| ORA-00354 corrupt redo log block header | Cause: The block header on the redo block indicated by the accompanying error is not valid. The block number and time-stamp are given in an accompanying message. Action: Perform recovery with a good version of the redo log or perform cancel-based recovery up to but not including the corrupted redo log file. 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. |
| ORA-00355 change numbers out of order | Cause: A 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. Action: Perform recovery with a good version of the log or perform time-based recovery up to the indicated time. |
| ORA-00356 inconsistent lengths in change description | Cause: A change record in the redo log contains lengths that do not add up to a consistent value. The log is corrupted in some way. Action: Perform recovery with a good version of the log or do time-based recovery up to the indicated time. |
| ORA-00357 too many members specified for log file the maximum is string | Cause: An 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. Action: Use fewer log file members. |
| ORA-00358 Too many file members specified the maximum is string | Cause: A CREATE or ALTER statement specified too many members in a parenthesised file list. Action: Specify a number of file members that is within the port-defined limit. |
| ORA-00359 logfile group string does not exist | Cause: An ADD LOGFILE MEMBER or DROP LOGFILE request specified a log file group number that does not exist. Action: Check the configuration of the log files and reissue the command. |
| ORA-00360 not a logfile member: string | Cause: A file name was given to DROP LOGFILE MEMBER command that is not a part of the database or which is a datafile. Action: Supply a valid log file member name. |
| ORA-00361 cannot remove last log member string for group string | Cause: An attempt has been made to remove the last member of a log file group. Action: If desired delete the entire log by using DROP LOGFILE. |
| ORA-00362 member is required to form a valid logfile in group string | Cause: A request to drop a log file member was denied because it would remove data required to form a complete log file. Action: If desired delete the entire log (after archiving if required) by using DROP LOGFILE. |
| ORA-00363 log is not the archived version | Cause: The 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. Action: Find 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. |
| ORA-00364 cannot write header to new log member | Cause: An I/O error occurred when attempting to write the header to a log member that is being added to an existing group. Action: See accompanying errors. Fix the problem or use another file. |
| ORA-00365 the specified log is not the correct next log | Cause: The 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. Action: Find the log that was generated by this copy of the database and give that file name to recovery. |
| ORA-00366 log string of thread string checksum error in the file header | Cause: The 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. Action: Find and install correct version of the log or reset the logs. |
| ORA-00367 checksum error in log file header | Cause: The 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. Action: Find the correct file and try again. |
| ORA-00368 checksum error in redo log block | Cause: The redo block indicated by the accompanying error is not valid. It has a checksum that does not match the block contents. Action: Perform recovery with a good version of the log or do time-based recovery up to the indicated time. If this happens when 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 the correct file or reset logs. |
| ORA-00369 Current log of thread string not useable and other log being cleared | Cause: An attempt to open the 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. Action: If 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. |
| ORA-00371 not enough shared pool memory | Cause: The SHARED_POOL_SIZE initialization parameter is too small. Action: Increase the parameter value. |
| ORA-00372 file string cannot be modified at this time | Cause: An attempt was made 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. Action: Check the status of the file and its tablespace. |
| ORA-00373 online log version string incompatible with ORACLE version string | Cause: The online log was written by an incompatible version of Oracle. This can occur when the log file was created by either a new or older version of Oracle. Action: Recover the database with the compatible software shut it down cleanly and then restart with current software. |
| ORA-00374 parameter db_block_size = string invalid; must be a multiple of string in the range [string..string] | Cause: An invalid value was specified for the DB_BLOCK_SIZE parameter. Action: Adjust the value of the parameter and restart the instance. |
| ORA-00375 unable to get default db_block_size | Cause: The system was unable to determine the default value for DB_BLOCK_SIZE. Action: See the accompanying system-specific error. As a workaround specify the block size in the initialization parameter file. |
| ORA-00376 file string cannot be read at this time | Cause: An attempt was made to read from a file that is not readable. Most likely the file is offline. Action: Check the state of the file. Bring it online. |
| ORA-00377 Frequent backups of file string causing write operation to stall | Cause: Backups 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 frequently it is possible that some writes will be re-issued repeatedly and never complete. Action: Increase the interval between begin hot-backup commands for this file. |
| ORA-00378 buffer pools cannot be created as specified | Cause: The number of buffers or the number of LRU latches is too small to satisfy the specified buffer pool configuration. Action: Either increase the number of buffers and/or number of LRU latches or configure smaller buffer pools. |
| ORA-00379 no free buffers available in buffer pool string for block size stringK | Cause: All buffers in the specified buffer pool for the specified block size are in use and no free buffers are available. Action: Increase the number of buffers in the specified pool for the specified block size. |
| ORA-00380 cannot specify db_numberk_cache_size since numberK is the standard block size | Cause: User 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. Action: Specify 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. |
| ORA-00381 cannot use both new and old parameters for buffer cache size specification | Cause: User 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}) AND one or more of {DB_BLOCK_BUFFERS/ BUFFER_POOL_KEEP/ BUFFER_POOL_RECYCLE}. This is illegal. Action: Use EITHER the old (pre-Oracle 9.0.0) 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. |
| ORA-00382 string not a valid block size valid range [string..string] | Cause: User 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. Action: Remove corresponding parameter from the initialization parameter file and restart the instance. |
| ORA-00383 DEFAULT cache for blocksize string cannot be reduced to zero | Cause: User attempted to reduce DB_CACHE_SIZE to zero or attempted to reduce DB_nK_CACHE_SIZE to zero while there were still online tablespaces with block size nK. Note that since the SYSTEM tablespace cannot be taken offline it is always illegal to set DB_CACHE_SIZE to zero. Action: Offline any tablespaces with the corresponding block size and then perform the operation again. |
| ORA-00384 Insufficient memory to grow cache | Cause: The system could not allocate sufficient memory to grow the cache to the specified size. Action: Attempt a smaller increase in the value of the parameter. |
| ORA-00390 log string of thread string is being cleared cannot become current log | Cause: An 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 usable when the clearing completes. The command that began the clearing may have terminated without completing the clearing. Action: If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command or drop the log. |
| ORA-00391 All threads must switch to new log format at the same time | Cause: An attempt to switch the current log of a single thread is not allowed because the compatibility requirements force a new log format version number. When changing log formats all threads must switch to the new format at the same time. Action: Open 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. |
| ORA-00392 log string of thread string is being cleared operation not allowed | Cause: An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing. Action: If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command or drop the log. |
| ORA-00393 log string of thread string is needed for recovery of offline datafiles | Cause: Log 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. Action: Archive the log and then repeat the clear command. If archiving is not possible and dropping the tablespaces is acceptable then add the clause UNRECOVERABLE DATAFILE at the end of the clear command. |
| ORA-00394 online log reused while attempting to archive it | Cause: An attempt was made to reuse an online log file that is being archived. Action: The online log file has been overwritten; it cannot be archived. |
| ORA-00395 online logs for the clone database must be renamed | Cause: A clone database open forces log file renaming to avoid overwriting the primary log files. Action: Rename the log files manually or using the LOG_FILE_NAME_CONVERT initialization parameter. |
| ORA-00396 error string required fallback to single-pass recovery | Cause: The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error. Action: Correct the cause of the indicated error (also recorded) so that future instance or crash recovery can succeed with the new algorithm. This usually requires making more main storage available to the recovery process. |
| ORA-00397 lost write detected for file string block string | Cause: The specified block is missing changes that should have been written to disk indicating a lost write by the file I/O subsystem or volume manager. Action: Run diagnostic checks on the I/O subsystem and resolve any errors |
| ORA-00398 abort thread recovery due to reconfiguration | Cause: Global enqueue service reconfiguration occurred during instance/crash recovery. Action: This is used internally no action is required. |
| ORA-00399 corrupt change description in redo log | Cause: A change vector in the redo log failed validation checks. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. |
| ORA-00400 invalid release value string for parameter string | Cause: The release level given for the specified initialization parameter is invalid. Action: Correct the parameter value in the parameter file and retry. |
