Oracle 12c R2 Error Codes and Solution Suggestions from ORA-00300 to ORA-00400
- ORA-00300: illegal redo log block size string specified – exceeds limit of string
Cause: The specified block size of the redo log is greater than the maximum block size for the operating system.
Action: Create the redo log on a device with a smaller block size
Cause: The creation of the redo log file failed
Action: Check: 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.
Cause: The maximum number of redo log files has been exceeded.
Action: Use 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.
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. to process this log.
Cause: An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.
Action: Either 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.
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, then retry the operation.
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 a) port-specific limit as to the number of instances b) the number of instances specified at create-database time
Cause: The initialization parameter INSTANCE_NUMBER specified a number that was out of range.
Action: Change 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.
Cause: The system cannot access a required archived redo log file.
Action: Check 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.
Cause: The system cannot access the archived redo log because it belongs to another database.
Action: Specify the correct redo log file, then retry the operation.
Cause: The archived log was out of sequence, probably because it was corrupt or the wrong redo log file name was specified during recovery.
Action: Specify the correct redo log file; then retry the operation.
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.
Cause: This message reports the filename for details of another message.
Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.
Cause: The online log cannot be opened. May not be able to find file.
Action: See accompanying errors and make log available.
Cause: The online log is corrupted or is an old version.
Action: Find and install correct version of log or reset logs.
Cause: The online log is corrupted or is an old version.
Action: Find and install correct version of log or reset logs.
Cause: The online log is corrupted or is an old version.
Action: Find and install correct version of log or reset logs.
Cause: This is not an archived log file.
Action: Find the correct file and try again.
Cause: On header read the file size indicated in the control file did not match the file size contained in the log file.
Action: Restore correct file or reset logs.
Cause: Check 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.
Action: Restore correct file or reset logs.
Cause: The file is not available.
Action: Restore the log file.
Cause: Cannot write to the log file.
Action: Restore the access to the file.
Cause: Check of log file header at database open found that an online log appears to be an incorrectly restored backup.
Action: Restore correct file or reset logs.
Cause: Attempt 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.
Action: Archive the logs for the thread then retry 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 a untranslated name that yields a shorter translated name.
Cause: The archived log is corrupted or for another thread. Can not use the log for applying redo.
Action: Find correct archived log.
Cause: The archived log supplied for recovery was generated after the log that is needed. Can not yet use the log for applying redo.
Action: Find correct archived log.
Cause: A log file has shrunk in size. This is likely to have been caused by operator or operating system error.
Action: Restore 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.
Cause: The archived log supplied for recovery was generated before the log that is needed. Can not use the log for applying redo.
Action: Find correct archived log.
Cause: The archived log is not the correct log. An earlier log is needed.
Action: Restore the correct log file.
Cause: The archived log is not the correct log. A later log is needed.
Action: Restore the correct log file.
Cause: The log was written by incompatible version of Oracle.
Action: Recover the database with the compatible software, shut it down cleanly, then restart with current software.
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.
Cause: An IO error occurred while reading the log described in the accompanying error.
Action: Restore accessibility to file, or get another copy of the file.
Cause: Reporting filename for details of another error
Action: See associated error messages
Cause: Reporting filename for details of another error
Action: See associated error messages
Cause: The log file size as specified in create database is too small.
Action: Increase the log file size.
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.
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.
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.
Cause: An IO error occurred on the named online log.
Action: Restore accessibility to file, or restore file from backup.
Cause: The internal information in an online log file does not match the control file.
Action: Restore correct file or reset logs.
Cause: Recovery 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.
Action: Supply the correct log file.
Cause: An 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.
Action: Correct the file/device as indicated by accompanying errors.
Cause: An IO error has 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.
Cause: A log file member was no longer complete.
Action: Correct the underlying problem by referring to the other error messages found with this one.
Cause: On header read the blocksize indicated in the control file did not match the blocksize contained in the log file.
Action: Restore correct file or reset logs.
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 warmstart the database.
Cause: The operating system was unable to determine the blocksize for the given filename.
Action: Consult the accompanying error message, and correct the device or specify another filename.
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 unuseable, and forcing the drop of some offline files.
Cause: The time specified in a recover-until statement must be after January 1st 1988.
Action: Specify a time after January 1st 1988.
Cause: Attempting 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.
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: Do recovery with a good version of the log or do incomplete recovery up to the indicated change or time.
Cause: The block header on the redo block indicated by the accompanying error, is not reasonable.
Action: Do 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.
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: Do recovery with a good version of the log or do time based recovery up to the indicated time.
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: Do recovery with a good version of the log or do time based recovery up to the indicated time.
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.
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.
Cause: An add logfile member or drop logfile request specified a logfile group number that does not exist.
Action: Check the configuration of the log files and reissue the command.
Cause: A filename was given to drop logfile member that is not a part of the database, or which is a data file.
Action: Supply a valid logfile member name.
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.
Cause: A request to drop a logfile member was denied because it would remove data required to form a complete logfile.
Action: If desired, delete the entire log (after archiving if required), by using DROP LOGFILE;
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.
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 problem or use another file.
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 filename to recovery.
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 log or reset logs.
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.
Cause: The redo block indicated by the accompanying error, is not vaild. It has a checksum that does not match the block contents.
Action: Do 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.
Cause: Attempt 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.
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.
Cause: Error code used internally by software. Should never be reported
Action: Treat as internal error. See error 600.
Cause: The SHARED_POOL_SIZE initialization parameter was too small.
Action: Increase the parameter value.
Cause: attempting 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
Cause: The 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.
Action: Recover the database with the compatible software, shut it down cleanly, 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: invalid value for db_block_size parameter
Action: adjust parameter and restart
Cause: attempting 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
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, 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.
Cause: Either 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.
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
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.
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), db_cache_advice } AND one or more of { db_block_buffers, buffer_pool_keep , buffer_pool_recycle }. This is illegal.
Action: Use 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.
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 “init.ora” file and restart the instance.
Cause: User attempted to reduce db_cache_size to zero, or attempted to to reduce db_nK_cache_size to zero while there were still online tablespaces with blocksize 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 blocksize and then perform the operation again.
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.
Cause: The 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.
Action: Restart the instance.
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 useable 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.
Cause: An 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.
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.
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.
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 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.
Cause: It has been detected that an online log that is being archived has been reused
Action: Cannot archive the logfile anymore since it has been overwritten
Cause: A clone database open forces logfile renaming to avoid overwriting the primary logfiles
Action: Rename the logfiles manually or using the log_file_name_convert initialization parameter
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 two-pass algorithm. This usually requires making more main memory available to the recovery process.
Cause: The foreground process doing instance recovery died.
Action: Check the foreground trace file for the cause of recovery failure.
Cause: Global enqueue service reconfiguration occurred during instance/crash recovery.
Action: This is used internally, no action is required.
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.
Cause: The release level given for the specified init parameter is invalid.
Action: Correct the parameter value in the parameter file and retry.