Cause: The network specified in the SQL*Net connect string is reserved for use by the dispatchers. Action: Specify other network protocols in the connection string.
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 log or reset logs.
Cause: A request to drop a logfile member was denied because it would remove data required to form a complete logfile. Action: If desired, delete the entire log (after archiving if required), by using DROP LOGFILE;
Cause: An add logfile member or drop logfile request specified a logfile group number that does not exist. Action: Check the configuration of the log files and reissue the command.
Cause: The log given to recovery is a backup of the online version from the time it was the current log. The archived version of the log would not be marked as end of thread. This error can also be caused by failing to list the current log of an enabled thread in a CREATE…
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…