BACKRUSH  유닉스명령  다음  자료실  Ascii Table   원격접속  달력,시간   프로세스  
지하철노선   RFC문서   SUN FAQ   SUN FAQ1   C메뉴얼   PHP메뉴얼   너구리   아스키월드 아이피서치

글쓴이: ora [ORA-00251~ORA00350]ERROR 조회수: 5549


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.


ORA-00301 error in adding log file 'string' - file cannot be created

Cause: The creation of the redo log file failed

Action: Check whether:

There is enough storage space on the device
The name of the file is valid
The device is online
An I/O error occurred
Also, it is possible REUSE was specified on the command line and a file of the incorrect size exists. Either do not specify REUSE or use a file of the correct size.


ORA-00302 limit of string logs exceeded

Cause: The maximum number of redo log files has been exceeded. There is a limit, set at database creation, on the number of redo log files (typically 16).

Action: Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES.


ORA-00303 cannot process Parallel Redo

Cause: A redo log containing Parallel Redo has been detected. The current Oracle release cannot process this format of redo.

Action: Use a later release that supports Parallel Redo.


ORA-00304 requested INSTANCE_NUMBER is busy

Cause: An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.

Action: Either:

Specify another INSTANCE_NUMBER,
Shut down the running instance with this number, or
Wait for instance recovery to complete on the instance with this number.

ORA-00305 log string of thread string inconsistent; belongs to another database

Cause: The database ID in the redo log file does not match the database ID in the control file. This redo log file is not from the current database.

Action: Specify the correct redo log file, and then retry the operation.


ORA-00306 limit of string instances in this database

Cause: Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances.

Action: You cannot start more than the lower of:

the operating system-specific maximum or
the number of instances specified by the MAXINSTANCES option specified in the CREATE DATABASE statement

ORA-00307 requested INSTANCE_NUMBER out of range, maximum is string

Cause: The initialization parameter INSTANCE_NUMBER specified a number that was out of range.

Action: Change the value of INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is 1 and the maximum value is the lower of the operating system-specific maximum or the value of the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation.


ORA-00308 cannot open archived log 'string'

Cause: The system cannot access a required archived redo log file.

Action: Check that the offline log exists, the storage device is online, and the archived file is in the correct location. Then attempt to continue recovery or restart the recovery session.


ORA-00309 log belongs to wrong database

Cause: The system cannot access the archived redo log because it belongs to another database.

Action: Specify the correct redo log file and then retry the operation.


ORA-00310 archived log contains sequence string; sequence string required

Cause: The archived log is out of sequence, probably because it is corrupted or the wrong redo log file name was specified during recovery.

Action: Specify the correct redo log file and then retry the operation.


ORA-00311 cannot read header from archived log

Cause: An I/O error occurred when attempting to read the log file header from the specified archived redo log file.

Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.


ORA-00312 online log string thread string: 'string'

Cause: This message reports the file name for details of another message.

Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.


ORA-00313 open failed for members of log group string of thread string

Cause: The online log cannot be opened. The file may not be in the expected location.

Action: Specify the correct redo log file or make the log available, if necessary. Also, see the accompanying messages.


ORA-00314 log string of thread string, expected sequence# string doesn't match string

Cause: The online log is corrupted or is an old version.

Action: Find and install the correct version of the log or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures.


ORA-00315 log string of thread string, wrong thread # string in header

Cause: The online log is corrupted or is an old version.

Action: Find and install the correct version of the log or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures.


ORA-00316 log string of thread string, type string in header is not log file

Cause: The online log is corrupted or is an old version.

Action: Find and install the correct version of the log or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures.


ORA-00317 file type string in header is not log file

Cause: This is not an archived log file.

Action: Find the correct file and try again. Refer to the Oracle9i Database Administrator's Guide for recovery procedures.


ORA-00318 log string of thread string, expected file size string doesn't match string

Cause: The file size indicated in the control file did not match the file size contained in the log file.

Action: Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures.


ORA-00319 log string of thread string has incorrect log reset status

Cause: An online redo log has log reset data that is different from the log reset data in the control file. The log is probably an incorrectly restored backup.

Action: Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures.


ORA-00320 cannot read file header from log string of thread string

Cause: The file is not available.

Action: Restore the log file.


ORA-00321 log string of thread string, cannot update log file header

Cause: Cannot write to the log file.

Action: Restore access to the file.


ORA-00322 log string of thread string is not current copy

Cause: An online log appears to be an incorrectly restored backup.

Action: Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures.


ORA-00323 Current log of thread string not useable and all others need archiving

Cause: An attempt to open the thread failed because it is necessary to switch redo generation to another online log, but all the other logs need to be archived before they can be used.

Action: Archive the logs for the thread and then retry the open.


ORA-00324 log file 'string' translated name 'string' too long, string characters exceeds string limit

Cause: The translated name for a log file is too long.

Action: Choose an untranslated name that yields a shorter translated name.


ORA-00325 archived log for thread string, wrong thread # string in header

Cause: The archived log is corrupted or for another thread. Cannot use the log for applying the redo.

Action: Find the correct archived log.


ORA-00326 log begins at change string, need earlier change string

Cause: The archived log supplied for recovery was generated after the log that is needed. Cannot yet use the log for applying redo.

Action: Find the correct archived log.


ORA-00327 log string of thread string, physical size string less than needed string

Cause: A log file has shrunk in size. This is likely to have been caused by a computer operator's mistake or an operating system error.

Action: Restore the log file from backup. If a backup is not available, drop this log and re-create it. If the database was shut down cleanly, no further action should be required; otherwise, incomplete recovery may be required.


ORA-00328 archived log ends at change string, need later change string

Cause: The archived log supplied for recovery was generated before the log that is needed. Cannot use the log for applying redo.

Action: Find the correct archived log.


ORA-00329 archived log begins at change string, need change string

Cause: The archived log is not the correct log. An earlier log is needed.

Action: Restore the correct log file.


ORA-00330 archived log ends at change string, need change string

Cause: The archived log is not the correct log. A later log is needed.

Action: Restore the correct log file.


ORA-00331 log version string incompatible with ORACLE version string

Cause: The log was written by an incompatible version of Oracle.

Action: Recover the database with the compatible software, shut it down cleanly, and then restart Oracle with the current software.


ORA-00332 archived log is too small - may be incompletely archived

Cause: The log is smaller than the space allocated in it. May be the result of a SHUTDOWN ABORT while it was being written by the archiver.

Action: Get a complete version of this log and use it for recovery. There should either be an online version of it or a copy that was successfully archived.


ORA-00333 redo log read error block string count string

Cause: An I/O error occurred while reading the log described in the accompanying error.

Action: Restore accessibility to file, or get another copy of the file.


ORA-00334 archived log: 'string'

Cause: This message reports the file name involved with other errors.

Action: See associated error messages.


ORA-00335 online log string: No log with this number, log does not exist

Cause: This message reports the file name involved with other errors.

Action: See associated error messages.


ORA-00336 log file size string blocks is less than minimum string blocks

Cause: The log file size as specified in the CREATE DATABASE statement is too small.

Action: Increase the log file size.


ORA-00337 log file 'string' does not exist and no size specified

Cause: An attempt to add a log found neither an existing file nor a size for creating the file.

Action: Specify a size for the log file.


ORA-00338 log string of thread string is more recent than controlfile

Cause: The control file change sequence number in the log file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.

Action: Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery.


ORA-00339 archived log does not contain any redo

Cause: The archived log is not the correct log. It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log.

Action: Restore the correct log file.


ORA-00340 IO error processing online log string of thread string

Cause: An I/O error occurred on the named online log.

Action: Restore accessibility to the file or restore the file from backup.


ORA-00341 log string of thread string, wrong log # string in header

Cause: The internal information in an online log file does not match the control file.

Action: Restore the correct file or reset the logs. Refer to the Oracle9i Database Administrator's Guide for recovery procedures.


ORA-00342 archived log was created before last RESETLOGS

Cause: Recovery was given a log that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another log created since then that contains the correct redo.

Action: Supply the correct log file.


ORA-00343 too many errors, log member closed

Cause: The maximum number of errors on this log member has been exceeded.

Action: Correct the underlying problem by referring to the other error messages found with this one.


ORA-00344 unable to re-create online log 'string'

Cause: An I/O failure occurred when attempting to re-create an online log as part of either an ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command.

Action: Correct the file/device as indicated by accompanying errors.


ORA-00345 redo log write error block string count string

Cause: An I/O error occurred while writing the log.

Action: Correct the cause of the error, and then restart the system. If the log is lost, apply media/incomplete recovery.


ORA-00346 log member marked as STALE

Cause: A log file member no longer is complete.

Action: Correct the underlying problem by referring to the other error messages found with this one.


ORA-00347 log string of thread string, expected block size string doesn't match string

Cause: During online recovery, the block size specified in the control file did not match the block size contained in the redo log file.

Action: Restore the correct redo file from a backup or reset the online redo log files.


ORA-00348 single-process redo failure. Must abort instance

Cause: A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation.

Action: SHUTDOWN ABORT and restart the database.


ORA-00349 failure obtaining block size for 'string'

Cause: The operating system was unable to determine the block size for the given file name.

Action: Consult the accompanying error message, and correct the device or specify another file name.


ORA-00350 log string of thread string needs to be archived

Cause: The command cannot be done because the log has not been archived, and media recovery has been enabled.

Action: Archive the log or disable media recovery. If the command supports an UNARCHIVED option, then it can be used. However, this may result in making backups unusable, and forcing the drop of some offline files.


관련글 : 없음 글쓴시간 : 2004/05/04 0:13 from 218.38.148.205

  [ORA-00351~ORA0816]Error 목록보기 새글 쓰기 지우기 응답글 쓰기 글 수정 [ORA-00101~ORA-00250]Error  
BACKRUSH  유닉스명령  다음  자료실  Ascii Table   원격접속  달력,시간   프로세스  
지하철노선   RFC문서   SUN FAQ   SUN FAQ1   C메뉴얼   PHP메뉴얼   너구리   아스키월드 아이피서치