These behavior changes are related to loading data:
The LOAD_MEMORY_MB option has been deprecated. Instead of setting LOAD_MEMORY_MB, you must now adjust the IQ temporary cache setting. The amount to increase the IQ temporary cache is approximately the sum of all the LOAD_MEMORY_MB settings of all of the concurrent LOAD TABLE executions.
Sybase IQ does not support loading large object columns from primary files using the LOAD TABLE…FORMAT BINARY clause. You can load large object data in binary format from secondary files. See Unstructured Data Analytics in Sybase IQ > Large Object Data Load and Unload.
Users must be specifically licensed to use the large object data types LONG BINARY and LONG VARCHAR. For details on the Unstructured Data Analytics Option, see Unstructured Data Analytics in Sybase IQ.
The LOAD TABLE statement BLOCK FACTOR, BLOCK SIZE, and UNLOAD FORMAT clauses have been deprecated.
When binary data of hexadecimal format is loaded
into a LONG BINARY column from a primary file,
the total number of hexadecimal digits (nibbles) must be an even
number. The error “Odd length of binary data
value detected on column” is reported,
if the cell value contains an odd number of hexadecimal digits.
Input files for LONG BINARY loads should always
contain an even number of hexadecimal digits.
When loading VARBINARY and BINARY data type columns from a primary file, Sybase IQ prepends a 0 nibble when the number of hexadecimal digits is an odd number.
Partial-width loads and loads of rows spanning file boundaries by LOAD TABLE and INSERT have been deprecated in this version of Sybase IQ.
