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 IT20404 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 / B10 - 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:                                              *
* Upgrade to DB2 11.1 Mod1 Fix Pack 1 iFix001                  *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT16127 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.04.2017
01.05.2017
01.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)