Bug report

What Debezium connector do you use and what version?

Oracle Connector and 1.9.4 Final

What is the connector configuration?

name=enquesta-connector
connector.class=io.debezium.connector.oracle.OracleConnector
tasks.max=1
database.server.name=cdc_test_db
database.hostname=ssi-dba-db02.ssivt.dev
database.port=1521
database.user=dbzuser
database.password=redacted
database.dbname=dckenq.dckenq
schema.include.list=CDC,DBZUSER
table.include.list=CDC.SAMPLE,DBZUSER.DEBEZIUM_SIGNAL
database.history.kafka.bootstrap.servers=ssi-dba-db02.ssivt.dev:9092
database.history.kafka.topic=schema-changes.inventory
internal.log.mining.query.logs.for.snapshot.offset=false
signal.data.collection=DCKENQ.DCKENQ.DBZUSER.DEBEZIUM_SIGNAL
value.converter.schemas.enable=false
key.converter.schemas.enable=false

What is the captured database version and mode of depoyment?

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
On-premise vm

What behaviour do you expect?

Only specified schemas and tables captured and schema excluded from messages

What behaviour do you see?

All non-system schemas and tables appear to be captured and schema is included in Json messages.

Do you see the same behaviour using the latest released Debezium version?

Yes

Do you have the connector logs, ideally from start till finish?

Yes, attached

How to reproduce the issue using our tutorial deployment?

Use my config against an Oracle DB with the identified schemas