Helyx Replication

Source Database in ARCHIVELOG Mode

The source Oracle database must operate in ARCHIVELOG mode. Helyx relies on archived redo logs to capture transactional changes reliably.

Supplemental logging is mandatory to ensure complete row-level data is available for replication.

ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;

Create a dedicated database user for Helyx replication activities.

CREATE USER helyx IDENTIFIED BY <password>;

Grant the following privileges to the helyx user:

GRANT CONNECT, RESOURCE TO helyx;

ALTER USER helyx QUOTA UNLIMITED ON USERS;

GRANT UNLIMITED TABLESPACE TO helyx;

Note

By default, Helyx creates objects in the USERS tablespace. If a different tablespace is required, create the user as shown below.

Example :

CREATE USER helyx IDENTIFIED BY <password> DEFAULT TABLESPACE tblspc_helyx QUOTA UNLIMITED ON tblspc_helyx;

The Debezium signal table is required for snapshot control and runtime signaling.

CREATE TABLE helyx.debezium_signal (id VARCHAR2(42) PRIMARY KEY,type VARCHAR2(32) NOT NULL,data VARCHAR2(400));

GRANT SELECT, INSERT, UPDATE, DELETE ON HELYX.DEBEZIUM_SIGNAL TO helyx;

Grant Required Privileges

Grant the following privileges to the helyx user:

GRANT CONNECT, RESOURCE TO helyx;

ALTER USER helyx QUOTA UNLIMITED ON USERS;

GRANT UNLIMITED TABLESPACE TO helyx;

Note

By default, Helyx creates objects in the USERS tablespace. If a different tablespace is required, create the user as shown below.

Example :

CREATE USER helyx IDENTIFIED BY <password> DEFAULT TABLESPACE tblspc_helyx QUOTA UNLIMITED ON tblspc_helyx;