-
Bug
-
Resolution: Done
-
Critical
-
1.9.5.Final, 2.0.0.Alpha3
-
None
-
False
-
None
-
False
In order to reproduce this issue, the connector must run indefinitely capturing changes for a table that does not change frequently. The offset SCN will not be advanced on transaction commits because the commit handler is never fired if the transaction consists of 0 events because they were all filtered out.
A transaction commit should always attempt to advance both the offset SCN (low watermark) and the commit SCN (high watermark) values.
- causes
-
DBZ-4718 ORA-00308 raised due to offset SCN not being updated in a low traffic environment
- Closed
-
DBZ-4907 Oracle keeps trying old scn even if it had no changes
- Closed
- links to
-
RHEA-2023:120698 Red Hat build of Debezium 2.3.4 release