Configure publication.config for the Source Database
Edit publication.config file where you unzipped the downloaded file from helyx website and set all required parameters.
| Parameter | Description | Purpose | Example |
|---|---|---|---|
| name | Unique name of the source connector. | Used to identify and manage the connector instance. | oracle-source-connector |
| bootstrap.ip | IP address of the Helyx physical server or VM. | Allows the connector to connect to the helyx-broker-manager for publishing change events. | 192.xxx.xxx.xxx |
| database.server.name | Logical name of the Oracle source database server. | Used as a namespace for topic generation and database identification. | ORCLSRC |
| database.hostname | Hostname or IP address of the source database. | Used by the connector to connect to the oracle source database server. | 192.xxx.xxx.xxx |
| topic.prefix | Prefix used when creating topics for captured tables. | Helps organize topics related to this connector. | oraclecdc |
| database.port | Port number used to connect to the source database. | Required for establishing database connectivity. | 1521 |
| database.password | Password of the database replication user (helyx). | Used for authentication with the source database. | ******** |
| database.dbname | Name of the source database instance. | Specifies which database the connector should capture changes from. | ORCLCDB |
| log.mining.archive.destination | Archive log destination used for Oracle LogMiner. | Allows the connector to read archived redo logs for change capture. | LOG_ARCHIVE_DEST_1 |
| heartbeat.interval.ms | Interval at which heartbeat messages are sent. | Helps monitor connector health and connectivity. | 10000 |
| database.connection.timeout.ms | Maximum time allowed for database connection attempts. | Prevents long waits if the database connection fails. | 30000 |
| batch.size | Number of events processed in a single batch. | Improves performance by processing multiple records together. | 65536 |
| max.batch.size | Maximum number of records returned in a batch. | Controls processing limits and memory usage. | 1000 |
| lob.chunk.size | Size of chunks used for LOB (BLOB/CLOB) data processing. | Helps efficiently process large object data types. | 8192 |
1. Configure tablelist.config
The table list should be provided as comma-separated values, each including the fully qualified schema name. For example, if table1 resides in the scott schema, the entry should be formatted as scott.table1. If table2 resides in helyx schema, the entry should be formatted as scott.table1, helyx.table2.
For example if you want to replicate every table in scott schema at source oracle database you must give scott.* at tablelist.config files.
2. tabletorepl
This procedure grants the necessary privileges to the helyx user, ensuring seamless replication between the source and target databases.
Assigning the appropriate permissions is critical because, without them, the helyx replication process may encounter errors or experience interruptions, potentially impacting the integrity and consistency of the replicated data. By providing the required access rights from the outset, you help guarantee that the replication workflow operates smoothly and reliably throughout the system.
User required source database sys user and sysdba privileges to run the command below :
./tabletorepl -s <full_qualified_path_to_publication.config> -tables <full_qualified_path_to_tablelist.config>To view the command help, run the following command:
./tabletorepl -helpStart Publication Service
serverconfig
This program is an essential components required to initiate and manage both the publication and subscription services within the replication framework. These executables facilitate seamless data replication between source and target databases, ensuring operational reliability and data consistency throughout the replication process.
Proper configuration and execution of these executables are fundamental to establishing, maintaining, and monitoring replication workflows in accordance with system requirements and best practices.
To start the Publication service
<path_to_serverconfig> -createpub -s <path_to_publication.config> -tables <path_to_tablelist.config>