|
Problem IT01393
|
Status: Closed |
A HANG RELATED TO STMM MAY BE ENCOUNTERED SHOULD AN INTERNAL COUNTER TRACKING SHARED SORT HEAP PAGES BECOME NEGATIVE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In the unlikely event of the STMM internal counter for
certain shared sort heap pages becoming negative, a hang may be
encountered with an agent stuck whilst reserving shared sort
space.
For this to apply STMM sort heap tuning and shared sorting must
be enabled.
The hang will be characterised by an EDU with the top frames
of its stack similar to:
(the top frame may not appear in all stacks taken for the EDU)
ossFetchAndAdd64
stmmRegisterReserveSharedSortSpace
stmmReserveUnthrottledSharedSortSpace
sqlsReserveSharedSortSpace
...
whilst holding the SQLO_LT_stmmSort__mainLatch latch and the
db2stmm EDU stuck waiting to acquire this latch. Other EDUs
will be similarly waiting for this latch.
As with all hangs, several stack traces should be gathered for
all EDUs to confirm a hang before matching with a known issue.
You will also be able to observe no change in the latch holder
in repeated "db2pd -latch" command outputs. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 4 *
**************************************************************** |
| Local Fix: |
Disable automatic SORT tuning. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Upgrade to DB2 Version 10.1 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.04.2014
19.08.2014
19.08.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
