Cause: An add logfile or add logfile member command would result in a log with too many members. The number of members is set when the database is created. Action: Use fewer log file members.
Cause: An attempt has been made to remove the last member of a log file group. Action: If desired, delete the entire log, by using DROP LOGFILE.
Cause: A create or alter statement specified too many members in a parenthesised file list. Action: Specify a number of file members that is within the port-defined limit.
Cause: A filename was given to drop logfile member that is not a part of the database, or which is a data file. Action: Supply a valid logfile member name.
Cause: A change number found in the redo log is lower than a previously encountered change number. The log is corrupted in some way. The corruption may be at the earlier change or at this one. Action: Do recovery with a good version of the log or do time based recovery up to the indicated…
Cause: Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption. Action: Do recovery with a good version of the log or do incomplete recovery up to the indicated change or time.
Cause: An IO error has 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.
Cause: Check of log file header at database open found that an online log has log reset data that is different from the control file. The log is probably an incorrectly restored backup. Action: Restore correct file or reset logs.
Cause: An I/O failure occurred when attempting to re-create an online as part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command. Action: Correct the file/device as indicated by accompanying errors.
Cause: An IO error occurred while reading the log described in the accompanying error. Action: Restore accessibility to file, or get another copy of the file.