DB2 - Problem description
Problem IC66963 | Status: Closed |
FREQUENT SQLESETI() OR SETDB2CLIENT TYPE API CALLS IN APPL. CAUSING EXTENDED COMPILING STATE AND FILLING THE PKGCACHE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problem description: | |
This APAR is similar to APAR IZ14287. However, APAR IZ14287 is not considering the "SET CLIENT ... <empty string>" as a reasonable valid SET request, hence not covering this case and causing the SET requests with empty string to fill the package cache and affecting the performance. With this APAR fix, caching SET stmt even its input is empty string will be bypassed. | |
Problem Summary: | |
FREQUENT SQLESETI() OR SETDB2CLIENT TYPE API CALLS IN APPL. CAUSING EXTENDED COMPILING STATE AND FILLING THE PKGCACHE | |
Local Fix: | |
Try to avoid submitting frequent SET CLIENT stmt if possible. | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows | |
Solution | |
LOCAL FIX: Try to avoid submitting frequent SET CLIENT stmt if possible. Fixed in DB2 V91Fp10 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC66997 IC67000 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.03.2010 14.06.2011 14.06.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.10 |