OceanBase for Oracle
| 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. |
Data Verification and Correction | Verify all existing data. Optionally, you can correct the inconsistent data based on verification results. Scheduled DataTasks are supported. |
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 timestamp. Allow re-consumption of incremental data logs 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. |
DDL Sync |
|
Metadata Retrieval | Retrieve the target metadata with filtering conditions set from the source table. |
Advanced Functions
| Function | Description |
|---|---|
CDC-based Incremental Data Sync | Support incremental data synchronization based on OceanBase LogProxy. |
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. |
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 |
|---|---|
OceanBase Version | Currently only OceanBase for MySQL is supported. |
OceanBase Data Types | Geospatial data is not supported. |
Prerequisites
| Prerequisite | Description |
|---|---|
Permissions for Account | Permissions for all tables in the SYS tenant databases and SELECT permission for databases and tables to be synced. |
Port Preparation | Allow the migration and sync node (Worker) to connect to the OceanBase ports (e.g., 2881) and LogProxy ports (if available, e.g., 2983). |
Parameters
| Parameter | Description |
|---|---|
needJsonEscape | Escape special characters in JSON to be written to the target database. |
fullDataSqlConditionEnabled | Add filtering conditions in SQL during source data scanning. It only works in Full Data migration. |
eventStoreSize | Cache size for parsed incremental events. |
clusterUrl | OceanBase cluster URL (similar to a name server). |
obLogProxyHost | LogProxy service address, typically in the format ip:2983. Required for LogProxy incremental mode. |
rpcPortList | RPC ports for OceanBase server nodes. If the host parameter is ip1;ip2, this parameter should be port1;port2. Common port is 2882. Required for LogProxy incremental mode. |
syncAccount | Account for LogProxy to connect to OceanBase server (optional). |
syncPwd | Password for LogProxy to connect to OceanBase server (optional). |
tenant | The tenant where the subscribed tables reside. |
clusterName | OceanBase cluster name. |
workingMode | Libobcdc parameter that LogProxy depends on. The default value is storage. |
Tips: To modify the general parameters, see General Parameters and Functions.
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:
|
writeStrategy | Target write strategies include:
|
Tips: To modify the general parameters, see General Parameters and Functions.