ORA-01130: database file version string incompatible with ORACLE version string
Cause: The named datafile was created under an incompatible version of Oracle, or the file is invalid or non-existent.
Action: Shut down and restart the correct version of Oracle or check the references to the datafile and make sure it exists.
ORA-01129: user’s default or temporary tablespace does not exist
Cause: The user’s default or temporary tablespace was dropped.
Action: Reassign the default or temporary tablespace.
ORA-01128: cannot start online backup – file string is offline
Cause: An attempt to start an online backup found that one of the files is offline.
Action: Bring the offending files online and retry this command or do a cold backup.
ORA-01127: database name ‘string’ exceeds size limit of string characters
Cause: Obvious
Action: none
ORA-01126: database must be mounted in this instance and not open in any instance
Cause: Obvious
Action: none
ORA-01125: cannot disable media recovery – file string has online backup set
Cause: An attempt to disable media recovery found that an online backup is still in progress.
Action: End the backup of the offending tablespace and retry this command.
ORA-01124: cannot recover data file string – file is in use or recovery
Cause: An attempt to do media recovery found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is curently doing media recovery on the file.
Action: Do not do media recovery.
ORA-01123: cannot start online backup; media recovery not enabled
Cause: An attempt to start backup of an on-line tablespace failed because media recovery is not enabled.
Action: Enable media recovery and retry this operation.
ORA-01122: database file string failed verification check
Cause: The information in this file is inconsistent with information from the control file. See accompanying message for reason.
Action: Make certain that the db files and control files are the correct files for this database.
ORA-01121: cannot rename database file string – file is in use or recovery
Cause: Attempted to use ALTER DATABASE RENAME to rename a datafile that is online in an open instance or is being recovered.
Action: Close database in all instances and end all recovery sessions.