[ERROR] The first available redo log for the next database incarnation does not have the expected sequence of 1. Thread:
thread_ID
.
Redo log for the previous incarnation:
file_name
. Sequence:
sequence_number
. First SCN:
SCN_value
. Next SCN:
SCN_value
. RESETLOGS SCN:
SCN_value
. RESETLOGS timestamp:
timestamp_value
.
Redo log for the next incarnation:
file_name
. Sequence:
sequence_number
. First SCN:
SCN_value
. Next SCN:
SCN_value
. RESETLOGS SCN:
SCN_value
. RESETLOGS timestamp:
timestamp_value
.
These redo logs are archived. The next database incarnation is missing some redo logs.
After an Oracle RESETLOGS event, the first available redo log for the next database incarnation does not have the sequence number of 1 as expected. Both the redo log for the previous database incarnation and the first redo log for the next database incarnation are archived. Therefore, no race condition exists. As a result, some redo logs for the new database incarnation are missing.
Ensure that the Extractor has access to all of the redo logs for the next database incarnation, starting from the log sequence number of 1.