|
Problem IC65687
|
Status: Closed |
DB2FMP (OR SQLJ) RETURNS ERROR IMPROPERLY CAUSING THE CORRESPONDING DB2AGENT TO TRAP WHILE WAITING FOR RESULT SET. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
Instance crashes with sigsegv and following stack:
?unknown + 0x0
sqlerRtnAgentProcessResSetsFenced + 0xA88
sqlerRtnReadFencedResultData + 0xA94
sqlerRtnReadFencedResultData + 0x70
sqlriInvokeInvoker + 0x194
sqlricall + 0xFC
sqlriSectInvoke + 0x1C
sqlrr_process_execute_request - 0x7E0
sqlrr_execute + 0x60
sqljsParseRdbAccessed + 0x934
sqljsParseRdbAccessed + 0xDC
sqljsParse + 0x414
sqljsSqlam + 0x220
sqljsDriveRequests + 0x98
sqljsDrdaAsInnerDriver + 0xE0
sqljsDrdaAsDriver + 0x13C
RunEDU+ 0x174
EDUDriver + 0x78
sqloEDUEntry + 0x32C
Error is not properly returned from the db2fmp in this case, who
was running the stored procedure on behalf of the agent who
crash, to this agent. This is what causes this agent to trap.
This APAR address the code that returns error from db2fmp
(sqlj) and has added debug code to the agent side to debug such
problems coming from other type of applications. For example,
you may see error such as below from db2fmp in the db2diag.log:
2009-11-13-07.54.36.320267 LEVEL: Error
PID : XXXXXX TID : XXXX PROC : db2fmp
(C) 0
INSTANCE: XXXXX NODE : XXX
EDUID : XXXX EDUNAME: db2fmp (C) 0
FUNCTION: DB2 UDB, database application extension for utili,
XXXXXXXXXXXXXXXXXXXe, probe:12145
DATA #1 : String, 6 bytes
XXXXXX
DATA #2 : String, 5 bytes
XXXXXX
DATA #3 : String, 18 bytes
XXXXXX
DATA #4 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1224 sqlerrml: 0
sqlerrmc:
sqlerrp : SQL09053
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 55032 |
| Problem Summary: |
**************************************************************
USERS EFFECTED:
All users of the db2fmp process.
**************************************************************
PROBLEM DESCRIPTION:
This APAR address the code that returns error from db2fmp
(sqlj) and has added debug code to the agent side to debug such
problems coming from other type of applications.
**************************************************************
RECOMMENDATION:
Upgrade to the latest DB2 9.5 fix pack.
************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in DB2 Version 9.5 fix pack 6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.01.2010
24.09.2010
10.01.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.,
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
