Oracle Database Errors or Warnings from Error ORA-00391 to ORA-00400
ORA-00391: All threads must switch to new log format at the same time
Cause: An attempt to switch the current log of a single thread is not allowed because the compatiblity requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time.
Action: Open the database to cause the coordinated log switch. If that is not possible then return to the same software version and compatibility setting last used to open the database.
ORA-00392: log string of thread string is being cleared, operation not allowed
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.
ORA-00393: log string of thread string is needed for recovery of offline datafiles
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 then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptible, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.
ORA-00394: online log reused while attempting to archive it
Cause: It has been detected that an online log that is being archived has been reused
Action: Cannot archive the logfile anymore since it has been overwritten
ORA-00395: online logs for the clone database must be renamed
Cause: A clone database open forces logfile renaming to avoid overwriting the primary logfiles
Action: Rename the logfiles manually or using the log_file_name_convert initialization parameter
ORA-00396: error string required fallback to single-pass recovery
Cause: The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error.
Action: Correct the cause of the indicated error (also recorded) so that future instance or crash recovery can succeed with the two-pass algorithm. This usually requires making more main memory available to the recovery process.
ORA-00397: instance recovery process terminated with error
Cause: The foreground process doing instance recovery died.
Action: Check the foreground trace file for the cause of recovery failure.
ORA-00398: abort thread recovery due to reconfiguration
Cause: Global enqueue service reconfiguration occurred during instance/crash recovery.
Action: This is used internally, no action is required.
ORA-00399: corrupt change description in redo log
Cause: A change vector in the redo log failed validation checks.
Action: Do recovery with a good version of the log or do time based recovery up to the indicated time.
ORA-00400: invalid release value string for parameter string
Cause: The release level given for the specified init parameter is invalid.
Action: Correct the parameter value in the parameter file and retry.
Above are list of Oracle Database Errors or Warnings from Error ORA-00391 to ORA-00400 received while performing certain operation against Oracle Database or related products.
What are Oracle Database Error Messages?
Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.
Hope this was helpful.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.