If you capture change data for tables in table spaces that are defined with the COMPRESS YES option, ensure that the DB2 subsystem to which the DB2 ECCR connects can access to the DB2 compression dictionary and the compressed table spaces and buffer pools for the source tables that are registered for CDC. To decompress data for PowerExchange requests, DB2 requires access to the compression dictionary that matches the DB2 log data.

DB2 might not be able to decompress data in the following circumstances:

Table-space locking by some DB2 utilities can prevent DB2 from accessing the compression dictionary. In this case, the ECCR ends abnormally. When the table-space lock is cleared, you can restart the ECCR to resume processing.

If you use DB2 for z/OS Version 11 new-function mode (NFM) or later, DB2 records old compression dictionaries in the DB2 log so that they remain available to decompress data when needed. You do not need to use the KEEPDICTIONARY option to retain them.

If you want the ECCR to skip any DB2 log records that contain data that DB2 cannot decompress and to continue capture processing, set the ROWNOTDECOMPRESSED parameter to NOFAIL in the DB2 ECCR REPL2OPT DD data set. For more information about the ROWNOTDECOMPRESSED parameter, see DB2 ECCR Configuration Statements in the REPL2OPT DD Data Set.