Data compression dictionary is not automatically created
You have a large table or a large XML
storage object for the table, but the data compression dictionary
was not created. You would like to understand why the creation of
the data compression dictionary did not occur as you were expecting.
This information applies to both the compression dictionary for the
table object and the compression dictionary for the XML storage object.
Data replication process cannot decompress a compressed row image
There are known situations that may occur
which result in a data replication solution being unable to successfully
decompress a log record with a compressed row image. For transient
(temporary) errors, the SQL code returned will correspond to the cause
of the error, while a permanent error is typically signalled by a
SQL0204N notification. Only transient error situations might result
in a subsequent successful decompression of a row image in a log record.
The db2ReadLog API will continue processing other
log records even if it cannot decompress a log record.