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

DB2 CONNECT SERVER MAY TRAP IN A CLIENT REROUTE CONFIGURATION.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
Under rare cirucumstances, the DB2 Connect Server may trap in a 
Client Reroute configuration.  The following conditions must be 
met: 
 
1) The application connects with explicit Trusted Connection 
andif the switch user request is made from the explicit trusted 
connection. 
2) DB2 Connect Server configured for concentrator. 
3) The database server supports Client Reroute or Sysplex. 
4) Primary and alternate ( or all members of sysplex groups) 
areunavailable. 
 
The server (behaving as a gateway) could trap if during a 
Trusted Context switch user  request the connection between the 
agent and the server is broken and the reroute server is also 
unavailable.   The following stack trace will be in stack dump. 
It is extremely difficult to hit this problem asthe window of 
opporitunity is extremely small and it would also required that 
all the other servers are unavailable. 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x090000001F81DEB4 
sqljrPostErrorProcessing__FP13sqljrDrdaArCbP14db2UCinterfacei + 
0x244 
0x090000001F7CB25C 
sqljrDrdaArTrustedSwitchUser__FP14db2UCinterface + 0x320 
0x090000001F7A0FCC 
sqleUCagentDrdaArTrustedSwitchUser__FP14db2UCinterface + 0x190 
0x0900000023B6A4B8 sqljsTrustedSwitchUser__FP14db2UCinterface + 
0x1C8 
0x0900000023B769B0 
sqljs_ddm_secchk__FP14db2UCinterfaceP14sqljsDDMObject + 0x228 
0x0900000023B88084 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP14sqljsDDMObjectP14db2U 
Cinterface 
+ 0x380 
0x0900000023B8930C 
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterface + 0x1EC 
0x0900000023B4980C 
sqljsSqlam__FP14db2UCinterfaceP13sqle_agent_cbb + 0x3C4 
0x0900000023B4CF14 
sqljsDriveRequests__FP13sqle_agent_cbP11UCconHandle + 0x2C4 
0x0900000023B4816C 
sqljsDrdaAsInnerDriver__FP17sqlcc_init_structb + 0x2D8 
0x0900000023B47CA8 sqljsDrdaAsDriver__FP17sqlcc_init_struct + 
0x110 
0x090000001F36F158 sqleRunAgent__FPcUi + 0x57C 
0x090000001EE5E000 
sqloCreateEDU__FPFPcUi_vPcUlP13SQLO_EDU_INFOPi + 0x354 
0x090000001EE5F1E4 sqloRunGDS__Fv + 0x2B0 
0x090000001EE5E67C sqloInitEDUServices + 0x3D0 
0x090000001EEE58AC 
sqloSystemControllerMain__FCUiPFv_iPFi_vPPvCPi + 0x574 
0x090000001EEE4734 sqloRunInstance + 0x12C 
0x0000000100002D2C DB2main + 0xA9C 
0x00000001000042CC main + 0x24 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Connect Server on all Linux, Unix and Windows        * 
* platforms at service levels from Version 9.1 GA through to   * 
* Version 9.1 Fix Pack 7.                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.1 Fix Pack 8 or see "Local Fix"     * 
* portion for other suggestions.                               * 
****************************************************************
Local Fix:
The change with the least impact would be to not use 
concentrator.
available fix packs:
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
The complete fix for this problem first appears in DB2 Version 
9.1 Fix Pack 8 and all the subsequent Fix Packs.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC63904 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.06.2009
05.10.2009
05.10.2009
Problem solved at the following versions (IBM BugInfos)
9.1.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.8 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.