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?

2.6, but this should also apply to 3.1.0.Final too

What is the connector configuration?

"snapshot.mode": "no_data"

What is the captured database version and mode of deployment?

(E.g. on-premises, with a specific cloud provider, etc.)

N/A

What behavior do you expect?

The connector should not fault

What behavior do you see?

The connector faults with this error message:

ORA-08186: invalid timestamp specified
ORA-06512: at "SYS.TIMESTAMP_TO_SCN", line 1 

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

(Ideally, also verify with latest Alpha/Beta/CR version)

Yes

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

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

N/A

How to reproduce the issue using our tutorial deployment?

The only way to reproduce this is to have a system with a very, very old LAST_DDL_TIME in the ALL_OBJECTS table that will cause the the following SQL query to fail:

SELECT TIMESTAMP_TO_SCN(MAX(last_ddl_time)) 
  FROM all_objects
 WHERE (owner ...)