Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-5266

No changes to commit_scn when oracle-connector got new lob data

    XMLWordPrintable

Details

    Description

      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Bug report

      When Oracle connector obtains new lob data, it does not make any changes to commit_scn

      What Debezium connector do you use and what version?

      oracle-connector

       

      What is the captured database version and mode of depoyment?

      oracle_19c

      What behaviour do you expect?

      when  insert some new lob-type data, i can see the new commit_scn in kafka topic

      What behaviour do you see?

       

      CreateTime:1655441784664        ["source-CJ_0101",{"server":"cj_server0101"}]     {"commit_scn":"2054923468","transaction_id":null,"snapshot_scn":"2054803212","scn":"2054923467"}
      CreateTime:1655451084712        ["source-CJ_0101",{"server":"cj_server0101"}]     {"commit_scn":"2054923468","transaction_id":null,"snapshot_scn":"2054803212","scn":"2054983937"}
      CreateTime:1655451144714        ["source-CJ_0101",{"server":"cj_server0101"}]     {"commit_scn":"2054923468","transaction_id":null,"snapshot_scn":"2054803212","scn":"2054986353"}
      CreateTime:1655451204715        ["source-CJ_0101",{"server":"cj_server0101"}]     {"commit_scn":"2054923468","transaction_id":null,"snapshot_scn":"2054803212","scn":"2054986525"}
      CreateTime:1655451264717        ["source-CJ_0101",{"server":"cj_server0101"}]     {"commit_scn":"2054923468","transaction_id":null,"snapshot_scn":"2054803212","scn":"2054987145"} 

       

       

      Do you see the same behaviour using the latest relesead Debezium version?

      (Ideally, also verify with latest Alpha/Beta/CR version)

      also in V2.0 

       

      How to reproduce the issue using our tutorial deployment?

      just insert lob-type data

      Implementation ideas (optional)

      You can see a function named "handlecommit (oraclepartition partition, logminereventrow)" in AbstractLogMinerEventProcessor.java

      if (--numEvents == 0) {
          // reached the last event update the commit scn in the offsets
          offsetContext.setCommitScn(commitScn);
      }  

      if you have events type is "EventType.LOB_WRITE", you will merge those events to the previous dml-event, so "--numEvents == 0" always is false ,you can't push any  commit_scn to kafka !!

      Attachments

        Activity

          People

            ccranfor@redhat.com Chris Cranford
            udontknow C J (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: