suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT38665 Status: Closed

SNAPSHOT MONITOR TRAPPED IN FUNCTION SQLPLGETLOCKWAITINFO()

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
When collecting monitoring data via the GET SNAPSHOT command,
there is a small timing window that can cause Db2 server to
trap.  The following is a sample stack for this trap.


-----Frame------ ------Address----- ------Function +
Offset------
0x00001019E67EA6E0 0x000010000E305510
_Z20sqlplGetLockWaitInfoPK14sqeApplicationP9sqeBsuEduP8sqeAgentj
PjP14sqlm_timestampP8SQLP_LRBP18sqlm_int_lock_waitPmS6_RK8sqlo_g
mtb + 0x0690
  ( = offset 0xDF95510 in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EA9F0 0x000010000C1936F8
_Z20sqm_write_lock_waitsP14sqeApplicationPK16sqm_agent_entityPK1
6sqeLocalDatabasejRK8sqlo_gmtP19sqm_snapshot_bufferPjP14sqlm_tim
estampPmSC_SF_hP16sqlm_header_info + 0x04d8
  ( = offset 0xBE236F8 in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EAE60 0x000010000C199110
  ( = offset 0xBE29110 in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EAFE0 0x000010000C183CC4
  ( = offset 0xBE13CC4 in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EB090 0x000010000C180AEC
  ( = offset 0xBE10AEC in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EC340 0x000010000C176AE4
_Z12sqlmonssagntj13sqm_entity_idP6sqlmaijPvP14sqlm_collectedttP5
sqlca + 0x2cb4
  ( = offset 0xBE06AE4 in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67ED500 0x000010000C152318
_Z20sqlmPdbRequestRouterP8sqeAgent + 0x0a18
  ( = offset 0xBDE2318 in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EDAB0 0x000010000B2AE040
  ( = offset 0xAF3E040 in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EDD10 0x000010000B2A76F8
_Z21sqleProcessSubRequestP8sqeAgent + 0x22c8
  ( = offset 0xAF376F8 in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EE120 0x000010000B328608 _ZN8sqeAgent6RunEDUEv +
0x09d8
  ( = offset 0xAFB8608 in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EE2F0 0x000010001082FFBC _ZN9sqzEDUObj9EDUDriverEv
+ 0x025c
  ( = offset 0x104BFFBC in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EE3B0 0x000010001082FD3C _Z10sqlzRunEDUPcj + 0x001c
  ( = offset 0x104BFD3C in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EE3D0 0x000010000E2761E8 sqloEDUEntry + 0x09c8
  ( = offset 0xDF061E8 in
/head/home/db2inst1/sqllib/lib64/libdb2e.so.1)
0x00001019E67EE790 0x0000100000088AF4
  ( = offset 0x8AF4 in /lib64/libpthread.so.0)
0x00001019E67EEA10 0x0000100016CC8814 clone + 0x00e4
  ( = offset 0x128814 in /lib64/libc.so.6)
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* AIX/Linux                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade db2 to v11.5.4.0 and above                           *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* AIX/Linux                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade db2 to v11.5.4.0 and above                           *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.10.2021
12.10.2021
12.10.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)