Error Code
ORA-00299
Description
Must use file-level media recovery on data file string.
Cause
Possible cause of this error is, the control file does not contain an entry for this file, so block media recovery cannot be done.
Action
To fix this issue, restore the data file and perform file-level media recovery.
reference
Monday, November 10, 2014
ORA-00298 Missing or invalid attribute value
Error Code
ORA-00298
Description
Missing or invalid attribute value.
Cause
Possible cause of this error is, a non-zero integer value is required when the following keyword attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT
Action
To fix this issue, correct the syntax and retry the command.
reference
ORA-00298
Description
Missing or invalid attribute value.
Cause
Possible cause of this error is, a non-zero integer value is required when the following keyword attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT
Action
To fix this issue, correct the syntax and retry the command.
reference
ORA-00297 Must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START
Error Code
ORA-00297
Description
Must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START.
Cause
Possible cause of this error is, 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
To fix this issue, contact customer support
reference
ORA-00297
Description
Must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START.
Cause
Possible cause of this error is, 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
To fix this issue, contact customer support
reference
ORA-00296 Maximum number of files exceeded for RECOVER DATAFILE LIST
Error Code
ORA-00296
Description
Maximum number of files (string) exceeded for RECOVER DATAFILE LIST.
Cause
Possible cause of this error is, 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
To fix this issue, re-start the instance with a higher value for DB_FILES.
reference
ORA-00296
Description
Maximum number of files (string) exceeded for RECOVER DATAFILE LIST.
Cause
Possible cause of this error is, 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
To fix this issue, re-start the instance with a higher value for DB_FILES.
reference
ORA-00295 Datafile number string is invalid
Error Code
Possible cause of this error is, an invalid file number was specified.
Action
To fix this issue, specify a valid datafile or tempfile number and retry the operation.
reference
ORA-00295
DescriptionDatafile/tempfile number string is invalid, must be between 1 and string.
CausePossible cause of this error is, an invalid file number was specified.
Action
To fix this issue, specify a valid datafile or tempfile number and retry the operation.
reference
Sunday, November 9, 2014
ORA-00294 Invalid archivelog format specifier string
Error Code
Description
Cause
Possible cause of this error is, 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
To fix this issue, correct the initialization file and re-start the instance.
reference
ORA-00294
Description
Invalid archivelog format specifier 'string'.
Cause
Possible cause of this error is, 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
To fix this issue, correct the initialization file and re-start the instance.
reference
ORA-00293 Control file out of sync with redo log
Error Code
ORA-00293
Description
Control file out of sync with redo log.
Cause
Possible cause of this error is, 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
To fix this issue, retry the RECOVER command using the current control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause.
reference
ORA-00293
Description
Control file out of sync with redo log.
Cause
Possible cause of this error is, 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
To fix this issue, retry the RECOVER command using the current control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause.
reference
ORA-00292 Parallel recovery feature not installed
Error Code
ORA-00292
Description
Parallel recovery feature not installed.
Cause
Possible cause of this error is, a parallel recovery was requested when the parallel recovery option is not installed.
Action
To fix this issue, delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file.
reference
ORA-00292
Description
Parallel recovery feature not installed.
Cause
Possible cause of this error is, a parallel recovery was requested when the parallel recovery option is not installed.
Action
To fix this issue, delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file.
reference
ORA-00291 Numeric value required for PARALLEL option
Error Code
ORA-00291
Description
Numeric value required for PARALLEL option.
Cause
Possible cause of this error is, a recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.
Action
To fix this issue, re-enter the command with a numeric argument specifying the degree of parallelism desired.
reference
ORA-00291
Description
Numeric value required for PARALLEL option.
Cause
Possible cause of this error is, a recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.
Action
To fix this issue, re-enter the command with a numeric argument specifying the degree of parallelism desired.
reference
ORA-00290 Operating system archival error occurred
Error Code
ORA-00290
Description
Operating system archival error occurred. See error below.
Cause
Possible cause of this error is, while attempting to archive to a redo log file, the server encountered an unexpected operating system error.
Action
To fix this issue, correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation.
reference
ORA-00290
Description
Operating system archival error occurred. See error below.
Cause
Possible cause of this error is, while attempting to archive to a redo log file, the server encountered an unexpected operating system error.
Action
To fix this issue, correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation.
reference
ORA-00289 Suggestion string
Error Code
ORA-00289
Description
Suggestion : string
Cause
Possible cause of this error is, 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
To fix this issue, consider using this filename for the next log needed for recovery.
reference
ORA-00289
Description
Suggestion : string
Cause
Possible cause of this error is, 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
To fix this issue, consider using this filename for the next log needed for recovery.
reference
ORA-00288 To continue recovery type ALTER DATABASE RECOVER CONTINUE
Error Code
ORA-00288
Description
To continue recovery type ALTER DATABASE RECOVER CONTINUE.
Cause
Possible cause of this error is, during media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors.
Action
To fix this issue, type ALTER DATABASE RECOVER CONTINUE and recovery will resume.
reference
ORA-00288
Description
To continue recovery type ALTER DATABASE RECOVER CONTINUE.
Cause
Possible cause of this error is, during media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors.
Action
To fix this issue, type ALTER DATABASE RECOVER CONTINUE and recovery will resume.
reference
ORA-00287 Specified change number string not found in thread string
Error Code
ORA-00287
Description
Specified change number string not found in thread string.
Cause
Possible cause of this error is, the given change number does not appear in any of the online redo logs for the given thread.
Action
To fix this issue, check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs.
reference
ORA-00287
Description
Specified change number string not found in thread string.
Cause
Possible cause of this error is, the given change number does not appear in any of the online redo logs for the given thread.
Action
To fix this issue, check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs.
reference
ORA-00286 No members available, or no member contains valid data
Error Code
ORA-00286
Description
No members available, or no member contains valid data.
Cause
Possible cause of this error is, none of the members of a redo log file group are available, or the available members do not contain complete data.
Action
To fix this issue, 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.
reference
ORA-00286
Description
No members available, or no member contains valid data.
Cause
Possible cause of this error is, none of the members of a redo log file group are available, or the available members do not contain complete data.
Action
To fix this issue, 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.
reference
ORA-00285 TIME not given as a string constant
Error Code
ORA-00285
Description
TIME not given as a string constant.
Cause
Possible cause of this error is, UNTIL TIME was not followed by a string constant for the time.
Action
To fix this issue, enter the time enclosed in single quotation marks.
reference
ORA-00285
Description
TIME not given as a string constant.
Cause
Possible cause of this error is, UNTIL TIME was not followed by a string constant for the time.
Action
To fix this issue, enter the time enclosed in single quotation marks.
reference
ORA-00284 Recovery session still in progress
Error Code
ORA-00284
Description
Recovery session still in progress.
Cause
Possible cause of this error is, an error during recovery was determined to be minor enough to allow the current recovery session to continue.
Action
To fix this issue, more specific messages will accompany this message. Refer to the other messages for the appropriate action.
reference
ORA-00284
Description
Recovery session still in progress.
Cause
Possible cause of this error is, an error during recovery was determined to be minor enough to allow the current recovery session to continue.
Action
To fix this issue, more specific messages will accompany this message. Refer to the other messages for the appropriate action.
reference
ORA-00283 Recovery session canceled due to errors
Error Code
ORA-00283
Description
Recovery session canceled due to errors.
Cause
Possible cause of this error is, an error during recovery was determined to be fatal enough to end the current recovery session.
Action
To fix this issue, more specific messages will accompany this message. Refer to the other messages for the appropriate action.
reference
ORA-00283
Description
Recovery session canceled due to errors.
Cause
Possible cause of this error is, an error during recovery was determined to be fatal enough to end the current recovery session.
Action
To fix this issue, more specific messages will accompany this message. Refer to the other messages for the appropriate action.
reference
ORA-00282 UPI string call not supported, use ALTER DATABASE RECOVER
Error Code
ORA-00282
Description
UPI string call not supported, use ALTER DATABASE RECOVER.
Cause
Possible cause of this error is, the given UPI call is no longer supported.
Action
To fix this issue, use the ALTER DATABASE RECOVER command for all recovery actions.
reference
ORA-00282
Description
UPI string call not supported, use ALTER DATABASE RECOVER.
Cause
Possible cause of this error is, the given UPI call is no longer supported.
Action
To fix this issue, use the ALTER DATABASE RECOVER command for all recovery actions.
reference
ORA-00281 Media recovery may not be performed using dispatcher
Error Code
ORA-00281
Description
Media recovery may not be performed using dispatcher.
Cause
Possible cause of this error is, an attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method.
Action
To fix this issue, connect to the instance via a dedicated server process to perform media recovery.
reference
ORA-00281
Description
Media recovery may not be performed using dispatcher.
Cause
Possible cause of this error is, an attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method.
Action
To fix this issue, connect to the instance via a dedicated server process to perform media recovery.
reference
ORA-00280 Change string for thread string is in sequence string
Error Code
ORA-00280
Description
Change string for thread string is in sequence #string.
Cause
Possible cause of this error is, this message helps to locate the redo log file with the specified change number requested by other messages.
Action
To fix this issue, use the information provided in this message to specify the required archived redo log files for other errors.
reference
ORA-00280
Description
Change string for thread string is in sequence #string.
Cause
Possible cause of this error is, this message helps to locate the redo log file with the specified change number requested by other messages.
Action
To fix this issue, use the information provided in this message to specify the required archived redo log files for other errors.
reference
ORA-00279 Change string generated at string needed for thread string
Error Code
ORA-00279
Description
Change string generated at string needed for thread string.
Cause
Possible cause of this error is, the requested log is required to proceed with recovery.
Action
To fix this issue, please supply the requested log with "ALTER DATABASE RECOVER LOGFILE <file_name>" or cancel recovery with "ALTER DATABASE RECOVER CANCEL".
reference
ORA-00279
Description
Change string generated at string needed for thread string.
Cause
Possible cause of this error is, the requested log is required to proceed with recovery.
Action
To fix this issue, please supply the requested log with "ALTER DATABASE RECOVER LOGFILE <file_name>" or cancel recovery with "ALTER DATABASE RECOVER CANCEL".
reference
Friday, November 7, 2014
ORA-00278 Log file string no longer needed for this recovery
Error Code
ORA-00278
Description
Log file string no longer needed for this recovery.
Cause
Possible cause of this error is, 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.
reference
ORA-00278
Description
Log file string no longer needed for this recovery.
Cause
Possible cause of this error is, 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.
reference
ORA-00277 Illegal option to the UNTIL recovery flag string
Error Code
ORA-00277
Description
Illegal option to the UNTIL recovery flag string.
Cause
Possible cause of this error is, only CANCEL, CHANGE and TIME can be used with the UNTIL keyword.
Action
To fix this issue, correct the syntax.
reference
ORA-00277
Description
Illegal option to the UNTIL recovery flag string.
Cause
Possible cause of this error is, only CANCEL, CHANGE and TIME can be used with the UNTIL keyword.
Action
To fix this issue, correct the syntax.
reference
ORA-00276 CHANGE keyword specified but no change number given
Error Code
ORA-00276
Description
CHANGE keyword specified but no change number given.
Cause
Possible cause of this error is, the CHANGE keyword was specified on the command line, but no change number was given.
Action
To fix this issue, retry the command using a valid change number after the CHANGE keyword.
reference
ORA-00276
Description
CHANGE keyword specified but no change number given.
Cause
Possible cause of this error is, the CHANGE keyword was specified on the command line, but no change number was given.
Action
To fix this issue, retry the command using a valid change number after the CHANGE keyword.
reference
ORA-00275 Media recovery has already been started
Error Code
ORA-00275
Description
Media recovery has already been started.
Cause
Possible cause of this error is, an attempt was made to start a second media recovery operation in the same session.
Action
To fix this issue, complete or cancel the first media recovery session or start another session to perform media recovery.
reference
ORA-00275
Description
Media recovery has already been started.
Cause
Possible cause of this error is, an attempt was made to start a second media recovery operation in the same session.
Action
To fix this issue, complete or cancel the first media recovery session or start another session to perform media recovery.
reference
ORA-00274 Illegal recovery option string
Error Code
ORA-00274
Description
Illegal recovery option string.
Cause
Possible cause of this error is, an illegal option was specified for a recovery command.
Action
To fix this issue, correct the syntax and retry the command.
reference
ORA-00274
Description
Illegal recovery option string.
Cause
Possible cause of this error is, an illegal option was specified for a recovery command.
Action
To fix this issue, correct the syntax and retry the command.
reference
Wednesday, October 29, 2014
ORA-00273 Media recovery of direct load data that was not logged
Error Code
ORA-00273
Description
Media recovery of direct load data that was not logged.
Cause
Possible cause of this error is, 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
To fix this issue, 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.
reference
ORA-00273
Description
Media recovery of direct load data that was not logged.
Cause
Possible cause of this error is, 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
To fix this issue, 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.
reference
ORA-00272 Error writing archive log string
Error Code
ORA-00272
Description
Error writing archive log string.
Cause
Possible cause of this error is, an I/O error occurred while archiving a redo log file.
Action
To fix this issue, 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.
reference
ORA-00272
Description
Error writing archive log string.
Cause
Possible cause of this error is, an I/O error occurred while archiving a redo log file.
Action
To fix this issue, 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.
reference
ORA-00271 There are no logs that need archiving
Error Code
ORA-00271
Description
There are no logs that need archiving.
Cause
Possible cause of this error is, 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.
reference
ORA-00271
Description
There are no logs that need archiving.
Cause
Possible cause of this error is, 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.
reference
ORA-00270 Error creating archive log string
Error Code
ORA-00270
Description
Error creating archive log string.
Cause
Possible cause of this error is, an error was encountered when either creating or opening the destination file for archiving.
Action
To fix this issue, check that the archive destination is valid and that there is sufficient space on the destination device.
reference
ORA-00270
Description
Error creating archive log string.
Cause
Possible cause of this error is, an error was encountered when either creating or opening the destination file for archiving.
Action
To fix this issue, check that the archive destination is valid and that there is sufficient space on the destination device.
reference
Monday, October 27, 2014
ORA-00269 Specified log file is part of thread string not string
Error Code
ORA-00269
Description
Specified log file is part of thread string not string.
Cause
Possible cause of this error is, the given redo log file is not part of the given thread.
Action
To fix this issue, 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.
reference
ORA-00269
Description
Specified log file is part of thread string not string.
Cause
Possible cause of this error is, the given redo log file is not part of the given thread.
Action
To fix this issue, 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.
reference
ORA-00268 Specified log file does not exist string
Error Code
ORA-00268
Description
Specified log file does not exist 'string'.
Cause
Possible cause of this error is, the given redo log file does not exist.
Action
To fix this issue, check the spelling and capitalization of the filename and retry the command.
reference
ORA-00268
Description
Specified log file does not exist 'string'.
Cause
Possible cause of this error is, the given redo log file does not exist.
Action
To fix this issue, check the spelling and capitalization of the filename and retry the command.
reference
ORA-00267 Name of archived log file not needed
Error Code
ORA-00267
Description
Name of archived log file not needed.
Cause
Possible cause of this error is, during media recovery, the name of an archived redo log file was entered, but no name was requested.
Action
To fix this issue, continue media recovery, but do not enter a new log name.
reference
ORA-00267
Description
Name of archived log file not needed.
Cause
Possible cause of this error is, during media recovery, the name of an archived redo log file was entered, but no name was requested.
Action
To fix this issue, continue media recovery, but do not enter a new log name.
reference
ORA-00266 Name of archived log file needed
Error Code
ORA-00266
Description
Name of archived log file needed.
Cause
Possible cause of this error is, during media recovery, the name of an archived redo log file was requested, but no name was entered.
Action
To fix this issue, mount the correct redo log file and enter its name when it is requested.
reference
ORA-00266
Description
Name of archived log file needed.
Cause
Possible cause of this error is, during media recovery, the name of an archived redo log file was requested, but no name was entered.
Action
To fix this issue, mount the correct redo log file and enter its name when it is requested.
reference
ORA-00265 Instance recovery required, cannot set ARCHIVELOG mode
Error Code
ORA-00265
Description
Instance recovery required, cannot set ARCHIVELOG mode.
Cause
Possible cause of this error is, 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
To fix this issue, open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.
reference
ORA-00265
Description
Instance recovery required, cannot set ARCHIVELOG mode.
Cause
Possible cause of this error is, 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
To fix this issue, open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.
reference
ORA-00264 No recovery required
Error Code
ORA-00264
Description
No recovery required.
Cause
Possible cause of this error is, an attempt was made to perform media recovery on files that do not // need any type of recovery.
Action
To fix this issue, 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.
reference
ORA-00264
Description
No recovery required.
Cause
Possible cause of this error is, an attempt was made to perform media recovery on files that do not // need any type of recovery.
Action
To fix this issue, 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.
reference
ORA-00263 there are no logs that need archiving for thread string
Error Code
ORA-00263
Description
There are no logs that need archiving for thread string.
Cause
Possible cause of this error is, an attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving.
Action
No action required.
reference
ORA-00263
Description
There are no logs that need archiving for thread string.
Cause
Possible cause of this error is, an attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving.
Action
No action required.
reference
ORA-00262 Current log string of closed thread string cannot switch
Error Code
ORA-00262
Description
Current log string of closed thread string cannot switch.
Cause
Possible cause of this error is, 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
To fix this issue, archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed.
reference
ORA-00262
Description
Current log string of closed thread string cannot switch.
Cause
Possible cause of this error is, 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
To fix this issue, archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed.
reference
ORA-00261 Log string of thread string is being archived or modified
Error Code
ORA-00261
Description
Log string of thread string is being archived or modified.
Cause
Possible cause of this error is, 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
To fix this issue, wait for the current operation to complete and try again.
reference
ORA-00261
Description
Log string of thread string is being archived or modified.
Cause
Possible cause of this error is, 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
To fix this issue, wait for the current operation to complete and try again.
reference
ORA-00260 Cannot find online log sequence string for thread string
Error Code
ORA-00260
Description
Cannot find online log sequence string for thread string.
Cause
Possible cause of this error is, 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
To fix this issue, check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.
reference
ORA-00260
Description
Cannot find online log sequence string for thread string.
Cause
Possible cause of this error is, 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
To fix this issue, check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.
reference
ORA-00259 Log string of open instance string is the current log, cannot archive
Error Code
ORA-00259
Description
Log string of open instance string (thread string) is the current log, cannot archive.
Cause
Possible cause of this error is, 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
To fix this issue, 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.
reference
ORA-00259
Description
Log string of open instance string (thread string) is the current log, cannot archive.
Cause
Possible cause of this error is, 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
To fix this issue, 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.
reference
ORA-00258 Manual archiving in NOARCHIVELOG mode must identify log
Error Code
ORA-00258
Description
Manual archiving in NOARCHIVELOG mode must identify log.
Cause
Possible cause of this error is, 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
To fix this issue, Specify log by filename, by group number or by thread and sequence number.
reference
ORA-00258
Description
Manual archiving in NOARCHIVELOG mode must identify log.
Cause
Possible cause of this error is, 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
To fix this issue, Specify log by filename, by group number or by thread and sequence number.
reference
ORA-00257 Archiver error. Connect internal only, until freed.
Error Code
ORA-00257
Description
Archiver error. Connect internal only, until freed.
Cause
Possible cause of this error is, 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
To fix this issue, 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.
reference
ORA-00257
Description
Archiver error. Connect internal only, until freed.
Cause
Possible cause of this error is, 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
To fix this issue, 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.
reference
ORA-00256 cannot translate archive destination string
Error Code
ORA-00256
Description
cannot translate archive destination string string.
Cause
Possible cause of this error is, the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.
Action
To fix this issue, check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string.
reference
ORA-00256
Description
cannot translate archive destination string string.
Cause
Possible cause of this error is, the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.
Action
To fix this issue, check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string.
reference
Wednesday, October 22, 2014
ORA-00255 Error archiving log string of thread string
Error Code
ORA-00255
Description
Error archiving log string of thread string, sequence # string
Cause
Possible cause of this error is, an error occurred during archiving.
Action
To fix this issue, 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.
reference
ORA-00255
Description
Error archiving log string of thread string, sequence # string
Cause
Possible cause of this error is, an error occurred during archiving.
Action
To fix this issue, 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.
reference
Subscribe to:
Posts (Atom)