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 IC62973 Status: Closed

COMMAND "DB2STOP FORCE" MAY CAUSE A TRAP

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Issuing db2stop force command may cause a trap on db2 
v9.7. 
 
The trap occurred immediately after sqleKillNode sent SIGDUMP 
to all processes which. The following may appear in the 
 db2diag.log: 
 
2009-01-27-12.10.19.234088-300 I32874473E296 LEVEL: Severe 
PID : 2158 TID : 183095683680 PROC : db2stop2 
INSTANCE: db2inst1 NODE : 014 
FUNCTION: DB2 UDB, base sys utilities, sqleKillNode, probe:90 
MESSAGE : Sending sigdump and waiting for 1 min to complete 
 
2009-01-27-12.10.19.302308-300 E32874770E1515 LEVEL: Critical 
PID : 30054 TID : 183106529632 PROC : db2ckpwd 14 
INSTANCE: db2inst1 NODE : 014 
EDUID : 1 EDUNAME: db2sysc 14 
FUNCTION: DB2 UDB, oper system services, 
sqloEDUCodeTrapHandler,probe: 10 
MESSAGE : ADM14001C An unexpected and critical error has 
occurred: 
"Trap". The instance may have been shutdown as a result. 
"Automatic" FODC 
(First Occurrence Data Capture) has been invoked and diagnostic 
information 
has been recorded in directory 
"/var/ibmdb2/nyqxt150/sqllib/db2dump/". Please look in this 
directory 
for detailed evidence about what happened and contact IBM 
support if 
necessary to diagnose the problem. 
 
DATA #1 : 
Signal Number Recieved, 4 bytes 11 
 
From trap 
file 30054.1.014.trap.txt: 
*************************************** 
DB2 build information: DB2 v9.5.0.3 s081118 SQL09053 
timestamp: 2009-01-27-12.10.19.247235 
instance name: db2inst1.014 
EDU name : db2sysc 14 
EDU ID : 1 
Signal #11 
uname: S:Linux R:2.6.9-68.9.ELmsdwlargesmp V:#1 SMP Fri Feb 22 
18:47:03 
EST 2008 M:x86_64 N:np737c3n5 
process id: 30054 
thread id : 183106529632 (0x2AA1FFE960) 
</Header> 
<SignalDetails> 
. . . 
<StackTrace> 
---FUNC-ADDR---- ------FUNCTION + OFFSET------ 
0000002A9B7E6047 ossDumpStackTraceEx + 0x01f7 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2osse.so.1) 
0000002A9B7E1BBC _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm + 0x00b4 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2osse.so.1) 
0000002A9B7E1C83 _ZN11OSSTrapFile4dumpEmiP7siginfoPv + 0x0009 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2osse.so.1) 
0000002A97C93F5D sqlo_trce + 0x03f3 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A97CD9337 sqloEDUCodeTrapHandler + 0x0107 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A956784F0 address: 0x0000002A956784F0 ; dladdress: 
0x0000002A9566C000 ; offset in lib: 0x000000000000C4F0 ; 
(/lib64/tls/libpthread.so.0) 
0000002A956757C0 pthread_kill + 0x0000 
(/lib64/tls/libpthread.so.0) 
0000002A97CD9129 sqloUNIXSignalEDU + 0x0127 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A97CD9868 sqloDumpInstanceHandler + 0x003e 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A956784F0 address: 0x0000002A956784F0 ; dladdress: 
0x0000002A9566C000 ; offset in lib: 0x000000000000C4F0 ; 
(/lib64/tls/libpthread.so.0) 
0000002A9C16D326 msgrcv + 0x0066 
(/lib64/tls/libc.so.6) 
0000002A969FD0C2 
_Z16sqlorqueInternalP13SQLO_QUE_DESCP12SQLO_MSG_HDRii + 0x020e 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A969FCD71 sqlorque2 + 0x00c5 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A96A163F1 address: 0x0000002A96A163F1 ; dladdress: 
0x0000002A95782000 ; offset in lib: 0x00000000012943F1 ; 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A96A15E49 _Z20sqlockpw_daemon_initv + 0x0165 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A96A3729C address: 0x0000002A96A3729C ; dladdress: 
0x0000002A95782000 ; offset in lib: 0x00000000012B529C ; 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A96A36587 sqloRunInstance + 0x00cb 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
000000000040732F DB2main + 0x06cb 
(db2ckpwd 14) 
0000002A96A38F05 _Z16sqloEDUMainEntryPcj + 0x000f 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A96A39DCA sqloEDUEntry + 0x07fe 
 
(/ms/dist/ibmdb2/PROJ/ds/9.5.3.1/.exec/x86_64.linux.2.6.glibc.2. 
3/lib64/libdb2e.so.1) 
0000002A95672137 address: 0x0000002A95672137 ; dladdress: 
0x0000002A9566C000 ; offset in lib: 0x0000000000006137 ; 
(/lib64/tls/libpthread.so.0) 
0000002A9C16C113 __clone + 0x0073 
(/lib64/tls/libc.so.6) 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB version v9.5 or above installed systems.             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Issuing db2stop force command may cause a trap on db2        * 
* v9.7.Detailed Information:The trap might occur immediately   * 
* after sqleKillNode sendingSIGDUMP to all processes. The      * 
* following may appear in                                      * 
* thedb2diag.log:2009-01-27-12.10.19.234088-300 I32874473E296  * 
* LEVEL:SeverePID : 2158 TID : 183095683680 PROC               * 
* :db2stop2INSTANCE: nyqxt150 NODE : 014FUNCTION: DB2 UDB,     * 
* base sys utilities, sqleKillNode,probe:90MESSAGE : Sending   * 
* sigdump and waiting for 1 min to                             * 
* complete2009-01-27-12.10.19.302308-300 E32874770E1515        * 
* LEVEL:CriticalPID : 30054 TID : 183106529632 PROC :db2ckpwd  * 
* 14INSTANCE: nyqxt150 NODE : 014EDUID : 1 EDUNAME: db2sysc    * 
* 14FUNCTION: DB2 UDB, oper system                             * 
* services,sqloEDUCodeTrapHandler,probe:10MESSAGE : ADM14001C  * 
* An unexpected and critical error hasoccurred:"Trap". The     * 
* instance may have been shutdown as a result."Automatic" FODC * 
* (First Occurrence Data Capture) has beeninvoked and          * 
* diagnostic information has been recorded indirectory         * 
* "/var/ibmdb2/nyqxt150/sqllib/db2dump/". Pleaselook in this   * 
* directory for detailed evidence about whathappened and       * 
* contact IBM support ifnecessary to diagnose the              * 
* problem.<StackTrace>---FUNC-ADDR---- ------FUNCTION +        * 
* OFFSET------0000002A9B7E6047 ossDumpStackTraceEx +           * 
* 0x01f7(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2osse 
* _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm                       * 
* +0x00b4(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2oss 
* _ZN11OSSTrapFile4dumpEmiP7siginfoPv                          * 
* +0x0009(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2oss 
* sqlo_trce +                                                  * 
* 0x03f3(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* sqloEDUCodeTrapHandler +                                     * 
* 0x0107(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* address: 0x0000002A956784F0 ; dladdress:0x0000002A9566C000 ; * 
* offset in lib: 0x000000000000C4F0                            * 
* ;(/lib64/tls/libpthread.so.0)0000002A956757C0 pthread_kill + * 
* 0x0000(/lib64/tls/libpthread.so.0)0000002A97CD9129           * 
* sqloUNIXSignalEDU +                                          * 
* 0x0127(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* sqloDumpInstanceHandler +                                    * 
* 0x003e(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* address: 0x0000002A956784F0 ; dladdress:0x0000002A9566C000 ; * 
* offset in lib: 0x000000000000C4F0                            * 
* ;(/lib64/tls/libpthread.so.0)0000002A9C16D326 msgrcv +       * 
* 0x0066(/lib64/tls/libc.so.6)0000002A969FD0C2_Z16sqlorqueIntern 
* +0x020e(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.s 
* sqlorque2 +                                                  * 
* 0x00c5(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* address: 0x0000002A96A163F1 ; dladdress:0x0000002A95782000 ; * 
* offset in lib: 0x00000000012943F1                            * 
* ;(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so.1)00 
* _Z20sqlockpw_daemon_initv +                                  * 
* 0x0165(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* address: 0x0000002A96A3729C ; dladdress:0x0000002A95782000 ; * 
* offset in lib: 0x00000000012B529C                            * 
* ;(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so.1)00 
* sqloRunInstance +                                            * 
* 0x00cb(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* DB2main + 0x06cb(db2ckpwd 14)0000002A96A38F05                * 
* _Z16sqloEDUMainEntryPcj +                                    * 
* 0x000f(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* sqloEDUEntry +                                               * 
* 0x07fe(/PATH/.exec/x86_64.linux.2.6.glibc.2.3/lib64/libdb2e.so 
* address: 0x0000002A95672137 ; dladdress:0x0000002A9566C000 ; * 
* offset in lib: 0x0000000000006137                            * 
* ;(/lib64/tls/libpthread.so.0)0000002A9C16C113 __clone +      * 
* 0x0073(/lib64/tls/libc.so.6)</StackTrace>                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrading to DB2 UDB v9.7fp1 resolves this issue.            * 
****************************************************************
Local Fix:
There is no workaround, but as this problem occurred while DB2 
was shutting down, there is no harm done to your database. 
First Fixed in DB2 9.5 Fix Pack 5.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 UDB v95fp5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.09.2009
17.02.2010
17.02.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP5,
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList