Redpanda Connect v4.103.1 - LogMiner Query Debug Logging

Redpanda Connect v4.103.1 was published on July 31, 2026. The release adds an additional debug log for LogMiner queries in the oracledb_cdc input, a narrow observability change for Oracle CDC diagnosis. It is a stable release, not a prerelease.

The full release notes and downloads are on the GitHub release page.

The only documented code change is an additional debug log for LogMiner queries in oracledb_cdc. The change is tracked in pull request 4653. No other connector additions, fixes, or behavior changes appear in the notes.

That narrow scope matters. A new diagnostic message can expose more of the query activity used by the Oracle CDC input, but the release notes do not say that query construction, execution, decoding, or checkpoint behavior changed. This should be treated as an observability update, not as evidence of a CDC correctness or performance fix.

The notes also do not document the exact message format or the fields written by the new log statement. They do not promise query text, parameters, elapsed time, result counts, or Oracle error details. Operators should confirm what the message contains in a test environment before building searches, alerts, or incident procedures around it.

For an Oracle capture pipeline, the added output provides another point of evidence around the LogMiner query stage. During an incident, that may help an operator determine whether the connector is reaching that stage and correlate its activity with Oracle logs and database observations. That is an operational inference from the purpose of the debug message, not a capability guaranteed by the release notes.

Use the extra logging deliberately. Capture a bounded diagnostic interval, preserve the connector logs with the relevant database timeline, then return logging to its normal level. Debug output can increase log volume and storage pressure, while the release notes provide no measurements for the size or frequency of this message.

Existing log pipelines may also need a small validation pass. Check that the new entry is retained, parsed, and searchable under the current log policy. Avoid depending on an assumed field layout because none is specified in the release notes. If the message includes sensitive query context, existing access and retention controls should govern it just like other connector debug data. The notes do not state whether such context is present, so this is a verification item rather than a claimed release property.

v4.103.1 is not marked as a prerelease. The published notes list no breaking changes, migration steps, configuration key changes, or altered defaults. They also contain no security advisory. On the available evidence, this is a small diagnostic release with one listed addition.

The scope cuts both ways. Teams investigating oracledb_cdc behavior have a concrete reason to evaluate it. Teams that do not use that input receive no documented functional change from this release. A normal staging check should focus on connector startup, expected CDC progress, log volume, and whether the added output supplies useful incident context.

Do not turn sparse notes into a larger claim. The release does not document faster mining, lower database load, broader Oracle compatibility, or repaired event delivery. The additional log may improve the evidence available during diagnosis, but it does not by itself change the health of the pipeline.