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

Oracle Connector(Using Logminer) with Oracle RDS (v12) does not capture changes

    XMLWordPrintable

Details

    Description

      Trying to test the oracle connector with the AWS RDS version of Oracle.

      Everything works fine when debezium is taking the initial snapshot of the table. But whenever new records get inserted, the changes are not streaming to the kafka topic. After a pretty long delay (~20mins or so) this shows up in the logs:

      2020-11-12 03:30:18,713 WARN   ||  All transactions with first SCN <= 577584 will be abandoned, offset: 576745   [io.debezium.connector.oracle.logminer.LogMinerHelper]
2020-11-12 03:30:18,713 WARN   ||  Following long running transaction 09000F0095010000 will be abandoned and ignored: Transaction{firstScn=576785, lastScn=576785, redoSqls=[[insert into "ADMIN"."CUSTOMERS"("ID","FIRST_NAME","SALARY") values ('4','tammy','900');]]}    [io.debezium.connector.oracle.logminer.LogMinerHelper]
2020-11-12 03:30:18,714 WARN   ||  Following long running transaction 0800210083010000 will be abandoned and ignored: Transaction{firstScn=576748, lastScn=576748, redoSqls=[[insert into "ADMIN"."CUSTOMERS"("ID","FIRST_NAME","SALARY") values ('3','timmo','600');]]}    [io.debezium.connector.oracle.logminer.LogMinerHelper]
2020-11-12 03:30:18,714 WARN   ||  Following long running transaction 09001B0094010000 will be abandoned and ignored: Transaction{firstScn=576826, lastScn=576826, redoSqls=[[insert into "ADMIN"."CUSTOMERS"("ID","FIRST_NAME","SALARY") values ('5','cardi b','1000');]]}    [io.debezium.connector.oracle.logminer.LogMinerHelper]

      Not sure if this is linked to the fact that the oracle connector requires the oracle database to have 2 log files per group, because this is not possible in RDS Oracle.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. DBZ-2759 long running transaction will be abandoned and ignored

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ccranfor@redhat.com Chris Cranford
              mngeow Marcus ngeow (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: