Oracle Database Errors or Warnings from Error ORA-01361 to ORA-01370
ORA-01361: global name mismatch
Cause: The database global name where the log file was generated did not match the user-specified global name of the Streams Capture process.
Action: Start a new capture process and ensure that the user-specified global name matches that of the database that generated the log file.
ORA-01362: Specified SQL_REDO_UNDO parameter is invalid
Cause: The specified input value for the parameter was not a valid number.
Action: Specify a valid number and try again.
ORA-01363: Specified COLUMN_NAME parameter is NULL
Cause: NULL was specified for input value of parameter.
Action: Specify a non-NULL value and try again.
ORA-01364: waiting for branch at SCN string
Cause: LogMiner reader process has completed mining of physical standby terminal logs up to the stop SCN. LogMiner reader is now waiting for logs from the new branch.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. If there is a problem with log transport, the files can be registered manually using the ALTER DATABASE REGISTER LOGICAL LOGFILE statement.
ORA-01365: waiting for new branch registration
Cause: LogMiner reader process has completed mining of physical standby terminal logs up to the stop SCN. The builder process is now waiting for logs from the new branch to be registered before continuing.
Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. If there is a problem with log transport, the files may be registered manually using the ALTER DATABASE REGISTER LOGICAL LOGFILE statement.
ORA-01366: failed to find redo logs required for terminal apply
Cause: LogMiner failed to find all the expected log files required to complete the terminal apply, requested using the FINISH APPLY clause. During terminal apply, LogMiner does not wait for logs to be registered. It expects all logs between the starting point and the last log on any redo branch that it will or could mine through, to be present at the mining site.
Action: Examine system.logmnr_log$ to see which logs are known to LogMiner. Then, locate or restore any missing logs and use the ALTER DATABASE REGISTER LOGICAL LOGFILE statement to register them. Alternatively, do not use the FINISH APPLY clause, but if activating a logical standby, only do this when you are sure that the missing log files can not be located and registered as this can lead to data loss.
ORA-01370: Specified restart SCN is too old
Cause: specified restart scn is too old, logmnr could not find a proper checkpoint.
Action: Specify a bigger restart SCN to try again
Above are list of Oracle Database Errors or Warnings from Error ORA-01361 to ORA-01370 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.