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 2.1.4.Final

What is the connector configuration?

Logminer mode

What is the captured database version and mode of depoyment?

19c, pluggable database

What behaviour do you expect?

Parsing DDL statements correctly.

What behaviour do you see?

Stacktrace with the following statement:

org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped.

...

Caused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'DROP TABLE TABLENAME;'
extraneous input 'FORCE' expecting {'AS', 'CASCADE', 'PURGE', ';'}

...

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

Can't tell. Only seen on 2.1.4.Final.

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

no

How to reproduce the issue using our tutorial deployment?

I guess, running the connector and executing the above statement.