Troubleshooting

The following troubleshooting tips might help you to resolve issues with this Micro-Integration. If problems persist, contact Solace.

Connection Fails After Configuring Client Certificate Authentication

Check the following:

  • Verify that the database URL uses the TCPS protocol and port 2484 (the default TLS port), not the standard Oracle listener port (1521).

  • Verify that the truststore and keystore files are in JKS or PKCS12 format.

  • If configuring mTLS, confirm that your Oracle Wallet is a custom wallet. Auto-managed wallets (such as OCI-managed wallets) do not support mTLS.

  • Verify that the paths to the truststore and keystore files are accessible from the location where the connector runs. In containerized deployments, ensure the directory containing the files is mounted into the container.

CDC Events Are Missing Column Values

If CDC events are missing values for one or more columns, verify that supplemental logging is enabled at both the database level and the table level. Without supplemental logging, LogMiner cannot capture the before and after values of individual columns. For setup instructions, see the Oracle Database Prerequisites section.

LOB Column Values Are Missing or Messages Are Too Large

Check the following:

  • If LOB fields (BLOB, CLOB, or XMLTYPE) appear as null or unavailable in CDC events, verify that lobEnabled is set to true in the consumer configuration.

  • If messages are too large or fail to publish because of LOB column data, use columnExcludeList to exclude the large LOB columns that are not needed downstream.

Column Names Have Unexpected Case in CDC Events

If downstream consumers cannot find columns by name, verify how the column was created in Oracle. Nonquoted identifiers are stored and emitted in uppercase (for example, COLUMN_NAME), while quoted identifiers preserve the original case (for example, column_name). Update your downstream mapping to match the case used in CDC events.