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

TRAP IN sqljs_ddm_sndpkt WHEN AN APPLICATION CALLS db2DatabasePing OR
db2gDatabasePing

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
The DB2 client instance traps when an application calls 
db2gDatabasePing or db2DatabasePing for a database after the 
application has lost the connection to that database. 
 
The trap only happens if both of the following conditions are 
true: 
- the DB2 registry variable DB2CONNECT_IN_APP_PROCESS=NO on the 
database client; and 
- the database client does automatic client reroute. 
One reason that the database client would do automatic client 
reroute is if the database server is DB2 on z/OS with sysplex. 
 
 
When the trap happens, db2diag.log contains a sequence of 
messages like this: 
 
9999-99-99-99.99.99.999999+999 XXXXXXXXX          LEVEL: Warning 
PID     : 9999                 TID  : 9999        PROC : 
db2agentg (XXXXXXXX) 
INSTANCE: xxxxxxxx             NODE : 999 
APPHDL  : XXX                  APPID: XXXXXXXXXXXXXXXXXXXXXXXX 
AUTHID  : XXXXXXXX 
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrRetrySetup, 
probe:10 
MESSAGE : ZRC=0x81360012=-2127167470=SQLZ_RC_CMERR, SQLT_SQLJC 
          "External Comm error" 
DATA #1 : String, 30 bytes 
Client Reroute is starting.... 
 
9999-99-99-99.99.99.999999+999 XXXXXXXXX          LEVEL: Warning 
PID     : 9999                 TID  : 9999        PROC : 
db2agentg (XXXXXXXX) 
INSTANCE: xxxxxxxx             NODE : 999 
APPHDL  : XXX                  APPID: XXXXXXXXXXXXXXXXXXXXXXXX 
AUTHID  : XXXXXXXX 
FUNCTION: DB2 UDB, DRDA Application Requester, sqljrRetrySetup, 
probe:15 
DATA #1 : String, 50 bytes 
The correlation token of the failed connection is 
DATA #2 : String, 26 bytes 
XXXXXXXXXXXXXXXXXXXXXXXXXX 
 
9999-99-99-99.99.99.999999+999 XXXXXXXXX          LEVEL: Warning 
PID     : 9999                 TID  : 9999        PROC : 
db2agentg (XXXXXXXX) 
INSTANCE: xxxxxxxx             NODE : 999 
APPHDL  : XXX                  APPID: XXXXXXXXXXXXXXXXXXXXXXXX 
AUTHID  : XXXXXXXX 
FUNCTION: DB2 UDB, DRDA Application Requester, 
sqljrListToConnect, probe:20 
DATA #1 : String, 40 bytes 
Reconnecting to Hostname/IP Address --> 
DATA #2 : String, 14 bytes 
999.999.999.999 
DATA #3 : String, 45 bytes 
Reconnecting to Service name/Port number --> 
DATA #4 : String, 4 bytes 
9999 
 
9999-99-99-99.99.99.999999+999 XXXXXXXXX          LEVEL: Warning 
PID     : 9999                 TID  : 9999        PROC : 
db2agentg (XXXXXXXX) 
INSTANCE: xxxxxxxx             NODE : 999 
APPHDL  : XXX                  APPID: XXXXXXXXXXXXXXXXXXXXXXXX 
AUTHID  : XXXXXXXX 
FUNCTION: DB2 UDB, DRDA Application Requester, 
sqljrClientReroute, probe:998 
DATA #1 : String, 41 bytes 
Client Reroute is completed successfully. 
 
9999-99-99-99.99.99.999999+999 XXXXXXXXX          LEVEL: Warning 
PID     : 9999                 TID  : 9999        PROC : 
db2agentg (XXXXXXXX) 
INSTANCE: xxxxxxxx             NODE : 999 
APPHDL  : XXX                  APPID: XXXXXXXXXXXXXXXXXXXXXXXX 
AUTHID  : XXXXXXXX 
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, 
probe:1 
MESSAGE : Error in agent servicing application with coor_node: 
DATA #1 : Hexdump, 2 bytes 
0xBFD03EF2 : 9999 
 
