-
Bug
-
Resolution: Done
-
Major
-
2.6.0.Final
-
None
What Debezium connector do you use and what version?
Debezium Oracle 2.6.Final
What is the connector configuration?
"database.hostname": "vip-primary-asex92",
"database.port": "1521",
"database.user": "dbzusr",
"database.password": "pwd",
"database.dbname": "CASEX92A",
"database.pdb.name": "ASEX92A",
"topic.prefix": "ASE1",
"table.include.list": "ASEDBUSR.ABRDVRS,ASEDBUSR.ABRDVRSUNT",
"snapshot.select.statement.overrides": "ASEDBUSR.ABRDVRS,ASEDBUSR.ABRDVRSUNT",
"snapshot.select.statement.overrides.ASEDBUSR.ABRDVRS": "SELECT * FROM ASEDBUSR.ABRDVRS WHERE TO_CHAR(REPLACED,'YYYYMMDD') > TO_CHAR(sysdate-7,'YYYYMMDD') ORDER BY CREATED ASC, PKEY ASC",
"snapshot.select.statement.overrides.ASEDBUSR.ABRDVRSUNT": "SELECT * FROM ASEDBUSR.ABRDVRSUNT WHERE TO_CHAR(REPLACED,'YYYYMMDD') > TO_CHAR(sysdate-7,'YYYYMMDD') ORDER BY CREATED ASC, PKEY ASC",
"snapshot.fetch.size": "10000",
"snapshot.max.threads": 2,
"signal.data.collection": "CASEX92A.dbzusr.DEBEZIUM_SIGNAL",
What is the captured database version and mode of depoyment?
Oracle 19c PDB
What behaviour do you expect?
The signaling data collection shouldn't be included in the snapshot process.
What behaviour do you see?
The signaling data collection is included in the snapshot process.
Do you have the connector logs, ideally from start till finish?
Database table 'ASEX92A.dbzusr.DEBEZIUM_SIGNAL' not configured with supplemental logging "(ALL) COLUMNS"; only explicitly changed columns will be captured. Use: ALTER TABLE dbzusr.DEBEZIUM_SIGNAL ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS
-> Is it really necessary to add supplemental logging for this table?
Only captured tables schema should be captured, capturing: [ASEX92A.ASEDBUSR.ABRDVRS, ASEX92A.ASEDBUSR.ABRDVRSUNT, ASEX92A.dbzusr.DEBEZIUM_SIGNAL]
- links to
-
RHEA-2024:139598 Red Hat build of Debezium 2.5.4 release