When you compare data types across databases, if the corresponding Informatica native type differs in precision compared to the databases, you might see a mismatch.

If you compare a binary data type with data types such as string or decimal, you might see a mismatch.

When you compare the time data type across databases, you might see a mismatch because Informatica treats time as datetime and each database has a different default date.

Informatica treats the datetimeoffset data type as varchar (0). If you compare datetimeoffset values with datetime values, you might see a mismatch.

When you compare floating point data types across databases, the default exponential notation on each database might be different. You might see a mismatch in the case of large floating point numbers.

When you compare data between Oracle and Snowflake databases, if the Oracle database contains varchar data, you might see a mismatch. To prevent this issue, map Oracle varchar data to nvarchar2.

If an Oracle table stores Unicode data in an nvarchar column and you map the column to other databases with Unicode data, you might see a mismatch. The mismatch occurs because Oracle supports Unicode data only in its nvarchar2 data type.