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

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