Description
The following error might be observed on the Confluent Cloud UI for Oracle CDC Source connectors:
The connector could not produce change events because the redo log consumer(s) failed to subscribe to the redo log topic '<redo log topic name>'. Please make sure this redo log topic exists, and the task that reads the database redo log is able to produce to this topic.
Applies To
Confluent Cloud
Confluent Oracle CDC Source connector
Cause
This can occur if the connector cannot read from the redo log topic due to security being configured on the Kafka cluster
Resolution
If the redo log topic updates are not propagated to the table topic and security is enabled on the Kafka cluster, you must configure redo.log.consumer.* accordingly.
For example, if configuring an Oracle CDC Source Connector to send data to a Confluent Cloud cluster, the following properties can be configured:
redo.log.consumer.bootstrap.servers: "XXXXXXXX" ,
redo.log.consumer.security.protocol: "SASL_SSL" ,
redo.log.consumer.ssl.endpoint.identification.algorithm: "https" ,
redo.log.consumer.sasl.mechanism: "PLAIN" ,
redo.log.consumer.sasl.jaas.config: "org.apache.kafka.common.security.plain.PlainLoginModule required username='XXXXXXXXX' password='XXXXXXXXXX';"
These properties mimic those that would normally be configured for the Connect worker to connect to the cluster.
In the case of an SSL-secured (non-Confluent Cloud) cluster, the following properties could be used:
"redo.log.consumer.security.protocol": "SSL",
"redo.log.consumer.ssl.truststore.location": "<filepath>",
"redo.log.consumer.ssl.truststore.password": "<password>",
"redo.log.consumer.ssl.keystore.location": "<filepath>",
"redo.log.consumer.ssl.keystore.password": "<password>",
"redo.log.consumer.ssl.key.password": "<password>”,
"redo.log.consumer.ssl.truststore.type":"<type>",
"redo.log.consumer.ssl.keystore.type": "<type>",