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

Oracle connector continually logging warnings about already processed transactions.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.6.0.CR1
    • None
    • oracle-connector
    • None

      As discussed with ccranfor@redhat.com on Gitter, we are having the issue where we have stuck transactions on one of our databases that causes Debezium to refuse to write its offsets, which results into the following messages being logged thousands of times every second:

       

      [2021-06-10 09:02:56,999] WARN Transaction 27001800a7735b00 was already processed, ignore. Committed SCN in offset is null, commit SCN of the transaction is 14339381438415, last committed SCN is 14339381466543 (io.debezium.connector.oracle.logminer.LogMinerHelper:489)
       

       

      This was after a fresh snapshot of the database. There are two transactions that have been open for well over a week now. Obviously they should be killed, but we have no control over that.

      My understanding was is that there is currently no way to ignore transactions so this would effectively grind the CDC process to a halt since the offsets are not being committed to Kafka. Please correct me if I'm wrong

       

      I've attached a trace log of the whole thing on his request of Chris (712k log lines, so it's a big one!)

       

            ccranfor@redhat.com Chris Cranford
            jorn.argelo@mn.nl Jorn Argelo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: