|
Problem IC94161
|
Status: Closed |
Performance hit when a global variable is first referenced in a session |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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.1 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.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 10.1 FP3 |
| Workaround |
A work-around is to explicitly set the global variable to the
default value as the first reference in the session. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC96571
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.07.2013
07.10.2013
07.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
