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

ParsingException: DDL statement couldn't be parsed

    XMLWordPrintable

Details

    • False
    • False
    • Hide

       
       
       
      debezium.source.database.history.skip.unparseable.ddl=true

      debezium.source.max.queue.size=10000
      debezium.source.max.batch.size=200
      debezium.source.poll.interval.ms=3

      debezium.source.snapshot.fetch.size=5000
      debezium.source.offset.flush.interval.ms=5000

      debezium.source.log.mining.batch.size.min=5
      debezium.source.log.mining.batch.size.max=300000
      debezium.source.log.mining.batch.size.default=100
      debezium.source.log.mining.sleep.time.min.ms=20
      debezium.source.log.mining.sleep.time.max.ms=300
      debezium.source.log.mining.sleep.time.default.ms=50
      debezium.source.log.mining.view.fetch.size=300000

      debezium.source.key.converter.schemas.enable=false
      debezium.source.value.converter.schemas.enable=false
      debezium.source.decimal.handling.mode=double

      debezium.source.database.history=io.debezium.relational.history.FileDatabaseHistory
      debezium.source.database.history.file.filename=data/history.dat
       
       

      Debezium Server: 1.7.1.Final

      Oracle: 12.1.0.2.0

       

      Run REBUILD INDEX

       

       

      Show
            debezium.source.database.history.skip.unparseable.ddl=true debezium.source.max.queue.size=10000 debezium.source.max.batch.size=200 debezium.source.poll.interval.ms=3 debezium.source.snapshot.fetch.size=5000 debezium.source.offset.flush.interval.ms=5000 debezium.source.log.mining.batch.size.min=5 debezium.source.log.mining.batch.size.max=300000 debezium.source.log.mining.batch.size.default=100 debezium.source.log.mining.sleep.time.min.ms=20 debezium.source.log.mining.sleep.time.max.ms=300 debezium.source.log.mining.sleep.time.default.ms=50 debezium.source.log.mining.view.fetch.size=300000 debezium.source.key.converter.schemas.enable=false debezium.source.value.converter.schemas.enable=false debezium.source.decimal.handling.mode=double debezium.source.database.history=io.debezium.relational.history.FileDatabaseHistory debezium.source.database.history.file.filename=data/history.dat     Debezium Server: 1.7.1.Final Oracle: 12.1.0.2.0   Run REBUILD INDEX    

    Description

      Oracle Session UGA 16.15MB (max = 29.89MB), PGA 431.35MB (max = 463.29MB)

      >>>>

      Ignoring unparsable DDL statement 'alter table SYSTEM.LOGMNR_KOPM$ modify partition P137 REBUILD UNUSABLE LOCAL INDEXES;': {}: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'alter table SYSTEM.LOGMNR_KOPM$ modify partition P137 REBUILD UNUSABLE LOCAL INDEXES;'
      mismatched input 'REBUILD' expecting {'ADD', 'DROP'}

       

      Getting this error, seems that debezium doesn't not support rebuilding indexes?

       

       

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. DBZ-4414 DDL statement issue with LogMiner

          • 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

              anmohant Anisha Mohanty
              bubbbajoe Joe Williams (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: