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-connector-oracle 2.3

What is the connector configuration?

interval.handling.mode=string

What is the captured database version and mode of depoyment?

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

Oracle 19c

What behaviour do you expect?

For "INTERVAL '-7 5:12:10.0123' DAY TO SECOND", got error second value in the string

What behaviour do you see?

Got error value: "P0Y0M-7DT-5H-12M-9.9877S"

Do you see the same behaviour using the latest relesead 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)

<Your answer>

How to reproduce the issue using our tutorial deployment?

<Your answer>

Feature request or enhancement

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

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

<Your answer>

Implementation ideas (optional)

debezium-connector-oracle/src/main/java/io/debezium/connector/oracle/OracleValueConverters.java:749, should be: 
double seconds = sign * ((double) (Integer.parseInt(m.group(5)))
+ (double) Integer.parseInt(Strings.pad(m.group(6), 6, '0')) / 1_000_000D);
?