DB2 - Problem description
Problem IC96571 | Status: Closed |
Performance hit when a global variable is first referenced in a session | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
During the first reference of a global variable in a session, users may notice large increase in statement latency and significantly higher CPU usage due to the excessive direct IO when fetching data from the catalog table SYSIBM.SYSVARIABLES. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users of Global Variables * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 FP3 * **************************************************************** | |
Local Fix: | |
A work-around is to explicitly set the global variable to the default value as the first reference in the session. | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 10.5 FP3 | |
Workaround | |
A work-around is to explicitly set the global variable to the default value as the first reference in the session. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.10.2013 27.02.2014 27.02.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.3 | |
10.5.0.3 |