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

DB2 INSTANCE MAY CRASH IN SQLODB2NAMESPACE()

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
If you have an environment with multiple DB2 instances 
databases and catalogued your databases with local 
node, the DB2 instance can crash in  the function 
sqloDB2Namespace() during some database operations. 
 
Basically, the affected scenario includes any cross-copy local 
connect, when extended security is on. 
 
This is an example of the stack that you can get : 
 
<StackTrace> 
<sqloDB2Namespace> <NotFound:-1> 
<sqlccipcconnr> <sqlccipc.C:1554> 
<sqlccconnr> <sqlcccmn.C:1799> 
<sqljcCommConnect> <sqljcmn.C:2341> 
<sqljcCmnMgrInit> <sqljcmn.C:298> 
<sqljrCreateTransport> <sqljrcomm.C:2052> 
<sqljrAssociateTransport> <sqljrclient.C:2419> 
<sqljrInternalConnect> <sqljrcomm.C:996> 
<sqljrFindBestAddressAndConnect> <sqljrcomm.C:1998> 
<sqljrDrdaArAuthenticate> <sqljrsec.C:169> 
<sqlexAppAuthenticate> <sqlexsmc.C:1414> 
<sqljrDrdaArConnect> <sqljrintrfc.C:340> 
<sqleUCdrdaARinit> <sqleu_common.C:446> 
<sqleUCappConnect> <sqleu_client.C:3840> 
<sqlxaConnect> <sqlxapi.C:5121> 
<sqlxa_open> <sqlxapi.C:2842> 
<sqlxa_open2> <sqlxapi.C:2563> 
<DRDA_Connection::xa_open> 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW with federated databases                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP5 or above                              * 
****************************************************************
Local Fix:
catalog the node as TCPIP instead of LOCAL
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
The problem was first fixed in DB2 9.7 FP5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.03.2011
02.01.2012
17.05.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList