|
Problem IC94161
|
Status: Geschlossen |
Performance hit when a global variable is first referenced in a session |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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. |
| verfügbare FixPacks: |
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
|
| Lösung |
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-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC96571
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 16.07.2013
07.10.2013
07.10.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
