Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC71279 Status: Closed

DB2READLOGFILTERDATA RETURNS FALSE SQL0204N CAUSING UNNECESSARY FULL
REFRESH DURING REPLICATION

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
In certain scenarios, the db2ReadLog API could return the 
db2ReadLogFilterData structure pre-pended to the log record with 
the "sqlcode" field incorrrectly set to -204. This false error 
message might cause some replication solutions to perform an 
unnecessary full refresh. This error can happen when all of the 
follow criteria are true: 
- The registry variable DB2_LOGGING_DETAIL is set to either 
APPLINFO or AUTHID 
- The iFilterOption field in the db2ReadLog API is set to 
DB2READLOG_FILTER_ON 
- The transaction belongs to a table which has both DATA CAPTURE 
CHANGES and compression enabled.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In certain scenarios, the db2ReadLog API could return the    * 
* db2ReadLogFilterData structure pre-pended to the log record  * 
* with the "sqlcode" field incorrrectly set to -204. This      * 
* false error message might cause some replication solutions   * 
* to perform an unnecessary full refresh. This error can       * 
* happen when all of the follow criteria are true:             * 
* - The registry variable DB2_LOGGING_DETAIL is set to either  * 
* APPLINFO or AUTHID                                           * 
* - The iFilterOption field in the db2ReadLog API is set to    * 
* DB2READLOG_FILTER_ON                                         * 
* - The transaction belongs to a table which has both DATA     * 
* CAPTURE CHANGES and compression enabled.                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.8 Fix Pack 3                        * 
****************************************************************
Local Fix:
If an sqlcode -204 error is found, check the log record type in 
the log manager log record header. If the record type is "0x0069 
- Information Only" OR "0x008B - Application Information", the 
sqlcode can be safely ignored.
available fix packs:
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Problem was fixed in DB2 Version 9.8 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.09.2010
10.01.2011
10.01.2011
Problem solved at the following versions (IBM BugInfos)
9.8.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.3 FixList