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.5.0.Beta1

What is the connector configuration?

curl -X POST http://localhost:8082/connectors -H "Content-Type: application/json" -d '{
    "name": "14debezium_prod_used_source19", 
    "config":

{      "connector.class" : "io.debezium.connector.oracle.OracleConnector",      "tasks.max" : "1",      "database.dbname": "dbprod",      "database.hostname": "db_ip",      "database.port": "1521",      "database.user": "iotcdc",      "database.password": "the_pass_word",      "topic.prefix": "14DEBEZIUM12",      "table.include.list": "cm_acmu_hist",      "schema.history.internal.kafka.bootstrap.servers" : "172.27.102.15:9092,172.27.102.16:9092,172.27.102.17:9092",      "schema.history.internal.kafka.topic": "14debezium-schema-changes12",      "message.key.columns": "cm_acmu_hist:acct_id;cm_acmu_hist:sa_id",      "snapshot.mode":"schema_only",      "snapshot.max.threads": "8",      "log.mining.strategy": "online_catalog",      "log.mining.username.include.list":"dbowner",      "schema.include.list":"dbowner",      "schema.history.internal.store.only.captured.tables.ddl": true,      "schema.history.internal.store.only.captured.databases.ddl": true,      "log.mining.query.filter.mode": "in",      "log.mining.batch.size.min": 5000,      "log.mining.batch.size.max": 200000,      "log.mining.batch.size.default": 50000,      "log.mining.sleep.time.min.ms": 0,      "log.mining.sleep.time.max.ms": 1000,      "log.mining.sleep.time.default.ms": 500,      "log.mining.sleep.time.increment.ms": 500,      "log.mining.transaction.retention.ms": 3600000   }

}'

What is the captured database version and mode of depoyment? 

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

RAC, with two nodes instances.

What behaviour do you expect?

Connector can be added and run 

What behaviour do you see?

Pls refer to the attachement.

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

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

Yes, I'm using the latest Beta version.

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

Yes, as attached.

How to reproduce the issue using our tutorial deployment?

Should be connecting to a Oracle 11g RAC db.

Feature request or enhancement

The code that check the oracle version should be change to comply with Oracle 11g.

in 2.5.0.Beta1,
private final static Pattern VERSION_PATTERN = Pattern
.compile("Oracle Database.
nVersion ([0-9])\\.([0-9])\\.([0-9])\\.([0-9])
.([0-9])");

it does not comply with "Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production"

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

The 2.5.0 version of plugins can be used with Oracle 11g

Implementation ideas (optional)

<Your answer>