-
Bug
-
Resolution: Done
-
Critical
-
1.9.3.Final
-
None
-
False
-
None
-
False
Bug report
For bug reports, provide this information, please:
The connector throws exception:
io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'alter table mesg_perf_stat TRUNCATE PARTITION SYS_P6300108 DROP STORAGE CASCADE UPDATE INDEXES;'
mismatched input 'DROP' expecting {'DISABLE', 'ENABLE', ';'}
What Debezium connector do you use and what version?
1.9.3.Final
What is the connector configuration?
{
"name": "debezium-t3-boff-connector",
"config": {
"connector.class" : "io.debezium.connector.oracle.OracleConnector",
"tasks.max" : "1",
"database.server.name" : "NAME",
"database.dbname": "db_name",
"database.url": "jdbc",
"database.user" : "t3_db_user_boff",
"database.password" : "t3_db_pwd_boff",
"database.connection.adapter" : "logminer",
"log.mining.strategy": "online_catalog",
"database.history.kafka.bootstrap.servers" : "kafka:9092",
"database.history.kafka.topic": "t3.db.history-changes",
"snapshot.mode": "schema_only",
"table.include.list": "TABLE1, TABLE2, TABLE3",
"decimal.handling.mode": "string",
"log.mining.batch.size.default": "100000"
}
}
What is the captured database version and mode of depoyment?
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.13.0.0.0
What behaviour do you expect?
no errors
What behaviour do you see?
errors in logs - connector stops
Do you see the same behaviour using the latest relesead Debezium version?
yes