Oracle->GaussDB

**Table 1** Data type mapping
Source Data Type	Destination Data Type	Synchronization (Source Data Type as Primary Key)	Synchronization (Source Data Type as Non-Primary Key)	Comparison (Source Data Type as Primary Key)	Comparison (Source Data Type as Non-Primary Key)	Remarks
CHAR	CHARACTER	Supported	Supported	Supported. The spaces before and after the character are ignored.	Supported. The spaces before and after the character are ignored.	-
VARCHAR	CHARACTER VARYING	Supported	Supported	Supported	Supported	The precision ranges of the source and destination databases are different, causing precision loss.
VARCHAR2	CHARACTER VARYING	Supported	Supported	Supported	Supported	-
NCHAR	CHARACTER	Supported	Supported	Supported. The spaces before and after the character are ignored.	Supported. The spaces before and after the character are ignored.	-
NVARCHAR2	NVARCHAR2	Supported	Supported	Supported	Supported	-
NUMBER	NUMERIC	Supported	Supported	Supported	Supported	-
NUMBER (6,3)	NUMERIC(6,3)	Supported	Supported	Supported	Supported	-
NUMBER (6,0)	INTEGER	Supported	Supported	Supported	Supported	-
NUMBER (3)	SMALLINT	Supported	Supported	Supported	Supported	-
NUMBER (6,-2)	INTEGER	Supported	Supported	Supported	Supported	-
BINARY_FLOAT	REAL	Supported	Supported	Not supported	Supported	The precision ranges of the source and destination databases are different, causing precision loss.
BINARY_DOUBLE	DOUBLE PRECISION	Supported	Supported	Not supported	Supported	-
FLOAT	DOUBLE PRECISION	Supported	Supported	Not supported	Supported	The precision ranges of the source and destination databases are different, causing precision loss.
INT	NUMERIC	Supported	Supported	Supported	Supported	-
INTEGER	NUMERIC	Supported	Supported	Supported	Supported	-
DATE	TIMESTAMP(0) WITHOUT TIME ZONE	Supported	Supported	Not supported	Supported	If a table with date type is created in the destination database, the data type precision range in the source database is different from that in the destination database, causing precision loss. Therefore, comparison is not supported.
TIMESTAMP	TIMESTAMP(6) WITHOUT TIME ZONE	Supported	Supported	Not supported	The value is accurate to six decimal places.	The maximum precision supported by the source database is 6.
TIMESTAMP_TZ	TIMESTAMP(6) WITH TIME ZONE	Not supported (The source database does not support creating tables using the primary key.)	Supported	Not supported	Filter this column.	-
TIMESTAMP_LTZ	TIMESTAMP(6) WITH TIME ZONE	Not supported (The destination database does not support creating tables using the primary key.)	Supported	Not supported	Filter this column.	-
INTERVAL_YM	INTERVAL YEAR TO MONTH	Supported	Supported	Not supported	Not supported	Incremental synchronization does not support this type.
INTERVAL_DS	INTERVAL DAY TO SECOND	Supported	Supported	Not supported	Not supported	Incremental synchronization does not support this type. The maximum precision supported by the source database is 6.
BLOB	BLOB	Not supported (The source database does not support creating tables using the primary key.)	Supported	Not supported	Supported	You can choose to filter data or compare the length, hash, and content. During hash comparison, Oracle uses the hash function in the DBMS_CRYPTO package to obtain the LOB hash value. To use the DBMS_CRYPTO package, the SYSDBA needs to grant permissions to users. Reference statement: GRANT EXECUTE ON DBMS_CRYPTO TO USER;
CLOB	CLOB	Not supported (The source database does not support creating tables using the primary key.)	Supported	Not supported	Supported	You can choose to filter data or compare the length, hash, and content. During hash comparison, Oracle uses the hash function in the DBMS_CRYPTO package to obtain the LOB hash value. To use the DBMS_CRYPTO package, the SYSDBA needs to grant permissions to users. Reference statement: GRANT EXECUTE ON DBMS_CRYPTO TO USER;
NCLOB	TEXT	Not supported (The source database does not support creating tables using the primary key.)	Supported	Not supported	Supported	You can choose to filter data or compare the length, hash, and content. During hash comparison, Oracle uses the hash function in the DBMS_CRYPTO package to obtain the LOB hash value. To use the DBMS_CRYPTO package, the SYSDBA needs to grant permissions to users. Reference statement: GRANT EXECUTE ON DBMS_CRYPTO TO USER;
LONG	TEXT	No (The source database does not support creating tables using the primary key.)	Supported	Not supported	Filter this column.	-
LONG_RAW	BYTEA	Not supported (The source database does not support creating tables using the primary key.)	Supported	Not supported	Filter this column.	-
RAW	RAW	Supported	Supported	Not supported	Supported	-
ROWID	CHARACTER(18)	Supported	Supported	Supported	Supported	-
BFILE	-	Not supported	Not supported	Not supported	Not supported	Restrictions on the source database: The BFILE type is not supported.
XMLTYPE	TEXT	No (The source database does not support creating tables using the primary key.)	Yes	Not supported	Not supported	-
UROWID	-	Not supported	Not supported	Not supported	Not supported	Full and incremental synchronizations are not supported.
SDO_GEOMETRY	-	Not supported	Not supported	Not supported	Not supported	Restrictions on the source database: The SDO_GEOMETRY type is not supported.
NUMBER(*, 0)	NUMERIC	Supported	Supported	Supported	Supported	-