|
Problem IC72485
|
Status: Closed |
Package cache size growing far beyond configured size while "db2pd -dyn" showing a lot of dynamic variations in X mode |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Inoperative (X mode) variations could happen when an application
is executing a variation where S-lock is held. When one of the
dependent objects of this var has been dropped we put an X lock
on it to invalidate it and mark it as inoperative to prevent
further access. At the end of invalidation, the X lock is not
released as we had a S-lock already in place. This
medium-duration X lock will prevent the var from being cleaned
by the cache space management function. This could cause the
instance to hung in the long run.
One of the main characteristics of this issue will be 'db2pd
-dyn' showing a lot of X mode vars in the Val column. I.e.
Dynamic SQL Variations:
Address AnchID StmtUID EnvID VarID NumRef Typ Lockname
Val Insert Time Sect Size
0x00002AACFA9676A0 126 22 1051 1 5 4 160000001B0400000100C00F56
X 2010-11-04-07.39.14.532097 1173752 |
| Problem Summary: |
|
| Local Fix: |
As a workaround run: db2 flush package cache dynamic |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Comment |
08279,7TD |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.11.2010
29.04.2011
01.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
