I have meet an issue with Oracle debezium connector about DDL statement couldn't be parsed. Before I have used the parameter schema.history.internal.skip.unparseable.ddl=true for the hotfix it. Now if i use schema.history.internal.skip.unparseable.ddl, my connector will not be able to capture new tables.

 "ERROR Mining session stopped due to error. (io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource:220)
io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement '
CREATE TABLE "PROD"."CHANGESHIPMENTEVENT"
( "HJMPTS" NUMBER(20,0),
"CREATEDTS" TIMESTAMP (3),
"MODIFIEDTS" TIMESTAMP (3),
"TYPEPKSTRING" NUMBER(20,0),
"OWNERPKSTRING" NUMBER(20,0),
"PK" NUMBER(20,0) NOT NULL ENABLE,
"SEALED" NUMBER(1,0),
"P_EVENTDATE" TIMESTAMP (3),
"P_CURRENTSELFDELIVERY" VARCHAR2(255 CHAR) COLLATE "USING_NLS_COMP",
"P_NEWSELFDELIVERY" VARCHAR2(255 CHAR) COLLATE "USING_NLS_COMP",
"P_EVENTSOURCE" VARCHAR2(255 CHAR) COLLATE "USING_NLS_COMP",
"P_REASONCODE" VARCHAR2(255 CHAR) COLLATE "USING_NLS_COMP",
"P_REASONNAME" VARCHAR2(255 CHAR) COLLATE "USING_NLS_COMP",
"P_MODIFIEDUSER" VARCHAR2(255 CHAR) COLLATE "USING_NLS_COMP",
"P_EXTRANOTE" CLOB COLLATE "USING_NLS_COMP",
"P_SHIPMENT" NUMBER(20,0),
"ACLTS" NUMBER(20,0) DEFAULT 0,
"PROPTS" NUMBER(20,0) DEFAULT 0,
PRIMARY KEY ("PK")
USING INDEX ENABLE
) DEFAULT COLLATION "USING_NLS_COMP" ;'
mismatched input ',' expecting

at io.debezium.antlr.ParsingErrorListener.syntaxError(ParsingErrorListener.java:43)"