[...] 
 
9999-99-99-99.99.99.999999+999 XXXXXXXXX          LEVEL: Warning 
PID     : 9999                 TID  : 9999        PROC : 
db2agentg (XXXXXXXX) 
INSTANCE: xxxxxxxx             NODE : 999 
APPHDL  : XXX                  APPID: XXXXXXXXXXXXXXXXXXXXXXXX 
AUTHID  : XXXXXXXX 
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, 
probe:10 
MESSAGE : ADM0503C  An unexpected internal processing error has 
occurred.  ALL 
          DB2 PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN 
SHUTDOWN. 
          Diagnostic information has been recorded.  Contact IBM 
Support for 
          further assistance. 
 
DATA #1 : Signal Number Recieved, 4 bytes 
11 
DATA #2 : Siginfo, 128 bytes 
0x99999999 : 9999 9999 9999 9999 9999 9999 9999 9999 
XXXXXXXXXXXXXXXX 
0x99999999 : 9999 9999 9999 9999 9999 9999 9999 9999 
XXXXXXXXXXXXXXXX 
0x99999999 : 9999 9999 9999 9999 9999 9999 9999 9999 
XXXXXXXXXXXXXXXX 
0x99999999 : 9999 9999 9999 9999 9999 9999 9999 9999 
XXXXXXXXXXXXXXXX 
0x99999999 : 9999 9999 9999 9999 9999 9999 9999 9999 
XXXXXXXXXXXXXXXX 
0x99999999 : 9999 9999 9999 9999 9999 9999 9999 9999 
XXXXXXXXXXXXXXXX 
0x99999999 : 9999 9999 9999 9999 9999 9999 9999 9999 
XXXXXXXXXXXXXXXX 
0x99999999 : 9999 9999 9999 9999 9999 9999 9999 9999 
XXXXXXXXXXXXXXXX 
0x99999999 : 9999 9999 9999 9999 9999 9999 9999 9999 
XXXXXXXXXXXXXXXX 
 
9999-99-99-99.99.99.999999+999 XXXXXXXXX          LEVEL: Warning 
PID     : 9999                 TID  : 9999        PROC : 
db2agentg (XXXXXXXX) 
INSTANCE: xxxxxxxx             NODE : 999 
APPHDL  : XXX                  APPID: XXXXXXXXXXXXXXXXXXXXXXXX 
AUTHID  : XXXXXXXX 
FUNCTION: DB2 UDB, DRDA Application Requester, 
sqljrSignalHandler, probe:10 
MESSAGE : DIA0505I Execution of a component signal handling 
function has begun. 
 
9999-99-99-99.99.99.999999+999 XXXXXXXXX          LEVEL: Severe 
PID:9999 TID:9999 NODE:999 Title: **** DRDA ARCB **** 
Dump File:XXXXXXXXXXXXXXXXXXXXXXXXXXXXX/99999999.999 
 
[...] 
 
Near the top of the function stack in the <StackTrace> section 
of the trap file that is written in the diagnostic data 
directory at the time of the trap are these functions: 
 sqljs_ddm_sndpkt 
 sqljsParseRdbAccessed 
 sqljsParse
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of DB2 for Linux, UNIX and Windows                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************
Local Fix:
As a workaround you can unset the DB2 registry variable 
DB2CONNECT_IN_APP_PROCESS=NO on the database client and then 
restart the database client instance.
available fix packs:
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
Problem was first fixed in Version 9.1 Fix Pack 11. 
At a minimum, this fix should be applied on the client instance.
Workaround
As a workaround you can unset the DB2 registry variable 
DB2CONNECT_IN_APP_PROCESS=NO on the database client and then 
restart the database client instance.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC77188 IC77189 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.06.2011
23.12.2011
23.12.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.11 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.