Aurora for PostgreSQL to OceanBase

BladePipe supports data replication from Aurora for PostgreSQL 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 file position or timestamp. Allow re-consumption of incremental data logs in a past period or since a specific Binlog file and position.
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.
DDL Sync	PostgreSQL DDL sync is realized by triggers. The user should have the permissions on triggers and tables. For more information, see Permissions Required for PostgreSQL ALTER TABLE ADD COLUMN, DROP COLUMN, MODIFY COLUMN ADD INDEX RENAME TABLE CREATE TABLE (whole database sync)
Metadata Retrieval	Retrieve the target metadata with filtering conditions or target primary keys set from the source table.

Advanced Functions

Function	Description
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.
Custom Code	For more information, see Custom Code Processing, Debug Custom Code and Logging in Custom Code.
Adding Virtual Columns	Support adding custom virtual columns with fixed values, such as region, ID, etc.
Setting Target Primary Key	Change the primary key to another field to facilitate data aggregation and other operations.

Limits

Limit	Description
OceanBase Version	Currently only OceanBase for MySQL is supported.
OceanBase Data Types	Geospatial data is not supported.

Source

Prerequisites

Prerequisite	Description
Permissions for Account	Required permissions (taking a self-managed database as an example): GRANT ALL PRIVILEGES ON DATABASE sync_db TO sync_user (or SELECT permission on all views in the sync_db information_schema, and SELECT permission on tables, indexes, constraints to be synchronized) ALTER USER sync_user REPLICATION
Incremental Data Sync Preparation	Prepare as follows: Modify postgresql.conf, set wal_level=logical and wal_log_hints=on Modify pg_hba.conf, set host replication sync_user CIDR netmask md5, host sync_db sync_user CIDR netmask md5, host postgres sync_user CIDR netmask md5 Restart PostgreSQL
Port Preparation	Allow the migration and sync node (Worker) to connect to the PostgreSQL port (e.g., port 5432).

Prerequisite

Description

Permissions for Account

Required permissions (taking a self-managed database as an example):

GRANT ALL PRIVILEGES ON DATABASE sync_db TO sync_user (or SELECT permission on all views in the sync_db information_schema, and SELECT permission on tables, indexes, constraints to be synchronized)
ALTER USER sync_user REPLICATION

Incremental Data Sync Preparation

Prepare as follows:

Modify postgresql.conf, set wal_level=logical and wal_log_hints=on
Modify pg_hba.conf, set host replication sync_user CIDR netmask md5, host sync_db sync_user CIDR netmask md5, host postgres sync_user CIDR netmask md5
Restart PostgreSQL

Port Preparation

Allow the migration and sync node (Worker) to connect to the PostgreSQL port (e.g., port 5432).

Parameters

Parameter	Description
fullFetchSize	Fetch size for scaning full data.
eventStoreSize	Cache size for parsed incremental events.
ignoreGisSRID	Whether to ignore SRID when parsing GIS data types.
defaultGisSRID	Set the SRID for GIS data types.

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)

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.