ORA-00328 Archived log ends at change %s, need later change %s
Cause: The archived log supplied for recovery was generated before the log that is needed. Can not use the log for applying redo. Action: Find correct archived log.
Cause: The archived log supplied for recovery was generated before the log that is needed. Can not use the log for applying redo. Action: Find correct archived log.
Cause: The archived log is out of sequence, probably because it is corrupted or the wrong redo log filename was specified during recovery. Action: Specify the correct redo log file; then retry the ope
Cause: An I/O error occurred while archiving a redo log file. Action: Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device.
Cause: Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs need to be archived before they can be used. Action: Archive the logs for the thread then retry open.
Cause: An I/O error occurred when attempting to read the log file header from the specified archived redo log file. Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.
Cause: The file is not available. Action: Restore the log file.
Cause: An I/O error occurred when attempting to read the log file header from the specified archived redo log file. Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.
Cause: The initialization parameter INSTANCE_NUMBER specified a number that was out of range. Action: Change INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is one and the maximum value is the lower of the operating system-specific maximum or the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating…
Cause: Cannot write to the log file. Action: Restore the access to the file.
Cause: The archived log is out of sequence, probably because it is corrupted or the wrong redo log filename was specified during recovery. Action: Specify the correct redo log file; then retry the operation.