Targeting Oracle with LogMiner Agent
Overview
This guide explains how to configure Oracle as a target database when using the LogMiner agent (or simply the standard Oracle JDBC connectivity provided by Gluesync).
|
How-to guide
For a step-by-step walkthrough tested on a running Gluesync, see the how-to guide Choose a key strategy: physical, logical, RRN or computed. |
Target Configuration
Database Requirements
-
Oracle Database (version 11.2.0.4 or higher)
-
User with appropriate write permissions (
INSERT,UPDATE,DELETE,CREATE TABLEif auto-creation is needed) -
Sufficient storage space for target tables
Setup via Web UI
-
Hostname / IP Address: DNS record or IP Address of your server;
-
Port: Optional, defaults to
1521; -
Database name: Name of your database;
-
Username: Username with read/write access to the tables;
-
Password: Password belonging to the given username;
-
Max connections count: Maximum number of connections the pool can instantiate.
Updates with bulk operations during CDC
|
When Use bulk operations during CDC ( For the target table this has the following effects:
|
Setup via Rest APIs
Here following an example of calling the Core Hub’s Rest API via curl to setup the connection for this Agent.
curl --location --request PUT 'http://core-hub-ip-address/pipelines/{pipelineId}/agents/{agentId}/config/credentials' \
--header 'Content-Type: application/json' \
--header 'Authorization: ••••••' \
--data '{
"hostCredentials": {
"connectionName": "myAgentNickName",
"host": "host-address",
"port": 1521,
"databaseName": "db_name",
"username": "target_user",
"password": "password",
"maxConnectionsCount": 100,
"enableTls": true,
"trustStorePath": "/opt/gluesync/data/oracle-tls/truststore.jks",
"trustStorePassword": "your_trust_store_password"
},
"customHostCredentials": {
"defaultConnectionType": "SID"
}
}'