Table of Contents

Search

  1. Preface
  2. IDR-000000 to IDR-000731
  3. IDR-008001 to IDR-008006
  4. IDR-009001 to IDR-009055
  5. IDR-010002 to IDR-010821
  6. IDR-020001 to IDR-020264
  7. IDR-030001 to IDR-031230
  8. IDR-050001 to IDR-053223
  9. IDR-060002 to IDR-060124
  10. IDR-070002 to IDR-070361
  11. IDR-100001 to IDR-100030
  12. IDR-110030 to IDR-110031
  13. IDR-120001 to IDR-120007
  14. IDR-130001 to IDR-130053
  15. IDR-140001 to IDR-140054
  16. IDR-150001 to IDR-150017
  17. CDCPUB_10001 to CDCPUB_16001

IDR- 031016

IDR-
031016

[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.

0 COMMENTS

We’d like to hear from you!