SAP HANA to OceanBase

BladePipe supports data replication from SAP HANA to OceanBase. View supported migration, sync, verification, and connector capabilities.

Target DataSource：

OceanBase

Connection

Basic Functions

Function	Description
Schema Migration	If the target schema does not exist, BladePipe will automatically generate and execute CREATE statements based on the source metadata and the mapping rule.
Full Data Migration	Migrate data by sequentially scanning data in tables and writing it in batches to the target database.
Incremental Data Sync	Sync of common DML like INSERT, UPDATE, DELETE is supported. UPDATE and DELETE for tables without primary keys are not synced by default (manual selection required).
Data Verification and Correction	Verify all existing data. Optionally, you can correct the inconsistent data based on verification results. Scheduled DataTasks are supported. For more information, see Create Verification and Correction DataJob.
Subscription Modification	Add, delete, or modify the subscribed tables with support for historical data migration. For more information, see Modify Subscription.
Position Resetting	Reset positions by data ID or timestamp. Allow re-consumption of CDC data in a past period.
Table Name Mapping	Support the mapping rules, namely, keeping the name the same as that in Source, converting the text to lowercase, converting the text to uppercase, truncating the name by "_digit" suffix.
Metadata Retrieval	Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Advanced Functions

Function	Description
Trigger-based Incremental Data Sync	The DataJob automatically creates triggers on tables. These triggers capture INSERT, UPDATE, and DELETE events and write them to the CDC tables.
Removal of Target Data before Full Data Migration	Remove the existing data in the Target before running the Full Data Migration, applicable for DataJobs reruning and scheduled Full Data migrations.
Recreating Target Table	Recreate target tables before running the Full Data Migration, applicable for DataJobs reruning and scheduled Full Data migrations.
Highly Concurrent Row-Level Write	It has the distributed database characteristics. A highly concurrent row-level write strategy (ROW) is adopted by default.
Incremental Data Write Conflict Resolution Rule	IGNORE: Ignore primary key conflicts (skip writing), REPLACE: Replace the entire row in case of primary key conflicts.
Scheduled Full Data Migration	For more information, see Create Scheduled Full Data DataJob.
Custom Code	For more information, see Custom Code Processing, Debug Custom Code and Logging in Custom Code.
Data Filtering Conditions	Support data filtering using WHERE conditions, with SQL-92 as the SQL language. For more information, see Data Filtering.

Limits

Limit	Description
DDL Change Handling	BladePipe captures data changes in a source SAP HANA instance through triggers. DDL synchronization is not supported. If there are DDL changes, follow the steps in Change Schema in a Source SAP HANA Instance.
Hana Data Types in Incremental Sync	In the incremental data sync phase with a source Hana instance, it does not allow capturing changes for TEXT, BIN_TEXT, ST_POINT, and ST_GEOMETRY data types by triggers.
OceanBase Version	Currently only OceanBase for MySQL is supported.
OceanBase Data Types	Geospatial data is not supported.

FAQ

• What should I do if an error occurs when connecting to a Sap Hana instance?

---

Source

Prerequisites

Prerequisite	Description
Permissions for Account	See Permissions Required for Hana

Parameters

Parameter	Description
sysTriggerDataSchema	The schema name where the trigger writes incremental data.
sysTriggerDataTable	The table name where the trigger writes incremental data.
incrPagingCount	The total amount of data queried each time by the trigger during incremental data synchronization.
incrIdleSleepSecond	The interval between queries for the trigger during idle period of incremental data synchronization (in seconds).
incrScanIntervalMs	The interval between data queries for the trigger during incremental data synchronization (in milliseconds).
autoCheckTriggerAndReInstall	Check the trigger status and reinstall it when the DataJob starts.
triggerDataCleanEnabled	Enable scheduled cleanup of trigger incremental data.
triggerDataCleanIntervalMin	The cleanup interval for trigger incremental data (in minutes).
triggerDataRetentionMin	The retention time for trigger incremental data (in minutes).
dbHeartbeatEnable	Configure whether to enable heartbeat for the source database.
needTriggerDataJsonEscape	Whether to escape characters (\) in the trigger incremental JSON.
triggerDataJsonQuotation	Custom quotation marks for trigger incremental JSON.
triggerParamBathSize	Set the number of columns involved per variable in the trigger template.
fullBeforeImageEnabled	Enable the trigger to record the complete data before all column changes.

Tips: To modify the general parameters, see General Parameters and Functions.

---

Target

Prerequisites

Prerequisite	Description
Permissions for Account	SELECT, INSERT, DELETE, UPDATE, and common DDL permissions.
Port Preparation	Allow the migration and sync node (Worker) to connect to the OceanBase port (e.g., 3306).

Parameters

Parameter	Description
keyConflictStrategy	Strategy for handling primary key conflicts during write in Incremental DataTask: IGNORE: Ignore conflicts (default) REPLACE: Replace conflicts (optional)
writeStrategy	Target write strategies include: ROW (single row, default) MULTI_SQL (multiple statements) BATCH (batch)

Tips: To modify the general parameters, see General Parameters and Functions.