ORA-00281: media recovery may not be performed using dispatcher

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-00280: change string for thread string is in sequence #string

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-00279: change string generated at string needed for thread string

ORA-00279: change string generated at string needed for thread string

Cause: The requested log is required to proceed with recovery.

Action: Please supply the requested log with ALTER DATABASE RECOVER LOGFILE lamp;lt;lamp;nbsp;file_namelamp;gt; or cancel recovery with ALTER DATABASE RECOVER CANCEL .

ORA-00278: log file string no longer needed for this recovery

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 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-00277: illegal option to the UNTIL recovery flag string

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-00276: CHANGE keyword specified but no change number given

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-00275: media recovery has already been started

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-00274: illegal recovery option string

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-00273: media recovery of direct load data that was not logged

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-00272: error writing archive log string

ORA-00272: error writing archive log string

Cause: An I or 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-00271: there are no logs that need archiving

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 required.

ORA-00270: error creating archive log string

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-00269: specified log file is part of thread string not string

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-00268: specified log file does not exist string

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 filename and retry the command.

ORA-00267: name of archived log file not needed

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-00266: name of archived log file needed

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-00265: instance recovery required, cannot set ARCHIVELOG mode

ORA-00265: instance recovery required, cannot set ARCHIVELOG mode

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.

ORA-00264: no recovery required

ORA-00264: no recovery required

Cause: An attempt was made to perform media recovery on files that do not or or 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.

ORA-00263: there are no logs that need archiving for thread string

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-00262: current log string of closed thread string cannot switch

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-00261: log string of thread string is being archived or modified

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-00260: cannot find online log sequence string for thread string

ORA-00260: cannot find online log sequence string for thread string

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.

ORA-00259: log string of open instance string (thread string) is the current log, cannot archive

ORA-00259: log string of open instance string (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-00258: manual archiving in NOARCHIVELOG mode must identify log

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 filename.

Action: Specify log by filename, by group number or by thread and sequence number.

ORA-00257: archiver error. Connect internal only, until freed.

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 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-00256: cannot translate archive destination string string

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-00255: error archiving log string of thread string, sequence # string

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-00254: error in archive control string string

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-00253: character limit string exceeded by archive destination string string

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-00252: log string of thread string is empty, cannot archive

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 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.

ORA-00251: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string

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-00250: archiver not started

ORA-00250: archiver not started

Cause: An attempt was made to stop automatic archiving, but the archiver process was not running.

Action: No action required.

ORA-00238: operation would reuse a filename that is part of the database

ORA-00238: operation would reuse a filename that is part of the database

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.

ORA-00237: snapshot operation disallowed: control file newly created

ORA-00237: snapshot operation disallowed: control file 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-00236: snapshot operation disallowed: mounted control file is a backup

ORA-00236: snapshot operation disallowed: mounted control file 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-00235: control file fixed table inconsistent due to concurrent update

ORA-00235: control file 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-00234: error in identifying or opening snapshot or copy control file

ORA-00234: error in identifying or opening snapshot or copy control file

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-00233: copy control file is corrupt or unreadable

ORA-00233: copy control file 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 filename that was specified for cfileUseCopy.

ORA-00232: snapshot control file is nonexistent, corrupt, or unreadable

ORA-00232: snapshot control file is nonexistent, corrupt, or unreadable

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).

ORA-00231: snapshot control file has not been named

ORA-00231: snapshot control file has not been named

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.

ORA-00230: operation disallowed: snapshot control file enqueue unavailable

ORA-00230: operation disallowed: snapshot control file 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-00229: operation disallowed: already hold snapshot control file enqueue

ORA-00229: operation disallowed: already hold snapshot control file 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-00228: length of alternate control file name exceeds maximum of string

ORA-00228: length of alternate control file name exceeds maximum of string

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.

ORA-00227: corrupt block detected in control file: (block string, # blocks string)

ORA-00227: corrupt block detected in control file: (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-00226: operation disallowed while alternate control file open

ORA-00226: operation disallowed while alternate control file 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-00225: expected size string of control file differs from actual size string

ORA-00225: expected size string of control file 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-00224: control file resize attempted with illegal record type (string)

ORA-00224: control file 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-16).

ORA-00223: convert file is invalid or incorrect version

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 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-00222: operation would reuse name of a currently mounted control file

ORA-00222: operation would reuse name of a currently mounted control file

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.

ORA-00221: error on write to control file

ORA-00221: error on write to control file

Cause: An error occurred when writing to one or more of the control files.

Action: See accompanying messages.

ORA-00220: control file not mounted by first instance, check alert log for more info

ORA-00220: control file 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-00219: required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)

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.

ORA-00218: block size string of control file string does not match DB_BLOCK_ SIZE (string)

ORA-00218: block size string of control file string 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. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value.

ORA-00217: control file could not be resized for new record types

ORA-00217: control file could not be resized for new record types

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.

ORA-00216: control file could not be resized for migration from 8.0.2

ORA-00216: control file could not be resized for migration from 8.0.2

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.

ORA-00215: must be at least one control file

ORA-00215: must be at least one control file

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-00214: control file string version string inconsistent with file string version string

ORA-00214: control file string version string inconsistent with file string version string

Cause: An inconsistent set of control files, datafiles or logfiles, and redo files was used.

Action: Use a consistant set of control files, datafiles or logfiles, and redo log files. That is, all the files must be for the same database and from the same time period.

ORA-00213: cannot reuse control file; old file size string, string required

ORA-00213: cannot reuse control file; 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-00212: block size string below minimum required size of string bytes

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-00211: control file does not match previous control files

ORA-00211: control file does not match previous control files

Cause: A control file was specified that belongs to another database.

Action: Find and install the correct control file.