-
Bug
-
Resolution: Done
-
Major
-
1.8.0.Final
-
None
-
False
-
None
-
False
I've came across three cases of SQL exceptions which broke the mining session. So I create one Jira for them.
(1) 0312_dbz_ORA-00310.log
java.sql.SQLException: ORA-00310: archived log contains sequence 43238; sequence 43234 required
This is with configuration "log.mining.strategy=online_catalog"
(2) 0312_dbz_ORA-01343.log
java.sql.SQLException: ORA-01343: LogMiner encountered corruption in the logstream
This is with configuration "log.mining.strategy=redo_log_catalog".
(3) 0314_dbz_ORA-01371.log
java.sql.SQLException: ORA-01371: Complete LogMiner dictionary not found
This is with configuration "log.mining.strategy=redo_log_catalog"
All of them were resolved by relaunch Debezium (curl DELETE & curl POST).
- is cloned by
-
DBZ-4859 ORA-01291 happened many times
- Closed