Oracle LogMiner Gluesync Configuration

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) Enable TLS/SSL encryption
Trust Server Certificate: (optional, defaults to false) Trust server certificate without validation
Additional Hosts: (optional) List of additional hosts for failover
Max connections count: Maximum number of connections the pool can instantiate

Advanced Settings

Connection type: (optional, defaults to SID) 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

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)

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,
        "trustServerCertificate": false,
        "additionalHosts": [],
        "maxConnectionsCount": 100
    },
    "customHostCredentials": {
        "logminerUsername": "C##GLUESYNC",
        "logminerPassword": "your_logminer_password",
        "logminerDatabase": "ORCLCDB",
        "logminerConnectionTimeout": "10000",
        "logminerReadTimeout": "60000"
    }
}'

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

enableTls: Enable TLS/SSL encryption
certificatePath: Path to TLS/SSL certificate
useWalletAuthentication: Use Oracle Wallet for authentication
walletPath: Path to Oracle Wallet

Best Practices

Connection Pool Management:
- Set appropriate maxConnectionsCount. LogMiner requires a dedicated session.
- Monitor potential blocking if pool is exhausted.
Timeout Configuration:
- Adjust timeoutSeconds based on network latency and LogMiner startup time (which can be slow on large databases).
Security:
- Always use TLS in production
- Least privilege principle for the LogMiner user.

Troubleshooting

For configuration-related issues:

Verify connection parameters (Host, Port, Service Name)
Check user privileges (SELECT_CATALOG_ROLE is often missed)
Validate Archive Log access
Review timeout settings if LogMiner fails to start

For detailed troubleshooting steps, see LogMiner Troubleshooting Guide.