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

Commit SCN is having Thread 0 details which is non existing

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • None
    • oracle-connector
    • None
    • 3
    • False
    • None
    • False

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

      Bug report

      For bug reports, provide this information, please:

      What Debezium connector do you use and what version?

      2.6.2.Final

      What is the connector configuration?

      NA

      What is the captured database version and mode of deployment?

      Oracle 12 c, schema_only mode and with log miner as hybrid.

      What behavior do you expect?

      COMMIT_SCN should have only one thread and one transaction details to be included in the topic. What we can see is information of Thread #0 which is an invalid thread. We couldn't be able to find the SCN 30060242016 anywhere.

      {"commit_scn":"30060242016:0:0b000f00249bdc00-0c001c009d57d500,30132873739:1:1000110028aeca00","scn":"30132873738"}

      As we cannot see any such Thread active with 0.

      What behavior do you see?

      More details can be found in the discussion

      https://debezium.zulipchat.com/#narrow/channel/348250-community-oracle/topic/How.20to.20reset.20offset.20to.20an.20offset.20which.20we.20provide.3F

       

              ccranfor@redhat.com Chris Cranford
              ranjit.norman Ranjit Norman
              Chris Cranford
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: