Oracle

DataArts Migration supports cloud-based RDS-Oracle and on-premises Oracle data sources. It adapts to Oracle 19c and 11c and meets the data synchronization requirements in different deployment environments.

Preparation and Constraints

Network requirements
The Oracle data source can communicate with CDM. This ensures smooth data transmission. For details, see Enabling Network Connectivity.
Required permissions
- Connection user permissions: The connection user must have the resource role and the SELECT permission on data tables in the tablespace.
- Write permission: If data needs to be written, the connection user must have the INSERT, UPDATE, and DELETE permissions on the destination table.
- Tablespace permissions: The connection user must have the required permissions to create and modify tables in the destination tablespace. This typically requires the UNLIMITED TABLESPACE permission.
- Role permissions: The connection user should have the CONNECT role permissions to connect to the database.

Selecting a Driver

Driver information

Relational Database Type	Driver Name	How to Obtain	Recommended Version
Oracle	ORACLE_6	Official Oracle website	ojdbc6.jar
Oracle	ORACLE_7	Official Oracle website	ojdbc7.jar
Oracle	ORACLE_8	Official Oracle website	ojdbc8.jar
Oracle	Historical versions	Maven repository	-

Description
- New versions (for example, Oracle Database 21c (21.3) drivers) are not supported. If they are used, the schema name cannot be obtained during job creation.
- The ojdbc8 12.2.0.1 version is recommended.

Supported Data Types

DataArts Migration supports the following field types and their common variants in Oracle 11c. This ensures that DataArts Migration can correctly read and write data.

Category	Field Type	Oracle Read	Oracle Write
Numeric	NUMBER	√	√
Numeric	SMALLINT	√	√
Floating number	BINARY FLOAT	√	√
	BINARY DOUBLE	√	√
	FLOAT	√	√
Character	CHAR	√	√
	NCHAR	√	√
	VARCHAR2	√	√
	NVARCHAR2	√	√
Time	DATE	√	√
	TIMESTAMP	√	√
	TIMESTAMP WITH TIME ZONE	√	√
	TIMESTAMP WITH LOCAL TIME ZONE	√	√
Large object	CLOB	√	√
	BLOB	x	x
	NCLOB	√	√
	BLOB	√	x
Other	RAW	√	√
	STRUCT	x	x
	ROWID	x	x
	UROWID	x	x
	INTERVAL DAY TO SECOND	x	x
	INTERVAL YEAR TO MONTH	x	x
	BFILE	x	x
	LONG	x	x
	LONG RAW	x	x

Supported Migration Scenarios

DataArts Migration supports the following offline synchronization modes:

Single table synchronization
DataArts Migration supports table/file synchronization in data ingestion into a data lake or data migration to the cloud.
Database and table shard synchronization
DataArts Migration supports synchronization of data from multiple databases and tables in data ingestion into a data lake or data migration to the cloud.
Entire DB migration
DataArts Migrations supports synchronization of data from an on-premises database in data ingestion into a data lake or data migration to the cloud.

Database and table shard synchronization and entire DB migration are not supported in all regions. The following table lists the supported Oracle migration scenarios.

Supported Migration Scenario	Oracle Single Table Read	Oracle Single Table Write	Oracle Database/Table Shard Read	Oracle Database/Table Shard Write	Oracle Entire DB Read	Oracle Entire DB Write
Supported	√	√	x	√	x	x

Core Capabilities

Connection configuration

Configuration Item	Supported	Description
User/AK	√	User authentication ensures connection security.
SSL encryption	x	SSL encryption ensures secure data transmission. Currently, this function is not supported.
SSL authentication	x	By default, certificate authentication is disabled.
Private certificate	x	Private certificates are not supported.
Connection configuration optimization	√	Connection configuration such as connectTimeout can be optimized to improve connection performance.
Custom driver	√	Custom drivers are supported and provide better flexibility.

Read capabilities

Configuration Item	Supported	Description
Shard concurrency	√	Horizontal sharding based on primary keys or common fields and multi-thread concurrent extraction significantly improve the throughput and efficiency.
Dirty data processing	√	Abnormal data can be written to the dirty data bucket to prevent job failures caused by a small amount of abnormal data.
Custom fields	√	You can add computed columns, constant columns, or masking functions for tasks to meet personalized service requirements.
Incremental read	√	Where conditions and the SQL mode enable incremental data reading.
Stream and batch reading	Batch reading	Batch reading improves efficiency when there is a small or medium amount of data.
Optimization of the number of rows read	√	You can set Fetch Size in the connection to properly control the amount of data to be transmitted. This improves performance and prevents a transmission delay or the system from being overloaded when there is a large amount of data.
View reading	√	Data can be read from views. This enables flexible data integration and processing.

Write capabilities

Configuration Item	Supported	Description
Data source optimization parameters	√	Optimization parameters such as batchSize and socketTimeout are supported at the source. They improve write performance.
Dirty data processing	√	Abnormal data can be written to the dirty data bucket to prevent job failures caused by a small amount of abnormal data.
Conflict resolution	x	The conflict resolution mechanism is not supported.
Pre- and post-import processing	√	Operations such as preSql and delete can clean and process data before and after data import.
Concurrent write	√	Concurrent write improves efficiency.
Optimization of the number of written rows	√	You can set the number of rows written by each request in the connection to properly control the amount of data to be transmitted. This improves performance and prevents a transmission delay or the system from being overloaded when there is a large amount of data. This function is not supported for this data source.