|
Problem IC78715
|
Status: Geschlossen |
ZERO LENGTH DRDA DDM MONITORRD CRASHES DB2 INSTANCE. |
| Produkt: |
DB2 CONNECT / DB2CONNCT / 950 - DB2 |
| Problembeschreibung: |
The instance may trap because of empty DRDA DDM MONITORRD
reply returned by the server.
The stack may look like as below. The defect causes memory
corruption can corrupt the stack.
sqlomcpy() ## Stack corrupted
sqljcReadBytes() ## Stack corrupted
sqljrParseMonitorRd() ## Stack corrupted
sqljrParseOpenSuccessReply() ## Stack corrupted
sqljrParseOpenQueryReply()
sqljrParse()
sqljrDrdaArOpen()
sqljs_ddm_opnqry()
sqljsParseRdbAccessed()
sqljsParse()
sqljsSqlam()
sqljsDriveRequests()
sqljsDrdaAsInnerDriver()
sqljsDrdaAsDriver()
RunEDU()
Trace buffer from zDB2 V10:
6132 data DB2 UDB DRDA Communication Manager sqljcIntReceive
fnc (3.3.54.4.0.1178)
6132 data DB2 UDB DRDA Communication Manager sqljcIntReceive
fnc (3.3.54.4.0.1178)
63C0 202000104C434E44 4444312020202020 ..LCNDDD1
....<.+.........
63D0 2020202000000000 FF000AD003000200 ............
...........}....
63E0 041C00
Trace Snippet:
6259 | | | | | | | | | | | sqljrParseMonitorRd entry
[eduid 5399 eduname db2agent]
6260 | | | | | | | | | | | | sqljcReadUint16Split entry
[eduid 5399 eduname db2agent]
6261 | | | | | | | | | | | | | sqljcReadDssContLen entry
[eduid 5399 eduname db2agent]
6262 | | | | | | | | | | | | | | pdLog entry [eduid 5399
eduname db2agent]
6263 | | | | | | | | | | | | | | | pdLogInternal entry
[eduid 5399 eduname db2agent]
6264 | | | | | | | | | | | | | | | | sqltGetDiagPath
entry [eduid 5399 eduname db2agent]
6265 | | | | | | | | | | | | | | | | sqltGetDiagPath data
[probe 10]
6266 | | | | | | | | | | | | | | | | sqltGetDiagPath exit
6267 | | | | | | | | | | | | | | | | pdIsFODCInProgress
entry [eduid 5399 eduname db2agent]
6268 | | | | | | | | | | | | | | | | pdIsFODCInProgress
exit
6269 | | | | | | | | | | | | | | | |
pdIsEduFODCInProgress entry [eduid 5399 eduname db2agent]
6270 | | | | | | | | | | | | | | | |
pdIsEduFODCInProgress exit
6271 | | | | | | | | | | | | | | | pdLogInternal exit
6272 | | | | | | | | | | | | | | pdLog exit
6273 | | | | | | | | | | | | | sqljcReadDssContLen exit
[rc = 0x87360009 = -2026504183 = SQLJC_ERROR_BEOF]
6274 | | | | | | | | | | | | sqljcReadUint16Split exit
[rc = 0x87360009 = -2026504183 = SQLJC_ERROR_BEOF]
6275 | | | | | | | | | | | | sqljcReadUint16Split entry
[eduid 5399 eduname db2agent]
6276 | | | | | | | | | | | | sqljcReadUint16Split exit
[rc = 0x87360009 = -2026504183 = SQLJC_ERROR_BEOF]
6277 | | | | | | | | | | | | sqloEDUCodeTrapHandler entry
[eduid 5399 eduname db2agent]
---------
An application may also receive the error message:
SQL0902C reason code = "9" SQLSTATE=58005
This error message would occur if the application is running on
the DB2 Connect server directly and if the db2set registry
parameter DB2CONNECT_IN_APP_PROCESS=NO is set. This specific
problem is related to this APAR and the issue is more prevalent
if a query is issued against the server that returns multiple
rows (possibly over 500 rows).
Removing DB2CONNECT_IN_APP_PROCESS=NO (or setting it to YES) may
workaround this particular instance of the issue. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All DB2 connect user using zDB2 V10. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v9.5.9 or higher version. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
V9.5.9 fixes the trap issue. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC79562 IC81612
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 15.09.2011
28.03.2012
15.05.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.5.9
|
| Problem behoben lt. FixList in der Version |
| 9.5.0.9
|
 |
