DanielLeens commented on issue #11965: URL: https://github.com/apache/seatunnel/issues/11965#issuecomment-5438932197
Thanks for adding the concrete config and restart history. I rechecked the current Oracle-CDC restore path on `apache/dev` (`e6caf5a4b337`). With this config, `startup.mode` is not set, so a fresh submission defaults to `initial`. But when the old job is restarted from its saved state, the CDC enumerator restores the checkpointed startup offset and continues from that stored SCN rather than re-evaluating `startup.mode`. That matches the error you saw: the old job keeps trying to resume from a stale SCN after the upstream OGG / mirror rebuild. So, from the evidence in this thread, I still do not see proof that SeaTunnel moved the SCN backward by itself. The stronger explanation is: 1. the original streaming job kept an old checkpointed SCN; 2. after the upstream mirror / OGG path was rebuilt, that saved resume point was no longer a valid place to continue from; 3. recreating the job as a new sync task was the correct recovery step, because that clears the old restored offset path. The most important remaining check is: does the newly created job run normally on the rebuilt mirror, or does it still repeat / fail from a fresh job with no restored state? If the fresh job is healthy, this issue is much closer to an expected recovery-after-upstream-reset case than to a SeaTunnel product bug. If you continue investigating, please add: 1. whether the newly created job after August 27, 2026 runs normally or still duplicates / fails; 2. if it still fails, the new failing log from that fresh job, not the old restored one; 3. whether any old checkpoint/savepoint directory was reused when the job was recreated. One more note: if the `password` values in the pasted config are real rather than placeholders, please rotate and redact them from the issue. -- 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]
