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?

Debezium Oracle Connector 2.4.0

What is the connector configuration?

    "connector.class" : "io.debezium.connector.oracle.OracleConnector",
        "database.connection.adapter" : "xstream",
        "tasks.max" : "1",
        "topic.prefix" : "ESPP_fact",
        "database.url" : "jdbc:oracle:oci:@host:1521/service",
        "database.user" : "USER",
        "database.password" : "PASSWORD",
        "database.dbname" : "DBNAME",
        "database.pdb.name" : "PDBNAME",
        "table.include.list" : "ESPP.T_BUSINESS_OPERATION",
        "schema.history.internal.kafka.bootstrap.servers" : "192.168.0.10:9092",
        "schema.history.internal.kafka.topic": "schema-changes.inventory",
        "database.out.server.name" : "DBZ_XOUT",
        "snapshot.mode" : "schema_only",
        "time.precision.mode" : "connect",
        "tombstones.on.delete":"true",
        "provide.transaction.metadata":"true",
        "decimal.handling.mode":"double"

What is the captured database version and mode of depoyment?

Oracle 19.20 standalone

What behaviour do you expect?

The connector should capture the DDL

What behaviour do you see?

The connector stops working not being able to capture the DDL-

Producer failure (io.debezium.pipeline.ErrorHandler:52)
io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement '

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

Yes I do see the same behaviour using 2.5CR1( also tried 2.4.1)

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

Yes I have plz  see  attacment