Details
-
Bug
-
Resolution: Done
-
Major
-
1.7.0.Final
-
None
-
False
-
False
Description
When running the Oracle connector after a while (12-16 hours) it stops unexpectedly with ORA-00310 error. Until then it streams perfectly fine with a LagFromSource of ~3-6 seconds.
We are running Oracle 12c (12.2.0.1.181016) with 2 node (RAC), one thread per instance as well as 5 groups per instance (10 in total).
Caused by: java.sql.SQLException: ORA-00310: archived log contains sequence 67140; sequence 67135 required at java.base/java.lang.Thread.run(Thread.java:829) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:127) at io.debezium.pipeline.ChangeEventSourceCoordinator.streamEvents(ChangeEventSourceCoordinator.java:166) at io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource.execute(LogMinerStreamingChangeEventSource.java:54) at io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource.execute(LogMinerStreamingChangeEventSource.java:175) at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:42) org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped.
The connector is configurated as follows:
snapshot.locking.mode=shared connector.class=io.debezium.connector.oracle.OracleConnector consumer.session.timeout.ms=60000 max.queue.size=8096 tasks.max=1 database.history.kafka.topic=schema-changes.lus consumer.max.poll.interval.ms=90000 log.mining.strategy=online_catalog decimal.handling.mode=double oracle.jdbc.useFetchSizeWithLongColumn=true lob.enabled=false database.history.skip.unparseable.ddl=true snapshot.fetch.size=1000 database.user=fbilogminer database.dbname=datadb database.connection.adapter=logminer database.history.kafka.bootstrap.servers=kafka:9092 database.url=jdbc:oracle:thin:@dbserver.company.local:1521/DBSERVER.COMPANY.LOCAL database.server.name=dbserver heartbeat.interval.ms=10000 database.password=xxx max.batch.size=1024 table.include.list=TABLE1,TABLE2,...,TABLE120 snapshot.mode=schema_only
Attachments
Issue Links
- is related to
-
DBZ-2458 Re-evaluate log switch logic for Log Miner implementation
-
- Closed
-
