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

Cause : Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared, the tablespaces containing the files will have to be dropped.
Action : Archive the log and then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptable, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.

Popularity: 11% [?]

Share This

Cause : An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing.
Action : If the clear command is still executing, then wait for its completion. If it terminated, then reissue the clear command or drop the log.

Popularity: 11% [?]

Share This

Cause : An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be usable when the clearing completes. The command that began the clearing may have terminated without completing the clearing.
Action : If the clear command is still executing, then wait for its completion. If it terminated, then reissue the clear command, or drop the log.

Popularity: 11% [?]

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

Popularity: 24% [?]

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 : 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 Oracle8i Administrator’s Guide for recovery procedures.

Popularity: 9% [?]

Share This

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.

Popularity: 14% [?]

Share This

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

Popularity: 21% [?]

Share This

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.

Popularity: 8% [?]

Share This