Oracle 12c R2 Error Codes and Solution Suggestions from ORA-00200 to ORA-00300
- ORA-00200: control file could not be created
Cause: It was not possible to create the control file.
Action: Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.
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.
Cause: This message reports the name file involved in other messages.
Action: See associated error messages for a description of the problem.
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.
Cause: A disk I/O failure was detected on reading the control file.
Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.
Cause: The system could not find a control file of the specified name and size.
Action: Check that ALL control files are online and that they are the same files that the system created at cold start time.
Cause: A disk I/O failure was detected on writing the control file.
Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.
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.
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 usused files.
Cause: The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.
Action: Look at the alert log for more information.
Cause: Cannot open the control file.
Action: Check to make sure the control file exists and is not locked by some other program.
Cause: A control file was specified that belongs to another database.
Action: Find and install the correct control file.
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.
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.
Cause: An inconsistent set of control files, datafiles/logfiles, and redo files was used.
Action: Use a consistant set of control files, datafiles/logfiles, and redo log files. That is, all the files must be for the same database and from the same time period.
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.
Cause: The control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed.
Action: Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.
Cause: The control file was missing some new record types supported by this release. These record types are automatically added by resizing the contol file during mount. The resize has failed.
Action: Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.
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. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value.
- ORA-00219: required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
Cause: An invocation of CREATE DATABASE or CREATE CONTROLFILE 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.
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.
Cause: An error occurred when writing to one or more of the control files.
Action: See accompanying messages.
Cause: The filename 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 filename.
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 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.
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-16).
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.
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.
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.
Cause: The specified filename, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system.
Action: Retry the operation with a shorter filename.
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.
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.
Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified.
Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName.
Cause: The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot.
Action: Call cfileMakeAndUseSnapshot again (or for the first time).
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 filename that was specified for cfileUseCopy.
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.
Cause: Concurrent update activity on a control file caused a process to read inconsistent information from the control file without a lock.
Action: Retry the operation.
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.
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.
Cause: The filename 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 filename.
Cause: The specified process waited the maximum allowed time for the control file enqueue.
Action: Restart the blocking instance indicated in the incident trace file or reboot the blocking node.
Cause: The current process did not release the control file enqueue within the maximum allowed time.
Action: Reissue any commands that failed and contact Oracle Support Services with the incident information.
Cause: Either the control file was recently created by using CREATE CONTROLFILE, an incomplete recovery was done, or some previous operations require the control file to be re-checked against the data dictionary.
Action: Shut down and restart the database or the pluggable database so that the check is performed, and then retry the operation.
Cause: Failed to create a new filename record entry in the control file because the maximum allowed filename records have been allocated and are in use.
Action: Free up controlfile filename section entries by dropping unwanted tablespaces/datafiles/redofiles.
Cause: Failed to expand control file filename section. See alert log for more details.
Action: Retry the operation after increasing disk space for controlfile expansion.
Cause: Failed to create a control file backup because concurrent control file backup operation was in progress.
Action: Retry backup creation later.
Cause: Failed to create a control file backup because some process signaled an error during backup creation. This is likely caused by the backup target (i.e., RMAN snapshot controlfile) being on a local file system so it could not be accessed by other instances. It can also be caused by other I/O errors to the backup target. Any process of any instance that starts a read/write control file transaction must have access to the backup control file during backup creation.
Action: Check whether RMAN snapshot controlfile is on shared storage. Also, check alert files of all instances for further information.
Cause: An attempt to create a control file backup failed because some process signaled an I/O error when accessing the backup target.
Action: Check alert and trace files for further information.
Cause: An attempt was made to stop automatic archiving, but the archiver process was not running.
Action: No action required.
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.
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 instance death during a log switch left the log empty.
Action: Empty logs do not need to be archived. Do not attempt to archive the redo log file.
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.
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.
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.
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.
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 that the destination device is out of space to store the redo log file. Another possible cause is that a destination marked as MANDATORY has failed.
Action: Check the alert log and trace files for detailed error information.
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 filename.
Action: Specify log by filename, by group number or by thread and sequence number.
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.
Cause: The log sequence number supplied to the archival command does not match any of the online logs for the thread. The log might have been reused for another sequence number, it might have been dropped, the sequence number might be greater than the current log sequence number, or 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.
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.
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.
Cause: An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving.
Action: No action 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 filenames were entered properly. If not, retry the command with the proper filenames.
Cause: The database either crashed or was shutdown 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.
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.
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.
Cause: The given redo log file does not exist.
Action: Check the spelling and capitalization of the filename and retry the command.
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.
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.
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 required.
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.
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.
Cause: An illegal option was specified for a recovery command.
Action: Correct the syntax and retry the command.
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.
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.
Cause: Only CANCEL, CHANGE, CONSISTENT and TIME can be used with the UNTIL keyword.
Action: Correct the syntax.
Cause: The specified redo log file is no longer needed for the current recovery.
Action: No action 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.
Cause: The requested log is required to proceed with recovery.
Action: Please supply the requested log with “ALTER DATABASE RECOVER LOGFILE <file_name>” or cancel recovery with “ALTER DATABASE RECOVER CANCEL”.
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.
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.
Cause: The given UPI call is no longer supported.
Action: Use the ALTER DATABASE RECOVER command for all recovery actions.
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.
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.
Cause: TIME was not followed by a string constant for the time.
Action: Enter the time enclosed in single quotation marks.
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 filenames are being used, especially if the redo log file is being accessed from a remote location.
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.
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.
Cause: This message reports the next redo log filename 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 filename for the next log needed for recovery.
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.
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.
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.
Cause: The redo log file and control file are out of sync because a non-current controle 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.
Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted following the % symbol are s, S, t, and T.
Action: Correct the initialization file and re-start the instance.
Cause: An invalid file number was specified.
Action: Specify a valid datafile or tempfile number and retry the operation.
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: Re-start the instance with a higher value for DB_FILES.
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 customer support
Cause: A non-zero integer value is required when the following keyword attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT
Action: Correct the syntax and retry the command.
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.
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