Data type conversions occur when Archive File data is accessed
by ODM.
- When code page translation of archived data to
UTF-8 is required, character column length may be extended 1.5 times
for NCHAR data or 3 times for single-byte character data, up to 32k.
However, if the total row size is greater than 32k, ODM may encounter
errors when joining or sorting data.
- VARBINARY columns are converted to BINARY columns.
The BINARY column data is padded with binary zeros to match the VARBINARY
column maximum data length. (For DB2® Linux and Windows the data is padded with ASCII spaces,
x'20'.)
- For MONEY, DECIMAL, or NUMERIC columns, if scale=0,
these data types are converted to int2 or int4. If precision <=31
and both scale>=0 and scale<=precision, these data types are
converted to NUMERIC(p,s), otherwise they are converted to BINARY_DOUBLE.
- NCLOBs are converted to CLOBs.
- For Oracle, NUMERIC columns without precision are
converted to BINARY_DOUBLE. Timestamps (including TZ and LZ) are converted
to ODBC timestamps.
- For Oracle and Informix®,
time intervals are converted to VARCHAR(30).
- For DB2 Linux and WINDOWS, LONGVARCHAR, LONGVARBINARY and
LONGVARGRAPHIC columns are converted to CLOBs or BLOBs.