Search docs.molo17.com

    Oracle XStream logo Oracle LogMiner Gluesync Configuration

    How-to guide

    For a step-by-step walkthrough tested on a running Gluesync, see the how-to guide Set up Oracle LogMiner CDC end to end.

    Web UI Configuration

    Configure the following parameters in the Gluesync Web UI:

    Basic Connection Settings

    • Hostname / IP Address: DNS record or IP Address of your server

    • Port: Optional, defaults to 1521

    • Database name: Name of your database (or PDB Service Name)

    • Username: Username with privileges (e.g., gluesync_logminer)

    • Password: Password belonging to the given username

    • Disable Auth: (optional, defaults to false) Disable authentication

    • Enable TLS: (optional, defaults to false) Connects to the TCPS listener of Oracle. See Connect over TLS or through a wallet

    • Upload 'trust store' file and Trust store password: (optional) The CA certificates that the server certificate of Oracle is validated against. Without a trust store, the default CAs of the Java runtime are used

    • Upload 'key store' file and Key store password: (optional) The client certificate and its private key, only for a listener that requires client authentication (mutual TLS)

    • Additional Hosts: (optional) List of additional hosts for failover

    • Max connections count: Maximum number of connections the pool can instantiate

    The Oracle form has no Trust server certificate switch: the Oracle driver always validates the certificate of the server.

    Advanced Settings

    • Connection type: (optional, defaults to SERVICE_NAME) Connection type used to connect to Oracle. Available types are:

      • SID

      • SERVICE_NAME

    • Timeout seconds: (optional, defaults to 60 seconds) Number of seconds to set as timeout for operations

    • Use wallet: (optional, defaults to false) Connects through a TNS alias resolved from a wallet folder, instead of the host and the port

    • Instance name: (required when Use wallet is on) The TNS alias, defined in the tnsnames.ora of Wallet path, of the database of the data user. Despite its name, it is an alias and not the name of an Oracle instance

    • Wallet path: (required when Use wallet is on) The folder that contains tnsnames.ora and the wallet, as Core Hub sees it

    • LogMiner instance name: (optional) The TNS alias that the LogMiner connections use when Use wallet is on, usually the CDB root. When it is empty, the LogMiner connections are opened on the host and the port with LogMiner database, outside the wallet, and the agent logs a warning

    LogMiner Credentials (Custom Host Credentials)

    When using the LogMiner agent, you must provide the credentials for the LogMiner utility:

    • LogMiner Username: (e.g., C##GLUESYNC) The username used by the LogMiner engine to access transaction logs.

    • LogMiner Password: The password for the LogMiner user.

    • LogMiner Database: (e.g., ORCLCDB) The name of the database where the LogMiner session should be initiated.

    • LogMiner Connection Timeout (logminerConnectionTimeout): (optional, defaults to 10000 ms) Maximum time in milliseconds allowed for the initial TCP handshake when opening the LogMiner JDBC connection.

    • LogMiner Read Timeout (logminerReadTimeout): (optional, defaults to 60000 ms) Maximum time in milliseconds the JDBC driver waits for a response from Oracle on the LogMiner connection after it has been established. When Oracle becomes unreachable (host restart, network blackhole), this timeout causes the blocking executeQuery call to fail within the configured window rather than hanging indefinitely. The agent then recovers in-place: it drops orphaned in-flight transaction state, reconnects, and resumes from the persisted SCN checkpoint — without requiring a full software restart.

    Lower logminerReadTimeout (e.g. 15000–30000) for faster recovery. Values below 5000 ms may produce false positives on loaded databases.

    Multi-Tenant Specific Settings

    For multi-tenant databases, additional settings might be required depending on your connection string:

    • CDB Name: Name of the container database (if connecting to Root)

    • PDB Name: Name of the pluggable database containing the data (if not specified in Service Name)

    Connect over TLS or through a wallet

    Gluesync reaches an Oracle listener that requires TLS (TCPS) in one of two ways: with Enable TLS and a trust store, or through a TNS alias of an Oracle wallet.

    Enable TLS with a trust store

    With Enable TLS on, the agent builds a TCPS descriptor from Hostname, Port, Connection type and Database name, for example jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(HOST=oracle)(PORT=2484))(CONNECT_DATA=(SERVICE_NAME=ORCL))). Set Port to the TCPS port of the listener.

    • The server certificate is always validated, against the uploaded trust store or, without one, against the default CAs of the Java runtime. A certificate issued by a private CA needs a trust store that holds that CA.

    • A trust store can be a .jks, .p12 or .pfx file, or a PEM file (.pem, .crt, .cer) with the CA certificates, which the agent converts to PKCS12. Use a .jks, .p12 or .pfx key store for mutual TLS.

    • The same settings apply to every connection opened on the host and the port: the connections of the data user and the LogMiner connections, which use LogMiner database.

    • A custom Connection string is used as you write it: enter PROTOCOL=TCPS in it yourself. With Enable TLS on, the trust store and the key store are applied to it as well.

    Use an Oracle wallet

    With Use wallet on, the agent connects to jdbc:oracle:thin:@<Instance name>?TNS_ADMIN=<Wallet path>, so the alias is resolved from the tnsnames.ora in Wallet path.

    To get the wallet, change its paths and copy it where Core Hub reads it, see Prepare an Oracle wallet for Gluesync.

    • The wallet folder decides the security of the connections that go through the alias: Enable TLS and the trust and key stores of the form are not applied to them.

    • Wallet path is a path inside the Core Hub container. In the Linux kit, the folder data/core-hub of the installation is mounted as /opt/gluesync/data: put the wallet folder under it and enter /opt/gluesync/data/<folder>. A path of the host fails with ORA-12263: Failed to access tnsnames.ora.

    • The wallet does not replace the credentials: Gluesync always sends the Username and the Password of the form, and the LogMiner Username and LogMiner Password for LogMiner.

    • Fill LogMiner instance name too, or the LogMiner connections bypass the wallet and a TCPS-only listener refuses them. On Oracle RAC, a connection through an alias cannot be pinned to one instance; the reader still mines every redo thread.

    • A custom Connection string takes precedence over the wallet for the connections of the data user: the TLS settings of the form apply to it.

    The how-to guide Set up Oracle LogMiner CDC end to end shows the wallet fields in the form and the errors you can meet.

    REST API Configuration

    Basic Connection Setup

    curl --location --request PUT 'http://core-hub-ip-address/pipelines/{pipelineId}/agents/{agentId}/config/credentials' \
    --header 'Content-Type: application/json' \
    --header 'Authorization: ••••••' \
    --data '{
        "agentType": "SOURCE",
        "agentTag": "oracle-logminer",
        "hostCredentials": {
            "connectionName": "myAgentNickName",
            "host": "oracle",
            "port": 1521,
            "databaseName": "ORCL",
            "username": "GLUESYNCUSER",
            "password": "your_password",
            "disableAuth": false,
            "enableTls": false,
            "additionalHosts": [],
            "maxConnectionsCount": 100
        },
        "customHostCredentials": {
            "logminerUsername": "C##GLUESYNC",
            "logminerPassword": "your_logminer_password",
            "logminerDatabase": "ORCLCDB",
            "logminerConnectionTimeout": "10000",
            "logminerReadTimeout": "60000"
        }
    }'

    Connection over TLS

    curl --location --request PUT 'http://core-hub-ip-address/pipelines/{pipelineId}/agents/{agentId}/config/credentials' \
    --header 'Content-Type: application/json' \
    --header 'Authorization: ••••••' \
    --data '{
        "agentType": "SOURCE",
        "agentTag": "oracle-logminer",
        "hostCredentials": {
            "connectionName": "myAgentNickName",
            "host": "oracle",
            "port": 2484,
            "databaseName": "ORCL",
            "username": "GLUESYNCUSER",
            "password": "your_password",
            "enableTls": true,
            "trustStorePath": "/opt/gluesync/data/oracle-tls/truststore.jks",
            "trustStorePassword": "your_trust_store_password",
            "maxConnectionsCount": 100
        },
        "customHostCredentials": {
            "logminerUsername": "C##GLUESYNC",
            "logminerPassword": "your_logminer_password",
            "logminerDatabase": "ORCLCDB"
        }
    }'

    trustStorePath and keyStorePath are paths inside the Core Hub container. Leave them out to use the files uploaded in the Web UI.

    Connection through a wallet

    curl --location --request PUT 'http://core-hub-ip-address/pipelines/{pipelineId}/agents/{agentId}/config/credentials' \
    --header 'Content-Type: application/json' \
    --header 'Authorization: ••••••' \
    --data '{
        "agentType": "SOURCE",
        "agentTag": "oracle-logminer",
        "hostCredentials": {
            "connectionName": "myAgentNickName",
            "host": "oracle",
            "port": 1521,
            "databaseName": "ORCL",
            "username": "GLUESYNCUSER",
            "password": "your_password",
            "maxConnectionsCount": 100
        },
        "customHostCredentials": {
            "useWalletAuthentication": true,
            "instanceName": "GS_ORCL",
            "walletPath": "/opt/gluesync/data/oracle-wallet",
            "logminerInstanceName": "GS_ORCLCDB",
            "logminerUsername": "C##GLUESYNC",
            "logminerPassword": "your_logminer_password",
            "logminerDatabase": "ORCLCDB"
        }
    }'

    Configuration Parameters

    LogMiner Specific Parameters

    • archiveLogOnly: (optional, boolean) If set to true, Gluesync will only read from archived logs and not online logs.

    • scnMining: (optional, boolean) Strategies for SCN tracking.

    • skipTransactionsWithParseErrors: (optional, boolean, defaults to true) Controls how the agent behaves when a transaction contains SQL statements that cannot be parsed.

      • If true, parse-failed payloads are stored in the LogMiner parse DLQ table and the transaction is skipped on commit so checkpoint progress can continue.

      • If false, the agent does not advance checkpoint on commit for parse-failed transactions (strict mode), so processing remains blocked until operator action.

    Use skipTransactionsWithParseErrors=true for fail-open behavior with auditability. Use false when you prefer strict correctness and manual intervention.

    Security Parameters

    In hostCredentials:

    • enableTls: (boolean, defaults to false) Connect to the TCPS listener

    • trustStorePath and trustStorePassword: (optional) Trust store with the CA of the server certificate

    • keyStorePath and keyStorePassword: (optional) Key store with the client certificate, for mutual TLS

    In customHostCredentials:

    • useWalletAuthentication: (boolean, defaults to false) Connect through a TNS alias of the wallet (Use wallet in the Web UI)

    • instanceName: TNS alias of the database of the data user, required with the wallet

    • walletPath: Folder with tnsnames.ora and the wallet, inside the Core Hub container, required with the wallet

    • logminerInstanceName: TNS alias of the LogMiner connections when the wallet is on

    The Oracle agents do not read trustServerCertificate or certificatePath.

    Best Practices

    1. Connection Pool Management:

      • Set appropriate maxConnectionsCount. LogMiner requires a dedicated session.

      • Monitor potential blocking if pool is exhausted.

    2. Timeout Configuration:

      • Adjust timeoutSeconds based on network latency and LogMiner startup time (which can be slow on large databases).

    3. Security:

      • Always use TLS in production, with Enable TLS and a trust store or with a wallet

      • Least privilege principle for the LogMiner user.

    Troubleshooting

    For configuration-related issues:

    1. Verify connection parameters (Host, Port, Service Name)

    2. Check user privileges (SELECT_CATALOG_ROLE is often missed)

    3. Validate Archive Log access

    4. Review timeout settings if LogMiner fails to start

    For detailed troubleshooting steps, see LogMiner Troubleshooting Guide.