Skip to main content

Oracle Migration and Synchronization to ClickHouse

NineData Data Replication supports copying data from Oracle to ClickHouse, supporting both schema and full data replication.

Function Introduction​

NineData data replication supports high-performance replication of structure, full data, and incremental data between data sources. For MySQL data sources, it also provides bidirectional replication, enabling the quick construction of geo-distributed active-active business architectures.

  • Structure: Supports the replication of object structures between homogeneous and heterogeneous data sources, greatly reducing the barrier to data replication between two sources.
  • Full Data: Achieves row-level concurrent batch replication through intelligent data sharding, effectively ensuring replication performance. The independently developed novel breakpoint resume technology ensures the accuracy of data in tables without primary keys.
  • Incremental Data: Supports incremental data replication of full object types DML|DDL, combined with transaction-level concurrency, hotspot merging, and other technologies to provide robust replication performance while ensuring transaction consistency.
  • Bidirectional Real-time Data Replication (only between MySQL instances): Direct bidirectional replication of data between multiple nodes ensures that all node data remains up-to-date.

With the above features, it is easy and efficient to achieve scenarios such as full|incremental data replication, full|incremental data migration, full|incremental data synchronization, data integration, and seamless migration without downtime, providing enterprises with flexible and reliable data replication solutions.

Prerequisites​

  • Both source and target data sources have been added to NineData. For instructions on how to add data sources, please refer to Adding Data Sources.

  • The versions of source and target data sources are as follows:

    Source Data SourceTarget Data Source
    Oracle 11g or aboveClickHouse 20.8 or above

  • If incremental replication is required, ensure the following configurations are set in the source data source:

    • Oracle's log mode is set to ARCHIVELOG mode (by default it is NOARCHIVELOG).

      sqlCopy code
      To verify the current log mode: SELECT log_mode FROM v$database;
      If the log mode is NOARCHIVELOG, perform the following steps:
      1. Shut down the database: SHUTDOWN IMMEDIATE;
      2. Start and mount the database: STARTUP MOUNT;
      3. Execute the command to enable archiving: ALTER DATABASE ARCHIVELOG;
      4. Start the database: ALTER DATABASE OPEN;

    • Supplemental Log has been enabled (not enabled by default).

      sqlCopy code
      To verify if Supplemental Log is enabled: SELECT supplemental_log_data_all allc FROM v$database;
      If it returns NO, execute the command to enable Supplemental Log:
      - ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;
      //Enables Supplemental Log at the database level, affecting all tables and columns, and consuming more resources.
      - ALTER TABLE <database_name>.<table_name> ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;
      - ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
      //Enables Supplemental Log on specific tables, affecting all columns in that table.

  • The access_management parameter value for the account used to log in to ClickHouse must be 1.

    Configuration Method:

    Open the /etc/clickhouse-server/User.xml configuration file with an editor, find the target user, and add the parameter: <access_management>1</access_management>.

  • The following permissions are required for both the source and target data sources.

    Replication TypeSource Data SourceTarget Data Source
    Full Replication
    • select connect
    • select any dictionary
    • select_catalog_role
    		Permissions related to TABLE (CREATE, CREATE TABLE, ALTER, ALTER COLUMN, DROP, SELECT, INSERT)

Notes​

  • If there are unsigned integer type fields in the source Oracle data source, they will be mapped to Uint type in ClickHouse.

  • Typically, Oracle to ClickHouse replication scenarios need to include schema replication, where the system automatically migrates Oracle table structures to ClickHouse and inserts two system columns into tables involved in replication in ClickHouse. If the replication type does not include schema replication, you need to manually ensure the following:

    • The schema of the data objects involved in ClickHouse data sources replication must be consistent with that of the Oracle data source.

    • Two system columns need to be manually inserted into tables involved in ClickHouse data source replication to record DML operations and Binlog time.

      Column NameData TypeDefault ValueDescription
      _jz_data_signInt8DEFAULT 1Records the type of DML operation to ensure consistency between ClickHouse and Oracle data.
      • INSERT operation: recorded as 1.
      • DELETE operation: recorded as -1.
      • UPDATE operation: split into INSERT and DELETE operations.
      _jz_data_timeStringDEFAULT now()Records the time of Binlog.

      Example:

      lessCopy code
      CREATE TABLE [IF NOT EXISTS] [db.]table_name [ON CLUSTER cluster]
      (
          ...
          _jz_data_sign Int8 DEFAULT 1 COMMENT 'replication data update sign: add = 1, remove = -1',
          _jz_data_time String DEFAULT now() COMMENT 'replication data update time'
      ) ENGINE = engine

Usage Limitations​

  • Before executing data synchronization, evaluate the performance of both source and target data sources, and it is recommended to perform data synchronization during off-peak hours. Otherwise, initializing full data may consume a certain amount of read-write resources of the source and target data sources, resulting in an increase in database load.
  • It is recommended to ensure that each table in the synchronized objects has a primary key or unique constraint, and column names are unique. Otherwise, duplicate synchronization of the same data may occur.

Operation Steps​

Commercialization Notice

NineData’s data replication product has been commercialized. You can still use 10 replication tasks for free, with the following considerations:

  • Among the 10 replication tasks, you can include 1 task, with a specification of Micro.

  • Tasks with a status of do not count towards the 10-task limit. If you have already created 10 replication tasks and want to create more, you can terminate previous replication tasks and then create new ones.

  • When creating replication tasks, you can only select the you have purchased. Specifications that have not been purchased will be grayed out and cannot be selected. If you need to purchase additional specifications, please contact us through the customer service icon at the bottom right of the page.

  1. Log in to the NineData Console.

  2. Click on in the left navigation pane.

  3. On the page, click on the button in the upper right corner.

  4. On the tab, configure according to the table below, and click .

    Parameter
    		Description
    Enter a name for the data synchronization task, using a meaningful name for easy identification and management. Maximum 64 characters.
    The data source where the synchronized object resides.
    The data source that receives the synchronized object.
    Choose the case conversion rule for object names migrated from the source to the target.
    • : Convert all object names to lowercase regardless of the naming convention on the source side.
    • : Retain the naming convention of the source.
    • : Convert all object names to uppercase regardless of the naming convention on the source side.
    Choose the content to be copied to the target data source.
    • : Only synchronize the schema of the source data source without synchronizing data.
    • : Synchronize all objects and data from the source data source, i.e., full data replication. The switch on the right is for periodic full replication. For more information, please refer to Periodic Full Replication.
    (selected when is selected)
    • : Stop the task when a table with the same name is detected during the pre-check phase.
    • : When a table with the same name is detected during the pre-check phase, a prompt is sent, and the task continues. Ignore the same-name table during schema replication. If data replication is also performed, data will be appended to the same-name table without overwriting existing data.
    • : When a table with the same name is detected during the pre-check phase, a prompt is sent, and the task continues. During schema replication, the same-name table in the target database is deleted, and the table structure is re-replicated based on the source database. If data replication is also performed, data will be written to the table after the table structure replication is completed.
    • (optional when both schema and data replication are performed): When a table with the same name is detected during the pre-check phase, a prompt is sent, and the task continues. During schema replication, the table structure in the target database is retained, and data in the same-name table is cleared when data replication begins, and then copied from the original table again.
    (required when is not selected)
    • : Stop the task when data exists in the target table is detected during the pre-check phase.
    • : When data exists in the target table is detected during the pre-check phase, ignore this part of the data and append other data.
    • : When data exists in the target table is detected during the pre-check phase, delete this part of the data and rewrite it.

  5. On the tab, configure the following parameters and then click .

    Parameter
    		Description
    Choose the content to be copied. You can select to copy all contents of the source database, or select , select the content to be copied from the list, and click > to add it to the list on the right.

    If you need to create multiple identical replication links, you can create a configuration file and import it when creating a new task. Click at the top right corner, then click Download Template to download the configuration file template to your local machine. After editing, click to upload the configuration file for batch import.

    Parameter
    		Description
    source_table_nameName of the source table containing the objects to be synchronized.
    destination_table_nameName of the target table receiving the synchronized objects.
    source_schema_nameName of the source schema containing the objects to be synchronized.
    destination_schema_nameName of the target schema receiving the synchronized objects.
    source_database_nameName of the source database containing the objects to be synchronized.
    target_database_nameName of the target database receiving the synchronized objects.
    column_listList of columns to be synchronized.
    extra_configurationAdditional configuration information, where you can configure the following:
    • Column Mapping: column_name, destination_column_name
    • Column Value: column_value
    • Data Filtering: filter_condition
    tip

    • An example of the extra_configuration content is as follows:

      {
          "column_name": "created_time", // Original column name to be mapped
          "destination_column_name": "migrated_time", // Target column name mapped to "migrated_time"
          "column_value": "current_timestamp()", // Change the column value to the current timestamp
          "filter_condition": "id != 0" // Only synchronize rows where ID is not 0.
      }

    • For a complete example of the configuration file, refer to the downloaded template.

  6. On the tab, select different operations based on the selected replication type, and then click . If there are updates in the source and target data sources during the configuration mapping phase, you can click the button in the upper right corner of the page to retrieve the information of the source and target data sources again.

    • Including : Configure the table name after synchronization to the target data source.

    • Excluding : The system automatically selects the same-named database in the target data source. If it does not exist, you need to manually select the target database. The table names and column names in the target database need to be consistent with the synchronized objects. If they are not consistent, you can manually map the table names and column names.

    You can click on on the right side of the page to customize the name of the columns after synchronization to the target data source. In addition, you can set to configure filter conditions through comparison expressions. Only data that meets the filter conditions will be synchronized to the target data source. For example, setting the filter condition to emp_no>=10005 means that data with emp_no less than 10005 will not be synchronized to the target data source.

  7. On the tab, wait for the system to complete the pre-check. After the pre-check passes, click .

    tip
    • You can check . After the synchronization task is completed, automatic data consistency comparison based on the source data source is initiated to ensure data consistency on both ends. Depending on your selection of , the timing of starting is as follows:
      • : Initiated after schema replication is completed.
      • + , : Initiated after full replication is completed.
    • If the pre-check fails, you need to click the in the column on the right of the target check item, troubleshoot the reason for the failure, manually fix it, and then click to execute the pre-check again until it passes.
    • Check items with in can be repaired or ignored depending on the specific situation.

  8. On the page, when prompted , the synchronization task begins. At this point, you can:

    • Click to view the execution status of each stage of the synchronization task.
    • Click to return to the task list page .

View Synchronization Results​

  1. Log in to the NineData console.

  2. Click on > in the left navigation pane.

  3. On the page, click on the of the target synchronization task, and the page description is as follows.

    result_no_incre

    Number
    		Function
    		Description
    1Configure AlertsAfter configuring alerts, the system will notify you in the selected way when the task fails. For more information, please refer to Operational Monitoring Overview.
    2More
    • : Pause the task. Only tasks with the status Running are selectable.
    • : Create a new replication task with the same configuration as the current task.
    • : End tasks that are incomplete or in listening (i.e., in incremental synchronization). After terminating the task, it cannot be restarted, so please proceed with caution. If triggers are included in the synchronization object, trigger replication options will pop up, please choose as needed.
    • : Delete the task. Once the task is deleted, it cannot be recovered, so please proceed with caution.
    3Structural Replication (Displayed in scenarios involving structural replication)Display the progress and details of structural replication.
    • Click on on the right side of the page: View the execution log of structural replication.
    • Click on refresh on the right side of the page: View the latest information.
    • Click on in the column on the right side of the target object in the list: View SQL playback.
    4Full Replication (Displayed in scenarios involving full replication)Display the progress and details of full replication.
    • Click on on the right side of the page: View various monitoring indicators during full replication. During full replication, you can also click on on the right side of the monitoring indicator page to limit the rate of data written to the target data source per second. The unit is rows/second.
    • Click on on the right side of the page: View the execution log of full replication.
    • Click on refresh on the right side of the page: View the latest information.
    5Data ComparisonDisplay the comparison results between the source data source and the target data source. If you have not enabled data comparison, click on the page.
    • Click on on the right side of the page: Re-initiate the comparison of data between the current source and target ends.
    • Click on on the right side of the page: After starting the comparison task, you can click this button to stop the comparison task immediately.
    • Click on on the right side of the page: View the execution log of consistency comparison.
    • Click on (only displayed in data comparison): View the trend chart of RPS (records per second compared) for comparison. Click on to view records from earlier times.
    • Click on details in the column on the right side of the comparison list (displayed only under the tab when there is inconsistency): View detailed comparison between the source and target ends.
    • Click on sql in the column on the right side of the comparison list (displayed only in case of inconsistency): Generate change SQL, which you can directly copy to the target data source to execute and modify the inconsistent content.
    6ExpandDisplay detailed information of the current replication task. Common Options:
    • : Export the current task's database and table configuration, allowing for quick import when creating a new replication task. This helps rapidly establish multiple replication links with the same replication objects.
    • : Configure the alarm strategy for the current task.

Appendix: Checklist​

Check ItemCheck Content
Source datasource connection checkCheck the status of the gateway of the source datasource, database connectable, and verify the username and password
Target datasource connection checkCheck the status of the gateway of the target datasource, database connectable, and verify the username and password
Target databse privilege checkCheck whether the account privileges of the target database meet the requirements
Source databse privilege checkCheck whether the account privileges of the source database meet the requirements
Target database data existence checkCheck whether the object to be replicated not empty in the target database
Objects with the same name in the target database existence checkCheck whether the object to be replicated already exists in the target database

Introduction to Data Replication

Last updated on