Table of Contents

Search

  1. Preface
  2. IDR-000000 to IDR-000704
  3. IDR-008001 to IDR-008006
  4. IDR-009001 to IDR-009055
  5. IDR-010002 to IDR-010812
  6. IDR-020001 to IDR-020264
  7. IDR-030001 to IDR-031041
  8. IDR-050001 to IDR-053222
  9. IDR-060002 to IDR-060123
  10. IDR-070002 to IDR-070351
  11. IDR-100001 to IDR-100030
  12. IDR-110030 to IDR-110031
  13. IDR-120001 to IDR-120007
  14. IDR-140001 to IDR-140054
  15. IDR-150001 to IDR-150014
  16. QADPTR-10001 to QADPTR-16001

IDR- 031019

IDR-
031019

[WARNING] Missing redo logs for a database incarnation. Possible cause is a race condition. The "prev timestamp" value of the next incarnation does not match the "timestamp" value of the previous incarnation. 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
.
The redo log for the new incarnation is online. The Extractor will try to remove the online redo logs for the new incarnation from its processing queue.
After a RESETLOGS event, the Oracle Extractor detected a database incarnation for which the redo logs are missing. This situation might occur because of a race condition. The Extractor will try to remove the online redo logs for the new incarnation from its processing queue to continue extraction processing.
No response is needed.

0 COMMENTS

We’d like to hear from you!