ORA-00322 log %s of thread %s is not current copy

Cause: Check of log file header at database open found that an online log appears to be an incorrectly restored backup. Action: Restore correct file or reset

ORA-00340 IO error processing online log %s of thread %s

Cause: An IO error occurred on the named online log. Action: Restore accessibility to file, or restore file from backup.

ORA-00232 Snapshot control file is nonexistent, corrupt, or unreadable

Cause: The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot. Action: Call cfileMakeAndUseSnapshot again (or for the first time).

ORA-00238 Operation would reuse a filename that is part of the database

Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database. Action: Retry the operation with a different filename.

ORA-00337 Log file ‘%s’ does not exist and no size specified

Cause: An attempt to add a log found neither an existing file nor a size for creating the file. Action: Specify a size for the log file.

ORA-00331 log version %s incompatible with ORACLE version %s

Cause: The log was written by incompatible version of Oracle. Action: Recover the database with the compatible software, shut it down cleanly, then restart with current software.

ORA-00306 Limit of %s instances in this database

Cause: Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances. Action: You cannot start more than the lower of a) port-specific limit as to the number of instances b) the number of instances specified at create-database time

ORA-00325 Archived log for thread %s, wrong thread # %s in header

Cause: The archived log is corrupted or for another thread. Can not use the log for applying redo. Action: Find correct archived log.

ORA-00305 Log %s of thread %s inconsistent; belongs to another database

Cause: The database ID in the redo log file does not match the database ID in the control file. This redo log file is not from the current database. Action: Specify the correct redo log file, then retry the operation.

ORA-00309 Log belongs to wrong database

Cause: The system cannot access the archived redo log because it belongs to another database. Action: Specify the correct redo log file, then retry the operation.