beta-zhou commented on issue #11965: URL: https://github.com/apache/seatunnel/issues/11965#issuecomment-5426480650
> Thanks for the detailed background and log. > > From the current Oracle-CDC behavior, this error usually means SeaTunnel / Debezium is trying to resume from an old SCN that is no longer present in the Oracle redo or archive logs after the upstream OGG / mirror pipeline was rebuilt. In other words, `Online REDO LOG files or archive log files do not contain the offset scn ... Please perform a new snapshot.` points to an invalid resume position; by itself it does not prove that SeaTunnel moved the SCN backward. > > On current SeaTunnel, Oracle-CDC supports `startup.mode = initial | latest | timestamp | specific`, and `startup.specific-offset.scn` must still exist in the selected log-mining backend. Also, when a CDC job is restored from checkpoint or savepoint, it resumes from the checkpointed offset path rather than starting a fresh snapshot automatically. > > Before maintainers can call this a product bug, could you please add: > > 1. the exact SeaTunnel version and full Oracle-CDC source config, especially `startup.mode`, any `startup.specific-offset.scn`, heartbeat settings, and whether checkpointing / exactly-once is enabled; > 2. whether this job was restarted from checkpoint / savepoint or submitted fresh after the OGG rebuild; > 3. whether the OGG rebuild reinitialized the mirror from an earlier point or recreated redo / archive history so the old SCN disappeared; > 4. whether restarting with `startup.mode=initial`, or from a new valid SCN / timestamp on the rebuilt mirror, resolves the failure. > > If the old SCN is gone after the upstream rebuild, the immediate recovery path is usually a fresh snapshot (`startup.mode=initial`) or a controlled restart from a valid current SCN / timestamp on the rebuilt mirror. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
