Checking Whether the Source Database Contains Unsupported Table Field Types

**Table 1** Checking whether the source database contains unsupported table field types
Check Item	Whether the source database contains unsupported table field types
Description	Check whether the source database contains unsupported table field types.
Failure Cause and Handling Suggestion	Failure cause: The source database contains unsupported table field types. The following table field types are supported: VARCHAR, VARCHAR2, NVARCHAR2, NUMBER, FLOAT, LONG, DATE, BINARY_FLOAT, BINARY_DOUBLE, RAW, LONG RAW, CHAR, NCHAR, CLOB, NCLOB, BLOB, ROWID, TIMESTAMP, TIMESTAMP WITH TIME ZONE and TIMESTAMP WITH LOCAL TIME ZONE. Handling suggestion: Select other tables that can be synchronized.

**Table 2** Checking whether the source database contains unsupported table field types
Check Item	Whether the source database contains unsupported table field types
Description	Check whether the source database contains unsupported table field types.
Failure Cause and Handling Suggestion	Failure cause: The source database contains unsupported table field types. The following table field types are not supported: xml, geometry, point, lineString, polygon, geometrycollection, multipoint, multilinestring and multipolygon. Handling suggestion: Delete the columns containing the unsupported field types. Alternatively, do not synchronize the tables containing the unsupported table field types.

**Table 3** Checking whether the source database contains unsupported table field types
Check Item	Whether the source database contains unsupported table field types
Description	The following table field types are not supported: geometry, point, lineString, polygon, geometrycollection, multipoint, multilinestring, and multipolygon. The source database contains unsupported table field types, resulting in migration failures.
Failure Cause and Handling Suggestion	Failure cause: The source database contains unsupported table field types. Handling suggestion: Delete the columns containing the unsupported field types. Alternatively, do not migrate the table containing the unsupported table field types.