Helyx Features

To check List of tables at Data-Pipeline process

You can generate a comprehensive list of tables currently managed by the data pipeline, along with the total count of these tables. This report provides visibility into which tables are actively included in real-time Change Data Capture (CDC) processing.

By reviewing this information, you can verify that all necessary tables are being replicated without any data loss occurring between the source and target servers. Ensuring that the tables are present and accounted for in the data pipeline helps maintain data integrity across your replication environment.

To get the table list run the below command :

<path_to_serverconfig> -tablelist -s <publication.config>

To Remove tables from replication data-pipeline

To remove one or more tables from the replication data pipeline, you must execute the appropriate command as described below. Once a table has been successfully removed from the data pipeline, it will no longer participate in the replication process. This means that any subsequent changes or new rows in the removed table will not be captured or replicated to the destination PostgreSQL databases.

Removing tables from the replication pipeline is a critical operation if certain tables are no longer needed for data synchronization, as it helps maintain an optimized and manageable replication environment.

To remove table from replication run the below command :

./serverconfig -removetablefromrepl -s publication.config -tables [<comma_separated_table_list>]

As an illustration, if you need to remove a specific table—such as DEMO.HX_EMPLOYEE—from the replication data pipeline, it is essential to specify the table's name using its fully qualified format. This means you must include both the schema name and the table name, separated by a period. For example, to correctly identify the table for removal, you would enter DEMO.HX_EMPLOYEE as shown below. Providing the full schema and table name ensures that the correct table is targeted for removal, preventing any ambiguity that could arise if there are tables with the same name in different schemas. You can provide multiple tables all at once.

Monitoring migration Lag Status

The Helyx lag status utility is a robust command-line interface (CLI) tool designed to provide users with real-time insights into replication lag at the table level. This tool not only displays the current lag status for each table but also includes detailed remarks that categorize the status as critical, low priority, or healthy.

By offering granular visibility and prioritization, the Helyx lag status utility enables database administrators to quickly identify and address tables that require immediate attention, ensuring optimal performance and data consistency across the replication environment.

Supported Data Types

Helyx provides robust support for a wide array of data types across both Oracle and PostgreSQL platforms.

The following section outlines the specific Oracle data types that are supported by Helyx during real-time Change Data Capture (CDC) and migration processes. This ensures seamless data integration and migration while maintaining data consistency and integrity between your Oracle and PostgreSQL environments.

The data types supported by Helyx for oracle and Postgresql :

The data types supported by Helyx for oracle and Postgresql :

Helyx Log maintenance

All operational logs are maintained in the /var/lib/helyx/logs directory. The primary log file that users should monitor is helyx-connect-service-manager.log, as this file contains key information about system operations. It is important to note that helyx does not automatically manage the housekeeping of these log files. Therefore, users are responsible for regularly checking available filesystem space and manually removing or archiving log files as and when needed.