Find Oracle Error Code Ora- and Pl/SQL Tips and Tricks

Cause : The redo block indicated by the accompanying error, is not valid. It has a checksum that does not match the block contents.
Action : Perform recovery with a good version of the log or do time-based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database. Restore the correct file or reset logs.

Popularity: 15% [?]

Share This

Cause : The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted.
Action : Find and install correct version of the log or reset the logs.

Popularity: 13% [?]

Share This

Cause : The block header on the redo block indicated by the accompanying error is not valid. The block number and time-stamp are given in an accompanying message.
Action : Perform recovery with a good version of the redo log or perform cancel-based recovery up to, but not including, the corrupted redo log file. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database.

Popularity: 16% [?]

Share This

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.

Popularity: 17% [?]

Share This

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.

Popularity: 16% [?]

Share This

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.

Popularity: 13% [?]

Share This

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.

Popularity: 16% [?]

Share This

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.

Popularity: 8% [?]

Share This