Bug report

Caused by: io.debezium.DebeziumException: Archive log destination name '+ASMGROUP/DBNAME1/ARCHIVELOG' is unknown to Oracle

Above error appears on every of beneath listed configurations:

ASMGROUP

+ASMGROUP

+ASMGROUP/DBNAME1/ARCHIVELOG

+ASMGROUP/DBNAME1/ARCHIVELOG/2024_06_10

The permissions set on the destination are wide enough to enable connecting

What Debezium connector do you use and what version?

Oracle 2.5.4.Final

What is the connector configuration?

{
    "connector.class": "io.debezium.connector.oracle.OracleConnector",
    "database.dbname": "DBNAME1",
    "database.hostname": "hotname123.fc.com",
    "database.password": "***",
    "database.port": "1521",
    "database.url": "jdbc:oracle:thin:@//hotname123.fc.com:1521/dddd.q1.im.it.prd",
    "database.user": "USER_NAME",
    "driver.trustServerCertificate": "true",
    "errors.log.enable": "true",
    "errors.log.include.messages": "false",
    "include.schema.changes": "false",
    "key.converter": "io.confluent.connect.avro.AvroConverter",
    "key.converter.basic.auth.user.info": "",
    "key.converter.schema.registry.url": "https://redpanda-registry.messaging-redpanda.qat.gaincapital.cloud",
    "key.converter.schemas.enable": "true",
    "log.mining.archive.destination.name": "+ASMGROUP/DBNAME1/ARCHIVELOG",
    "name": "Avro_Debezium_Source_V1_TABLE1_test",
    "provide.transaction.metadata": "false",
    "schema.history.internal.consumer.sasl.jaas.config": "${env::CONNECT_SASL_JAAS_CONFIG}",
    "schema.history.internal.consumer.sasl.mechanism": "SCRAM-SHA-256",
    "schema.history.internal.consumer.security.protocol": "SASL_SSL",
    "schema.history.internal.consumer.ssl.endpoint.identification.algorithm": "https",
    "schema.history.internal.kafka.bootstrap.servers": "redpanda-bootstrap.messaging-redpanda.qat.gaincapital.cloud:9092",
    "schema.history.internal.kafka.topic": "_Stonex_Oracle_Test",
    "schema.history.internal.producer.sasl.jaas.config": "${env::CONNECT_SASL_JAAS_CONFIG}",
    "schema.history.internal.producer.sasl.mechanism": "SCRAM-SHA-256",
    "schema.history.internal.producer.security.protocol": "SASL_SSL",
    "schema.history.internal.producer.ssl.endpoint.identification.algorithm": "https",
    "schema.registry.url": "https://[messaging-redpanda.qat.gaincapital.cloud|https://redpanda-wholesale-us-registry.messaging-redpanda.some.cloud/]",
    "snapshot.fetch.size": "1000",
    "snapshot.mode": "schema_only",
    "ssl.endpoint.identification.algorithm": "https",
    "table.include.list": "SCHEMA.TABLE1",
    "tasks.max": "1",
    "tombstones.on.delete": "false",
    "topic.creation.default.cleanup.policy": "delete",
    "topic.creation.default.partitions": "1",
    "topic.creation.default.replication.factor": "3",
    "topic.creation.enable": "true",
    "topic.prefix": "hotname123",
    "transforms": "unwrap,route",
    "transforms.route.regex": "([^.]+)",
    "transforms.route.replacement": "TABLE1_test_data_topic",
    "transforms.route.type": "org.apache.kafka.connect.transforms.RegexRouter",
    "transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",
    "value.converter": "io.confluent.connect.avro.AvroConverter",
    "value.converter.basic.auth.user.info": "",
    "value.converter.schema.registry.url": "https://redpanda-registry.messaging-redpanda.qat.gaincapital.cloud",
    "value.converter.schemas.enable": "true"
{color:#000000}}

What is the captured database version and mode of depoyment?

hard to say; all information we've got is ojdbc library version: 8

What behaviour do you expect?

Successfully established connection to logs archive

What behaviour do you see?

Failure on attempt to access the archive

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

no, it cannot be used in our scenario.

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

yes, however the only complete error is logged in the Redpanda console

How to reproduce the issue using our tutorial deployment?

try to utilize ASM disks group as logs archive.

Feature request or enhancement

Support for ASM disks with "+" sign, as a prefix