-
Bug
-
Resolution: Done
-
Blocker
-
1.5.0.Final, 1.6.0.Beta1
-
None
-
False
-
False
-
Undefined
-
-
Issue: Using debezium oracle connector with logminer for XML_TYPE column retrives only data from snapshot, during replication XML_TYPE column is null (other columns are fine)
Environment:
DB host: Oracle linux 7
DB version: Oracle 19c
Oracle connector: 1.6 Beta and 1.5 Final | using LogMiner
Debezium on classic kafka and kafka connect
Expected result:
Retrive XML_TYPE data in snpashot and during replication
Actual result:
Using snapshot everything works fine, during replication XML_TYPE columns are nulls
Some investigation on this issue:
Investigation can be found in my conversation with ccranfor@redhat.com under this thread.
- account is impacted by
-
DBZ-6224 ExtractNewDocumentState.apply() throw exception
- Closed
- is duplicated by
-
DBZ-3782 Oracle Logminer ParserDML - Statement couldn't be parsed for XMLType
- Closed
-
DBZ-4476 XMLTYPE field is always coming null
- Closed
-
DBZ-6098 Connector captures update events on XMLTYPE column in some tables and dosen't work on others
- Closed
- is related to
-
DBZ-5337 Oracle XMLTYPE tables are not supported
- Pull Request Sent
-
DBZ-3782 Oracle Logminer ParserDML - Statement couldn't be parsed for XMLType
- Closed
-
DBZ-6782 Oracle XML column types are not properly resolved when adding XMLTYPE column during streaming
- Closed
-
DBZ-1550 Add Oracle JDBC driver to distribution package if possible
- Closed
-
DBZ-6676 Update documentation on XML and RAW data types
- Closed
-
DBZ-6859 Oracle connector test suite logging no longer works
- Closed
-
DBZ-5441 Unsupported non-relational tables should be gracefully skipped by the connector during streaming
- Closed
- links to
-
RHEA-2024:129636 Red Hat build of Debezium 2.5.4 release