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 ( log miner extract )

What is the connector configuration?

Using specific tables and message.key.columns, log miner configured 

What is the captured database version and mode of deployment?

on premise

What behavior do you expect?

Will be very helpful to have option to start extract using option start_scn to point on a specific SCN on database. Very helpful instead signal table

What behavior do you see?

For Oracle connector the start_scn option to have option for entire extract instead using signal table 

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

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

Not implemented on 3.4 version

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

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

not the case 

How to reproduce the issue using our tutorial deployment?

Not case 

Feature request or enhancement

Feature 

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

Start extract on Oracle database from a speficic scn 

Implementation ideas (optional)

<Your answer>