|
Problem IT25986
|
Status: Closed |
DIAGNOSTICS DUMPING MAY HANG WHEN DUMPING PACKAGE CACHE INFORMATION
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When Db2's diagnostics dumping is triggered as a result of a
memory corruption issue it may dead-latch with itself as a
result of trying to allocate memory during the diagnostics
dumping process.
The signature latch information in db2pd -latch output will be
similar to:
0x00000001662DD5C0 374059 374059
/view/db2_v105fp8_aix64_s160901_special_36544/vbs/engn/include/s
qlo_mem_latch.h 67 SQLO_LT_SMemPool__MemLatchType__latch
1
and there will be evidence of an incomplete FODC run in the
DIAGPATH with the function "sqlra_cache_full_dump" appearing in
the stack trace.
The dead-latched EDU is also holding an
SQLO_LT_sqlra_anchor_stmt__latch (reported with holder 0 in
db2pd -latch output) which may result in other EDUs hanging too.
This APAR removes the attempt to allocate memory during
diagnostics dumping eliminating the dead-latch allowing
diagnostics dumping to complete.
Note that this doesn't impact the original issue for which the
diagnostics dumping was triggered. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* n/a *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 V11.1 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.08.2018
17.12.2019
17.12.2019 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
