|
Problem IC61857
|
Status: Closed |
DB2 SERVER RUNNING AS A GETAWAY TO ANOTHER LUW SERVER MAY TRAP IN SQLJSPARSEXASYNCCTL() WHILE RUNNING XA APPLICATION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
DB2 server accessed by an XA application doing many local
transactions may abort with a SEGV signal in
sqljsParseXASyncctl() function. This happens only when LUW
Server is used as a gateway to another LUW server.
The EDU which traps is db2agentg.
The problem is caused if the application had at least 3 internal
rollbacks for local transactions previously. For example
deadlocks (SQL0911) could cause such rollbacks.
A typical stack trace from the trap file may look like this:
<StackTrace>
-------Frame------ ------Function + Offset------
0x090000000278A0DC sqljsParseXASyncctl
0x0900000002789B28 sqljs_ddm_syncctl
0x0900000000DCB3A4 sqljsParseRdbAccessed
0x0900000000E03D54 sqljsParse
0x0900000000AC33F0 sqljsSqlam
0x0900000000B8CEF8 sqljsDriveRequests
0x0900000000B8CC04 sqljsDrdaAsInnerDriver
0x0900000000B8C98C sqljsDrdaAsDriver
0x0900000000B69850 RunEDU
0x0900000000B695B0 EDUDriver
0x0900000000B642EC sqloEDUEntry
</StackTrace>
Stack traceback can also contain following functions:
sqljsParseDrdaSyncctl
sqljs_ddm_syncct
sqljsParseRdbAccessed
sqljsParseP13sqljsDrdaAsCbP14db2UCinterface
sqljsDrdaAsDriver
sqeAgent
sqzEDU
sqlzRunEDU
sqloEDUEntry |
| Problem Summary: |
Users Affected: ALL
Problem Description: See Error Description.
Problem Summary: See Error Description. |
| Local Fix: |
If possible avoid using the DB2 LUW server as a gateway.
For example when accessing the database via a catalogued local
loopback you will be using the gateway. So in this case connect
to the local database directly and not via the loopback. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 UDB Version 9.7, FixPak 1 (build s091114) |
| Workaround |
see LOCAL FIX. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.07.2009
15.12.2009
20.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
