Wrong topic name while setting up source connector against oracle 11g

123 views
Skip to first unread message

Hrishikesh Dutta Gupta

unread,
Apr 2, 2024, 2:42:22 PM4/2/24
to debezium
Hi,

  I am trying to setup debezium source connector against a oracle 11g DB server (Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production) and below is how my source json looks like, the source connector should fetch data changes from 3 tables(idctrd, idctrdleg and idccptytrd) to start with . Now I can see that the topic which is being created is 'testOracle' which I expected to be rather the individual table names. e.g idctrd, idctrdleg and idccptytrd as I am going to use these same names for the  debezium sink connector(given below) we use to push data to another oracle 11g instance. We have earlier used the same source and sink config  against a postgres source DB which has worked fine. 
Question is - how can I fix this from the source config  properties and are  there any other changes recommended here to work against a oracle 11g instance apart from what we have used ?   Thanks in advance.

Source config:

"connector.class": "io.debezium.connector.oracle.OracleConnector",
    "tasks.max": "1",
    "database.hostname": "*****",
    "database.port": "1521",
    "database.user": "**",
    "database.password": "**",
    "database.dbname": "**",
    "database.server.name": "**",
    "table.include.list": "idctrd,idctrdleg,idccptytrd",
    "topic.prefix": "testOracle",
    "schema.history.internal.kafka.bootstrap.servers" : "kafka:29092",
    "schema.history.internal.kafka.topic": "schema-changes.inventory",
    "transforms": "topicRename",
    "transforms.topicRename.type": "org.apache.kafka.connect.transforms.RegexRouter",
    "transforms.topicRename.regex": ".*\\.(.*)",
    "transforms.topicRename.replacement": "$1"

Sink config:

"connector.class": "io.debezium.connector.jdbc.JdbcSinkConnector",
    "tasks.max": "1",
    "connection.url": ****:1521/***",
    "connection.username": "***",
    "connection.password": "***",
    "topics": "idctrd,idctrdleg,idccptytrd",
    "schema.evolution": "basic",
    "quote.identifiers": "false",
    "insert.mode": "upsert",
    "primary.key.mode": "record_key",
    "primary.key.fields": "id"


Regards
 Hrishi

Chris Cranford

unread,
Apr 2, 2024, 3:20:05 PM4/2/24
to debe...@googlegroups.com
Hi,

So I think your issue is that you've misconfigured your "table.include.list" and you likely should have seen a warning in the logs that the filter configuration resulted in no tables being found, thus no data will be captured.  The "table.include.list" should be defined as a comma-separated list of "<schema>.<table>" elements.  So for example, in a tablespace/schema called "DEBEZIUM" and a table called "CUSTOMERS" and "ORDERS", the include list would be:

    "table.include.list": "DEBEZIUM.CUSTOMERS,DEBEZIUM.ORDERS"

Give that a try and see if that solves the issue.

Thanks,
Chris
--
You received this message because you are subscribed to the Google Groups "debezium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debezium+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/05f0d9e7-2db5-40c2-8c66-53042f89bff7n%40googlegroups.com.

Hrishikesh Dutta Gupta

unread,
Apr 3, 2024, 12:40:30 AM4/3/24
to debezium
Hi Chris,

  Yes, actually I have tried with the mentioned option also(given below),here 'prodfxiapp2' is the schema name , but still the topic getting created is 'testOracle'.

"table.include.list": "prodfxiapp2.idctrd,prodfxiapp2.idctrdleg,prodfxiapp2.idccptytrd"

Regards
 Hrishi

Chris Cranford

unread,
Apr 3, 2024, 10:33:32 AM4/3/24
to debe...@googlegroups.com
Are you tables created using case sensitivity Hrishi where you need to use quotes in Oracle?

Chris

Chris Cranford

unread,
Apr 3, 2024, 10:34:37 AM4/3/24
to debe...@googlegroups.com
If you can enable TRACE logging and attach the connector's start-up logs so we can look, that may be the best way to determine the issue.
Reply all
Reply to author
Forward
0 new messages