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
Showing posts with label ora-code. Show all posts
Showing posts with label ora-code. Show all posts
Sunday, November 9, 2014
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
Subscribe to:
Posts (Atom)