|
Problem IC69012
|
Status: Closed |
ERROR MESSAGES IN THE DB2DIAG.LOG REPORTING LOCK HOLDING GENERATES LOCK DUMPS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Error messages in db2diag.log reports lock holding and dumps
stack and lock information like below:
2010-04-02-13.45.43.126676-300 I1805455E1197 LEVEL:
Warning
PID : 31140 TID : 47822187522368PROC :
db2sysc
INSTANCE: sample NODE : 000 DB : sample
APPHDL : 0-36 APPID: *LOCAL.xxxxx.100402184525
AUTHID : sample
EDUID : 18 EDUNAME: db2agent (sample)
FUNCTION: DB2 UDB, data protection services, sqlptrmv, probe:110
DATA #1 : <preformatted>
Transaction 2 still holds locks.
CALLSTCK:
[0] 0x00002B7E5F23AD6F pdLogPrintf + 0xE1
[1] 0x00002B7E5F63481A _Z8sqlptrmvP8sqeAgentPP11SQLP_TENTRY +
0x3D2
[2] 0x00002B7E5F635D61
_Z17sqlpEndUowRuntimeP8sqeAgentP9SQLP_DBCB + 0x5BD
[3] 0x00002B7E5F631988
/view/db2_v95fp5_linuxamd64_s091123/vbs/INST/lib/libdb2e.so.1 +
0x14C3988
[4] 0x00002B7E5F62FEAC
_Z8sqlpxrbkP8sqeAgentP15SQLXA_CALL_INFOPiP9SQLP_GXIDPP11sqlo_xla
tch
+ 0x4D8
[5] 0x00002B7E5F633320 _Z8sqlptfrgP8sqeAgentm + 0x1D0
[6] 0x00002B7E5F687D24 _Z15sqlrr_appl_termP8sqeAgentiP5sqlca +
0x35A
[7] 0x00002B7E5F332F6A
_ZN14sqeApplication12AppStopUsingEP8sqeAgenthP5sqlca + 0x314
[8] 0x00002B7E5F376CE8 _Z11sqlesrspWrpP14db2UCinterface + 0x96
[9] 0x00002B7E5F376F1B sqleUCagentConnectReset + 0xA1
2010-04-02-13.45.43.138313-300 I1806653E182 LEVEL: Error
PID:31140 TID:47822187522368 NODE:000 Title: SQLP_TENTRY
Dump File:/home/sample/sqllib/db2dump/31140.18.000.dump.bin
2010-04-02-13.45.43.138517-300 I1806836E829 LEVEL: Info
PID : 31140 TID : 47822187522368PROC :
db2sysc
INSTANCE: sample NODE : 000 DB : sample
APPHDL : 0-36 APPID: *LOCAL.xxxxx.100402184525
AUTHID : sample
EDUID : 18 EDUNAME: db2agent (sample)
FUNCTION: DB2 UDB, data protection services, sqlptrmv, probe:130
DATA #1 : SQLP_LOCKNAME, PD_TYPE_SQLP_LOCKNAME, 13 bytes
A59B0000000000000000000073 SQLP_SERVERNAME
DATA #2 : SQLP_LRB, PD_TYPE_SQLP_LRB, 64 bytes
state L next 0x(nil) rsInfoIdx 0
status G mode ..S dur 1 conv_mode ... conv_dur 0 tran_handl 2
holdcount 0 lrbExtFlag 0x00 lrbIntFlag 0x0000 chainNum 0
tran_chain 0x(nil) head_ptr 0x0x2b7e879ad800 awb_ptr 0x(nil)
Please note this issue is specific to federated environment. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Only federated users are effected *
****************************************************************
* PROBLEM DESCRIPTION: *
* Messages in the db2diag.log reporting lock holding creates *
* lock dumps. *
****************************************************************
* RECOMMENDATION: *
* Stack dumping could be reduced by increasing the *
* DB2_CON_UNREF_THRESHOLD. *
**************************************************************** |
| Local Fix: |
Stack dumping could be reduced by increasing the
DB2_CON_UNREF_THRESHOLD
alter server <servname> options(add DB2_CON_UNREF_THRESHOLD
'100000')
[use set instead of add if this option already exists] |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 |
First fixed in V9.7 Fixpack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.06.2010
27.09.2010
27.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
