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. 解决： Check that the correct control files were specified.
ORA-00204: error in reading (block string, # blocks string) of control file 原因： A disk I/O failure was detected on reading the control file.
解决： 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.
ORA-00205: error in identifying control file, check alert log for more info 原因： The system could not find a control file of the specified name and size.
解决： Check that ALL control files are online and that they are the same files that the system created at cold start time.
ORA-00206: error in writing (block string, # blocks string) of control file 原因： A disk I/O failure was detected on writing the control file.
解决： 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.
ORA-00207: control files are not for the same database
原因： 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.
解决： Check that the control file is for the correct database and is not an old version. ORA-00208: number of control file names exceeds limit of string
原因： An attempt was made to use more control files than Oracle supports.
解决： 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. ORA-00209: control file blocksize mismatch, check alert log for more info
原因： The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.
解决： Look at the alert log for more information. ORA-00210: cannot open the specified control file 原因： Cannot open the control file.
解决： Check to make sure the control file exists and is not locked by some other program. ORA-00211: control file does not match previous control files
原因： A control file was specified that belongs to another database. 解决： Find and install the correct control file.
ORA-00212: block size string below minimum required size of string bytes
原因： The block size specified was too small. Space for the system overhead is required. 解决： Specify a larger block size and retry the operation.
ORA-00213: cannot reuse control file; old file size string, string required
原因： To reuse a control file, it must be the same size as the one previously used.
解决： 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: control file \ 原因： An inconsistent set of control files, datafiles/logfiles, and redo files was used.
第11页
解决： 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. ORA-00215: must be at least one control file
原因： No control file is specified or the control file specified does not exist. 解决： Specify at least one valid control file and retry the operation. ORA-00216: control file could not be resized for migration from 8.0.2
原因： 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.
解决： 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-00217: control file could not be resized for new record types
原因： 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.
解决： 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-00218: block size string of control file \ 原因： 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.
解决： 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)
原因： 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.
解决： In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses.
ORA-00220: control file not mounted by first instance, check alert log for more info
原因： 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.
解决： Find and install the correct control file. ORA-00221: error on write to control file
原因： An error occurred when writing to one or more of the control files. 解决： See accompanying messages.
ORA-00222: operation would reuse name of a currently mounted control file
原因： The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified
第12页
currently mounted control file.
解决： Retry the operation with a different filename. ORA-00223: convert file is invalid or incorrect version
原因： 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.
解决： 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: control file resize attempted with illegal record type (string)
原因： An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter.
解决： Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1-16).
ORA-00225: expected size string of control file differs from actual size string
原因： 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. 解决： Restore a good copy of the control file.
ORA-00226: operation disallowed while alternate control file open
原因： The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access.
解决： Retry the operation after calling cfileUseCurrent.
ORA-00227: corrupt block detected in control file: (block string, # blocks string)
原因： A block header corruption or checksum error was detected on reading the control file. 解决： Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.
ORA-00228: length of alternate control file name exceeds maximum of string
原因： The specified filename, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system. 解决： Retry the operation with a shorter filename.
ORA-00229: operation disallowed: already hold snapshot control file enqueue
原因： The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue.
解决： Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue.
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
原因： The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.
解决： Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.
ORA-00231: snapshot control file has not been named
原因： During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified.
解决： Specify a name for the snapshot control file by calling cfileSetSnapshotName.
第13页
ORA-00232: snapshot control file is nonexistent, corrupt, or unreadable
原因： The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot.
解决： Call cfileMakeAndUseSnapshot again (or for the first time). ORA-00233: copy control file is corrupt or unreadable 原因： The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.
解决： Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy. ORA-00234: error in identifying or opening snapshot or copy control file
原因： A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.
解决： Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.
ORA-00235: control file fixed table inconsistent due to concurrent update
原因： Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information. 解决： Retry the operation.
ORA-00236: snapshot operation disallowed: mounted control file is a backup
原因： Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file. 解决： Mount a current control file and retry the operation.
ORA-00237: snapshot operation disallowed: control file newly created 原因： An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made. 解决： Mount a current control file and retry the operation.
ORA-00238: operation would reuse a filename that is part of the database
原因： 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.
解决： Retry the operation with a different filename. ORA-00250: archiver not started
原因： An attempt was made to stop automatic archiving, but the archiver process was not running.
解决： No action required.
ORA-00251: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string 原因： 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.
解决： 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
原因： 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.
第14页
解决： 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
原因： The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long.
解决： Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message.
ORA-00254: error in archive control string \
原因： The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter.
解决： 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 原因： An error occurred during archiving.
解决： 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
原因： The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.
解决： 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.
原因： 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.
解决： 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-00258: manual archiving in NOARCHIVELOG mode must identify log 原因： 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.
解决： Specify log by filename, by group number or by thread and sequence number.
ORA-00259: log string of open instance string (thread string) is the current log, cannot archive 原因： 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.
解决： 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
原因： 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.
解决： Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.
第15页