home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC77214 Status: Closed

DB2 TRAPPED WITH SIGSEGV ON BACKUP THREAD (DB2BM) WITH
SQMLOCKEVENTS::COLLECTREQUESTORAPPINFO IN STACK TRACE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
This trap will be triggered in situations where DB2 have the new 
locking event monitor running, and there are lock conflicts in 
the path of a backup operation in progress, resulting in 
lockwait events.  Typical stack trace will be: 
 
Stack #1             Signal #11        Timestamp 
 
0        ossDumpStackTraceEx 
1        OSSTrapFile::dumpEx 
2        sqlo_trce 
3        sqloEDUCodeTrapHandler 
4        __pthread_mutex_cond_lock 
5        sqmLockEvents::collectRequestorAppInfo 
6        sqmLockEvents::collectLockEvent 
7        sqlplnfd 
8        sqlplrq 
9        SqlubTableLock::request 
10       sqlubReadSMS 
11       sqlubBMCont 
12       sqlubbuf 
13       sqleSubCoordProcessRequest 
14       sqeAgent::RunEDU 
15       sqzEDUObj::EDUDriver 
16       sqlzRunEDU 
17       sqloEDUEntry 
18       pthread_create@@GLIBC_2.2.5 
19       clone
Problem Summary:
Users Effected: 
 
Problem Description: 
DB2 TRAPPED WITH SIGSEGV ON BACKUP THREAD (DB2BM) WITH 
SQMLOCKEVENTS::COLLECTREQUESTORAPPINFO IN STACK TRACE 
 
Problem Summary: 
 
This trap will be triggered in situations where DB2 have the new 
 
locking event monitor running, and there are lock conflicts in 
the path of a backup operation in progress, resulting in 
lockwait events.  Typical stack trace will be: 
 
Stack #1             Signal #11        Timestamp 
 
0        ossDumpStackTraceEx 
1        OSSTrapFile::dumpEx 
2        sqlo_trce 
3        sqloEDUCodeTrapHandler 
4        __pthread_mutex_cond_lock 
5        sqmLockEvents::collectRequestorAppInfo 
6        sqmLockEvents::collectLockEvent 
7        sqlplnfd 
8        sqlplrq 
9        SqlubTableLock::request 
10       sqlubReadSMS 
11       sqlubBMCont 
12       sqlubbuf 
13       sqleSubCoordProcessRequest 
14       sqeAgent::RunEDU 
15       sqzEDUObj::EDUDriver 
16       sqlzRunEDU 
17       sqloEDUEntry 
18       pthread_create@@GLIBC_2.2.5 
19       clone
Local Fix:
disable the new lock event monitor (the monitor created with 
'CREATE EVENT MONITOR FOR LOCKING')
available fix packs:
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
defect  wsdbu00845928 
CSD     First fixed in DB2 UDB Version 9.7, FixPak 5 
module  engn_sqm
Workaround
Upgrade to DB2 Version Version 9.7, FixPak 5
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.06.2011
07.12.2011
07.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList