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?

Oracle Connector, 3.0.7.Final

What is the connector configuration?

{
  "name": "foobar-prod-producer",
  "config":

{     "connector.class": "io.debezium.connector.oracle.OracleConnector",     "tasks.max": "1",     "signal.enabled.channels": "file",     "log.mining.strategy": "online_catalog",     "schema.history.internal.store.only.captured.tables.ddl": "true",     "topic.prefix": "foobar-prod",     "schema.history.internal.kafka.topic": "foobar-prod_schema_history",     "database.history.skip.unparseable.ddl": "true",     "snapshot.fetch.size": "10000",     "errors.retry.timeout": "-1",     "database.user": "c##dbzuser",     "database.dbname": "barfoo_PROD_DU",     "database.time_zone": "Europe/Berlin",     "database.pdb.name": "barfoo_PDB1",     "database.connection.adapter": "logminer",     "signal.file": "/home/barfoo/kafka/signals/foobar-prod.signal",     "database.url": "jdbc:oracle:thin:@//pldbsrv:1521/barfoo_pdb1.foobar.abc.oraclevcn.com",     "errors.retry.delay.max.ms": "30000",     "schema.history.internal.kafka.bootstrap.servers": "pl-kafka-dwh.barfoo.cloud:9094",     "column.exclude.list": "",     "database.password": "***censored***",     "name": "foobar-prod-producer",     "errors.tolerance": "none",     "table.include.list": "barfoo_prod_du.anmeld,barfoo_prod_du.artikel,barfoo_prod_du.artme,barfoo_prod_du.bestand,barfoo_prod_du.bestell_kopf,barfoo_prod_du.bestell_pos,barfoo_prod_du.bestjour,barfoo_prod_du.commission_interrupt,barfoo_prod_du.drucken,barfoo_prod_du.fahr_pos,barfoo_prod_du.fahrzeug,barfoo_prod_du.festplatz,barfoo_prod_du.fkt_kopf,barfoo_prod_du.invauftrag,barfoo_prod_du.invergebnis,barfoo_prod_du.kunde,barfoo_prod_du.knz_arbeitszeit,barfoo_prod_du.knz_kom,barfoo_prod_du.knz_lagerplatzauslastung,barfoo_prod_du.knz_transporte,barfoo_prod_du.knz_wa,barfoo_prod_du.knz_we,barfoo_prod_du.komm_gruppe,barfoo_prod_du.lhm_typ,barfoo_prod_du.lhm_typ_modul,barfoo_prod_du.lieferantenbewertung,barfoo_prod_du.mandanten,barfoo_prod_du.mde,barfoo_prod_du.mde_kopf,barfoo_prod_du.mde_pos,barfoo_prod_du.mm_grund,barfoo_prod_du.modul,barfoo_prod_du.palette,barfoo_prod_du.personal,barfoo_prod_du.platz,barfoo_prod_du.platz_art,barfoo_prod_du.pminder,barfoo_prod_du.pnull,barfoo_prod_du.prot_anmeld,barfoo_prod_du.puthost,barfoo_prod_du.smde,barfoo_prod_du.sperr_typ,barfoo_prod_du.spersonal,barfoo_prod_du.tbereich,barfoo_prod_du.tourkopf,barfoo_prod_du.tpa,barfoo_prod_du.versandart,barfoo_prod_du.vorgang,barfoo_prod_du.wa_kopf,barfoo_prod_du.wa_pos,barfoo_prod_du.we_auftragsart,barfoo_prod_du.we_kopf,barfoo_prod_du.we_pos,barfoo_prod_du.we_pos_nve,barfoo_prod_du.zielplatztausch_historie,barfoo_prod_du.zust_typ,barfoo_prod_du.freight_payment_term",     "snapshot.mode": "initial"   }

,
  "tasks": [
   

{       "connector": "foobar-prod-producer",       "task": 0     }

  ],
  "type": "source"
}

What is the captured database version and mode of deployment?

Oracle Database CDB/PDB, deployed in Oracle Cloud, Version 19.25.0.0.0

What behavior do you expect?

ALTER TABLE should not break the conenctor

What behavior do you see?

Mining session stopped due to error

Do you see the same behaviour using the latest released Debezium version?

tested with 3.0.7 Final

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

Please find the log attached: 2025-02-21_connect.log

How to reproduce the issue using our tutorial deployment?

?

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

user/customer should be able to use ALTER TABLE without breaking the log mining process

Implementation ideas (optional)

—