Regression in 3.4.1.Final: ORA-00933 in LogFileCollector due to missing space in SQL concatenation

[Renan Rocha]

Hi Debezium Team,

I've recently updated my Debezium Oracle Source Connector (LogMiner) from version 3.4.0.Final to 3.4.1.Final and encountered a SQL syntax error that seems to be a regression.

The connector fails to start with the following error: io.debezium.DebeziumException: Redo thread 1 is inconsistent; ORA-00933: SQL command not properly ended

Analysis: Looking at the logs, the generated SQL has a missing space between DS.DEST_ID and the AND operator: ... WHERE A.DEST_ID = DS.DEST_IDAND DS.DEST_NAME = 'LOG_ARCHIVE_DEST_1' ...

It appears that the class io.debezium.connector.oracle.logminer.LogFileCollector, specifically in the getAllRedoThreadArchiveLogs method, is concatenating the strings incorrectly when the property log.mining.archive.destination.name is provided.

Environment:

• Debezium Version: 3.4.1.Final

• Connector: Oracle Source (LogMiner)

• Oracle Version: 19c

• Configuration: log.mining.archive.destination.name is set to 'LOG_ARCHIVE_DEST_1'

Relevant Stack trace snippet:

Plaintext

Jan 29 01:37:15 prd-dbz1 connect-distributed.sh[2334150]: Caused by: Error : 933, Position : 168, Sql = SELECT A.NAME, A.SEQUENCE#, A.FIRST_CHANGE#, A.NEXT_CHANGE#, DS.DEST_NAME FROM V$ARCHIVED_LOG A, V$DATABASE D, V$ARCHIVE_DEST_STATUS DS WHERE A.DEST_ID = DS.DEST_IDAND DS.DEST_NAME = 'LOG_ARCHIVE_DEST_1' AND A.STATUS='A' AND A.THREAD#=1 AND A.RESETLOGS_CHANGE# = D.RESETLOGS_CHANGE# AND A.RESETLOGS_TIME = D.RESETLOGS_TIME ORDER BY A.SEQUENCE# DESC Jan 29 01:37:15 prd-dbz1 connect-distributed.sh[2334150]: at io.debezium.connector.oracle.logminer.LogFileCollector.getAllRedoThreadArchiveLogs(LogFileCollector.java:515)

SQL command not properly ended
Query: SELECT A.NAME, A.SEQUENCE#, A.FIRST_CHANGE#, A.NEXT_CHANGE#, DS.DEST_NAME
FROM V$ARCHIVED_LOG A, V$DATABASE D, V$ARCHIVE_DEST_STATUS DS
WHERE A.DEST_ID = DS.DEST_IDAND DS.DEST_NAME = 'LOG_ARCHIVE_DEST_1'...

It appears this behavior started after the update, as I hadn't encountered it in version 3.4.0.Final. Do you think this could be a regression, or is there something I should adjust in my configuration for 3.4.1?

Best regards, Renan Rocha

[Chris Cranford]

Hi -

This was identified, and will be fixed in 3.4.2. Thanks for the report.

-cc

--
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 visit https://groups.google.com/d/msgid/debezium/c3f79e81-a19d-49bd-8bef-e74d789ddf57n%40googlegroups.com.

[Renan Rocha]

Thanks for the quick confirmation, Chris! Looking forward to the 3.4.2 release. 

Best regards.