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

Logminer mining session stopped due to several kinds of SQL exceptions


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.9.0.CR1
    • 1.8.0.Final
    • oracle-connector
    • None
    • False
    • None
    • False

      I've came across three cases of SQL exceptions which broke the mining session. So I create one Jira for them.

      (1) 0312_dbz_ORA-00310.log
      java.sql.SQLException: ORA-00310: archived log contains sequence 43238; sequence 43234 required
      This is with configuration "log.mining.strategy=online_catalog" 
      (2) 0312_dbz_ORA-01343.log
      java.sql.SQLException: ORA-01343: LogMiner encountered corruption in the logstream
      This is with configuration "log.mining.strategy=redo_log_catalog".
      (3) 0314_dbz_ORA-01371.log
      java.sql.SQLException: ORA-01371: Complete LogMiner dictionary not found
      This is with configuration "log.mining.strategy=redo_log_catalog"


      All of them were resolved by relaunch Debezium (curl DELETE & curl POST). 

        1. 0312_dbz_ORA-00310.log
          227 kB
        2. 0312_dbz_ORA-01343.log
          372 kB
        3. 0314_dbz_ORA-01371.log
          1.55 MB

            Unassigned Unassigned
            zouxinyu0328 Ethan Zou (Inactive)
            0 Vote for this issue
            4 Start watching this issue