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

IN DPF, DB2 TRAPS IN sqeDBMgr::LocalDeactivate IF A NODE FAILS AND THAT
NODE IS THE CATALOG NODE FOR SOME DATABASE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In a DPF environment if an instance has multiple databases 
having different catalog nodes, for example: 
 
db2 list db directory | egrep "Database name|Catalog" 
Database name                        = SAMP1 
Catalog database partition number    = 0 
Database name                        = SAMP2 
Catalog database partition number    = 1 
 
And a node fails which is the catalog node for one of the 
databases (for example, node 0 or 1 above), db2 can trap with 
the following callstack: 
 
ossDumpStackTraceEx 
OSSTrapFile::dumpEx 
sqlo_trce 
sqloEDUCodeTrapHandler 
__pthread_mutex_cond_lock 
sqeDBMgr::LocalDeactivate 
sqleSubRequestRouter 
sqleProcessSubRequest 
sqeAgent::RunEDU 
sqzEDUObj::EDUDriver 
sqlzRunEDU 
sqloEDUEntry 
pthread_create@@GLIBC_2.2.5 
clone
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See SYSROUTE APARs to verify where this problem is being     * 
* addressed                                                    * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.07.2016
28.04.2017
28.04.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)