Below are the list of Oracle ORA message from ORA-00201 to ORA-00300. You can find the cause and actions from each of the message accordingly.
| ORA MESSAGE | CAUSE / ACTION |
|---|---|
| ORA-00201 controlfile version string incompatible with ORACLE version string | Cause: The control file was created by incompatible software. Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release. |
| ORA-00202 controlfile: 'string' | Cause: This message reports the name file involved in other messages. Action: See associated error messages for a description of the problem. |
| ORA-00203 using the wrong controlfiles | Cause: The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file. Action: Check that the correct control files were specified. |
| ORA-00204 error in reading (block string / # blocks string) of controlfile | Cause: A disk I/O failure was detected on reading the control file. Action: Check that the disk is online. If it is not bring it online and shut down and restart Oracle. If it is online then look for operating system reasons for Oracle's inability to read the disk or control file. See the Oracle9i Database Administrator's Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation. |
| ORA-00205 error in identifying controlfile check alert log for more info | Cause: The system could not find a control file of the specified name and size. Action: One of the following: - Check that the proper control file name is referenced in the CONTROL_FILES initialization parameter in the initialization parameter file and try again. - When using mirrored control files that is more than one control file is referenced in the initialization parameter file remove the control file name listed in the message from the initialization parameter file and restart the instance. If the message does not recur remove the problem control file from the initialization parameter file and create another copy of the control file with a new file name in the initialization parameter file. |
| ORA-00206 error in writing (block string / # blocks string) of controlfile | Cause: A disk I/O failure was detected on writing to the control file. Action: Check that the disk is online. If it is not bring it online and shut down and restart Oracle. If it is online then look for operating system reasons for Oracle's inability to write to the disk or control file. See the Oracle9i Database Administrator's Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation. |
| ORA-00207 controlfiles are not for the same database | Cause: The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name. Action: Check that the control file is for the correct database and is not an old version. When using multiplexed control files that is more than one control file is referenced in the initialization parameter file remove the control file name listed in the message from the initialization parameter file and restart the instance. If the message does not recur remove the problem control file from the initialization parameter file and create another copy of the control file using a new file name in the initialization parameter file. |
| ORA-00208 number of controlfile names exceeds limit of string | Cause: An attempt was made to use more control files than Oracle supports. Action: Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file and restart Oracle. Delete unused files. |
| ORA-00209 control file blocksize mismatch check alert log for more info | Cause: The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter. Action: Reduce the block size to the amount specified in the message and try again. |
| ORA-00210 cannot open the specified controlfile | Cause: Cannot open the control file. Action: Check to make sure the control file exists and is not locked by some other program. |
| ORA-00211 controlfile does not match previous controlfiles | Cause: A control file was specified that belongs to another database. Action: Find and install the correct control file. |
| ORA-00212 block size string below minimum required size of string bytes | Cause: The block size specified was too small. Space for the system overhead is required. Action: Specify a larger block size and retry the operation. |
| ORA-00213 cannot reuse controlfile; old file size string string required | Cause: To reuse a control file it must be the same size as the one previously used. Action: Either do not specify REUSE or specify a matching combination of MAXDATAFILES / MAXLOGFILES / MAXLOGMEMBERS / MAXLOGHISTORY and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement. |
| ORA-00214 controlfile 'string' version string inconsistent with file 'string' version string | Cause: An inconsistent set of control files / datafiles and redo log files was used. Action: Use a consistent set of control files / datafiles and redo log files. That is all the files must be for the same database and from the same time period. |
| ORA-00215 must be at least one controlfile | Cause: No control file is specified or the control file specified does not exist. Action: Specify at least one valid control file and retry the operation. |
| ORA-00216 controlfile could not be resized for migration from 8.0.2 | Cause: Control files created by release 8.0.2 were missing some records. These records are automatically added by resizing the control file when attempting to run a later release. The resize failed. Action: Look in the alert log for the reason that the resize failed. If it can be fixed by giving the control file more space then do that. Otherwise use the CREATE CONTROLFILE script dumped to the trace file to create a new control file. |
| ORA-00217 controlfile could not be resized for migration from 9.0.1 | Cause: Controlfiles created by release 9.0.1 were missing some records. These records are automatically added by resizing the controlfile when attempting to run a later release. The resize failed. Action: Look in the alert log for the reason the resize failed. If it can be fixed by giving the controlfile more space then do that. Otherwise use the CREATE CONTROLFILE script dumpped to the trace file to create a new controlfile. |
| ORA-00218 block size string of controlfile does not match DB_BLOCK_SIZE (string) | Cause: The block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE or else might indicate that the control file has either been corrupted or belongs to a different database. Action: Restore a good copy of the control file. |
| ORA-00219 required controlfile size string exceeds maximum allowable size string | Cause: An invocation of CREATE DATABASE / CREATE CONTROLFILE / cfileCalcSizeList or cfileCalcSizeArray was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value. Action: In the case of CREATE DATABASE or CREATE CONTROLFILE use a different combination of MAXDATAFILES / MAXLOGFILES / MAXLOGMEMBERS / MAXLOGHISTORY and MAXINSTANCES clauses. In the case of cfileCalcSizeList() or cfileCalcSizeArray() use a different combination of record type counts. |
| ORA-00220 controlfile not mounted by first instance check alert log for more info | Cause: The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file. Action: Find and install the correct control file. |
| ORA-00221 error on write to controlfile | Cause: An error occurred when writing to one or more of the control files. Action: See accompanying messages. |
| ORA-00222 operation would reuse name of a currently mounted controlfile | Cause: The file name supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted control file. Action: Retry the operation with a different file name. |
| ORA-00223 convert file is invalid or incorrect version | Cause: An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when the ALTER DATABASE CONVERT command is issued. Action: Use a correct version of the convert file or regenerate it with the migration utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set. |
| ORA-00224 controlfile resize attempted with illegal record type (string) | Cause: An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter. Action: Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1 to 16). |
| ORA-00225 expected size string of controlfile differs from actual size string | Cause: The expected size of the control file as stored in its header was different than the actual operating system file size. This usually indicates that the control file was corrupted. Action: Restore a good copy of the control file. |
| ORA-00226 operation disallowed while alternate controlfile open | Cause: The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access. Action: Retry the operation after calling cfileUseCurrent. |
| ORA-00227 corrupt block detected in controlfile: (block string / # blocks string) | Cause: A block header corruption or checksum error was detected on reading the control file. Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command. |
| ORA-00228 length of alternate controlfile name exceeds maximum of string | Cause: The specified file name which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy exceeds the maximum file name length for this operating system. Action: Retry the operation with a shorter file name. |
| ORA-00229 operation disallowed: already hold snapshot controlfile enqueue | Cause: The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue. Action: Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue. |
| ORA-00230 operation disallowed: snapshot controlfile enqueue unavailable | Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue. Action: Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates. |
| ORA-00231 snapshot controlfile has not been named | Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no file name for the snapshot control file had previously been specified. Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName. |
| ORA-00232 snapshot controlfile is nonexistent / corrupt or unreadable | Cause: The snapshot control file was found to be non-existent / corrupt or unreadable during an invocation of cfileUseSnapshot. Action: Call cfileMakeAndUseSnapshot again (or for the first time). |
| ORA-00233 copy controlfile is corrupt or unreadable | Cause: The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy. Action: Before retrying cfileUseCopy use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same file name that was specified for cfileUseCopy. |
| ORA-00234 error in identifying or opening snapshot or copy controlfile | Cause: A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot / cfileMakeAndUseSnapshot or cfileUseCopy. Action: Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE respectively. |
| ORA-00235 controlfile fixed table inconsistent due to concurrent update | Cause: Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information. Action: Retry the operation. |
| ORA-00236 snapshot operation disallowed: mounted controlfile is a backup | Cause: Attempting to invoke cfileSetSnapshotName / cfileMakeAndUseSnapshot or cfileUseSnapshot when the currently mounted control file is a backup control file. Action: Mount a current control file and retry the operation. |
| ORA-00237 snapshot operation disallowed: controlfile newly created | Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made. Action: Mount a current control file and retry the operation. |
| ORA-00238 operation would reuse a filename that is part of the database | Cause: The file name supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database. Action: Retry the operation with a different file name. |
| ORA-00250 archiver not started | Cause: An attempt was made to stop automatic archiving but the archiver process was not running. Action: No action is required. |
| ORA-00251 LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string | Cause: The destination specified by the LOG_ARCHIVE_DUPLEX_DEST parameter is the same as the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command. Action: Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST or specify a different destination with the ALTER SYSTEM command. |
| ORA-00252 log string of thread string is empty cannot archive | Cause: A log must be used for redo generation before it can be archived. The specified redo log was not been used since it was introduced to the database. However it is possible that the instance died during a log switch and the log was empty. Action: Empty logs do not need to be archived. Do not attempt to archive the redo log file. |
| ORA-00253 character limit string exceeded by archive destination string string | Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long. Action: Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message. |
| ORA-00254 error in archive control string 'string' | Cause: The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter. Action: Check the archive string used to make sure it refers to a valid online device. |
| ORA-00255 error archiving log string of thread string sequence # string | Cause: An error occurred during archiving. Action: Check the accompanying message stack for more detailed information. If the online log is corrupted then the log can be cleared using the UNARCHIVED option. This will make any existing backups useless for recovery to any time after the log was created but will allow the database to generate redo. |
| ORA-00256 cannot translate archive destination string string | Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated. Action: Check the accompanying message stack for more detailed information. Then retry the ALTER SYSTEM command using a different string. |
| ORA-00257 archiver error. Connect internal only until freed. | Cause: The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file. Action: Check the archiver trace file for a detailed description of the problem. Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving. |
| ORA-00258 manual archiving in NOARCHIVELOG mode must identify log | Cause: The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number group number or file name. Action: Specify the log by file name by group number or by thread and sequence number. |
| ORA-00259 log string of open thread string is the current log cannot archive | Cause: An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries. Action: Force a log switch in the instance where the thread is open. If no instances are open – open the database so that instance recovery can recover the thread. |
| ORA-00260 cannot find online log sequence string for thread string | Cause: The log sequence number supplied in the ARCHIVE statement does not match any of the online logs for the thread. This can result from any of the following situations: - The log might have been reused for another sequence number. - The log might have been dropped. - The sequence number might be greater than the current log sequence number. - The thread might not have any logs. Action: Check the ARCHIVE statement then specify a valid log sequence number. Specify a valid log sequence number. |
| ORA-00261 log string of thread string is being archived or modified | Cause: The log is either being archived by another process or an administrative command is modifying the log. Operations that modify the log include clearing / adding a member / dropping a member / renaming a member and dropping the log. Action: Wait for the current operation to complete and try again. |
| ORA-00262 current log string of closed thread string cannot switch | Cause: The log cannot be cleared or manually archived because it is the current log of a closed thread and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived or cleared and cannot be reused. Action: Archive another log in the same thread first or complete the clearing. See attached errors for the reason the switch cannot be completed. |
| ORA-00263 there are no logs that need archiving for thread string | Cause: An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving. Action: No action required. |
| ORA-00264 no recovery required | Cause: An attempt was made to perform media recovery on files that do not need any type of recovery. Action: Do not attempt to perform media recovery on the selected files. Check to see that the file names were entered properly. If not retry the command with the proper file names. |
| ORA-00265 instance recovery required cannot set ARCHIVELOG mode | Cause: The database either crashed or was shut down with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles. Action: Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option. |
| ORA-00266 name of archived log file needed | Cause: During media recovery the name of an archived redo log file was requested but no name was entered. Action: Mount the correct redo log file and enter its name when it is requested. |
| ORA-00267 name of archived log file not needed | Cause: During media recovery the name of an archived redo log file was entered but no name was requested. Action: Continue media recovery but do not enter a new log name. |
| ORA-00268 specified log file does not exist 'string' | Cause: The given redo log file does not exist. Action: Check the spelling and capitalization of the file name and retry the command. |
| ORA-00269 specified log file is part of thread string not string | Cause: The given redo log file is not part of the given thread. Action: Check that the thread of the redo log file matches the thread on the command line. If not use a redo log file from the appropriate thread. Retry the command after correcting the error. |
| ORA-00270 error creating archive log string | Cause: An error was encountered when either creating or opening the destination file for archiving. Action: Check that the archive destination is valid and that there is sufficient space on the destination device. |
| ORA-00271 there are no logs that need archiving | Cause: An attempt was made to archive the unarchived redo log files manually but there are no files that need to be archived. Action: No action is required. |
| ORA-00272 error writing archive log string | Cause: An I/O error occurred while archiving a redo log file. Action: Check that the output device is still available and correct any device errors that may have occurred. Also make certain that sufficient space for archiving is available on the output device. |
| ORA-00273 media recovery of direct load data that was not logged | Cause: A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt. Action: The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available try to recover this file to eliminate this error. |
| ORA-00274 illegal recovery option string | Cause: An illegal option was specified for a recovery command. Action: Correct the syntax and retry the command. |
| ORA-00275 media recovery has already been started | Cause: An attempt was made to start a second media recovery operation in the same session. Action: Complete or cancel the first media recovery session or start another session to perform media recovery. |
| ORA-00276 CHANGE keyword specified but no change number given | Cause: The CHANGE keyword was specified on the command line but no change number was given. Action: Retry the command using a valid change number after the CHANGE keyword. |
| ORA-00277 illegal option to the UNTIL recovery flag string | Cause: Only CANCEL / CHANGE and TIME can be used with the UNTIL keyword. Action: Correct the syntax. |
| ORA-00278 log file 'string' no longer needed for this recovery | Cause: The specified redo log file is no longer needed for the current recovery. Action: No action is required. The archived redo log file may be removed from its current location to conserve disk space if needed. However the redo log file may still be required for another recovery session in the future. |
| ORA-00279 change string generated at string needed for thread string | Cause: The requested log is required to proceed with recovery. Action: Supply the requested log with ALTER DATABASE RECOVER LOGFILE filename or cancel recovery with ALTER DATABASE RECOVER CANCEL. |
| ORA-00280 change string for thread string is in sequence #string | Cause: This message helps to locate the redo log file with the specified change number requested by other messages. Action: Use the information provided in this message to specify the required archived redo log files for other errors. |
| ORA-00281 media recovery may not be performed using dispatcher | Cause: An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method. Action: Connect to the instance via a dedicated server process to perform media recovery. |
| ORA-00282 UPI string call not supported use ALTER DATABASE RECOVER | Cause: The given UPI call is no longer supported. Action: Use the ALTER DATABASE RECOVER command for all recovery actions. |
| ORA-00283 recovery session canceled due to errors | Cause: An error during recovery was determined to be fatal enough to end the current recovery session. Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action. |
| ORA-00284 recovery session still in progress | Cause: An error during recovery was determined to be minor enough to allow the current recovery session to continue. Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action. |
| ORA-00285 TIME not given as a string constant | Cause: UNTIL TIME was not followed by a string constant for the time. Action: Enter the time enclosed in single quotation marks. |
| ORA-00286 no members available or no member contains valid data | Cause: None of the members of a redo log file group are available or the available members do not contain complete data. Action: If a member is temporarily offline attempt to make it available. Make sure that the correct file names are being used especially if the redo log file is being accessed from a remote location. |
| ORA-00287 specified change number string not found in thread string | Cause: The given change number does not appear in any of the online redo logs for the given thread. Action: Check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs. |
| ORA-00288 to continue recovery type ALTER DATABASE RECOVER CONTINUE | Cause: During media recovery a new log is not required but the continuation command is necessary to do a checkpoint and report errors. Action: Type ALTER DATABASE RECOVER CONTINUE and recovery will resume. |
| ORA-00289 suggestion : string | Cause: This message reports the next redo log file name that is needed according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived. Action: Consider using this file name for the next log needed for recovery. |
| ORA-00290 operating system archival error occurred. See error below | Cause: While attempting to archive to a redo log file the server encountered an unexpected operating system error. Action: Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation. |
| ORA-00291 numeric value required for PARALLEL option | Cause: A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism. Action: Re-enter the command with a numeric argument specifying the degree of parallelism desired. |
| ORA-00292 parallel recovery feature not installed | Cause: A parallel recovery was requested when the parallel recovery option is not installed. Action: Delete the PARALLEL clause from the RECOVER command. Also delete the RECOVERY_PARALLELISM parameter in the initialization file. |
| ORA-00293 controlfile out of sync with redo log | Cause: The redo log file and control file are out of sync because a non-current control file was specified when the instance was started. Action: Retry the RECOVER command using the current control file or retry the RECOVER command using the USING BACKUP CONTROLFILE clause. |
| ORA-00294 invalid archivelog format specifier 'string' | Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted for string are s / S / t and T. Action: Correct the initialization file and restart the instance. |
| ORA-00295 datafile/tempfile number string is invalid must be between 1 and string | Cause: An invalid file number was specified. Action: Specify a valid datafile or tempfile number and retry the operation. |
| ORA-00296 maximum number of files (string) exceeded for RECOVER DATAFILE LIST | Cause: The RECOVER DATAFILE LIST command specified more datafiles than are allowed by the DB_FILES initialization parameter. This error occurs when doing recovery with Recovery Manager and the instance has been started with a DB_FILES parameter specifying fewer datafiles than Recovery Manager needs to recover to satisfy the user's RECOVER command. Action: Restart the instance with a higher value for DB_FILES. |
| ORA-00297 must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START | Cause: The RECOVER DATAFILE START command was issued but no RECOVER DATAFILE LIST commands had been issued. This only happens when doing recovery with Recovery Manager and is an internal error in Recovery Manager because Recovery Manager should always issue RECOVER DATAFILE LIST before RECOVER DATAFILE START. Action: Contact Oracle Support Services. |
| ORA-00298 Missing or invalid attribute value | Cause: A nonzero integer value is required when the following keyword attributes are specified: -TIMEOUT -EXPIRE -DELAY -NEXT Action: Correct the syntax and retry the command. |
| ORA-00299 must use file-level media recovery on data file string | Cause: The control file does not contain an entry for this file so block media recovery cannot be done. Action: Restore the data file and perform file-level media recovery. |
| 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. |
