|
Problem IC70833
|
Status: Closed |
A MEMORY CORRUPTION WHEN WRITING AN ERROR MESSAGE FOR USEREXIT. THIS CAN CAUSE DB2 TO CRASH WITH SIGSEGV. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
A memory corruption when writing an error message for userexit.
This can cause DB2 to crash with SIGSEGV. This corruption is
known to happen in the sqlufrol function and may be possible in
other functions. An FODC directory will be created in which the
agent receiving SIGSEGV may have a truncated stack.
An error message like the following may be seen in the
db2diag.log:
2010-08-13-17.00.11.162122-420 I1036874E498 LEVEL: Warning
PID : 10214 TID : 1456 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-1466 APPID:
*LOCAL.db2inst1.100813235706
AUTHID : DB2INST1
EDUID : 1456 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlufrol,
probe:8181
MESSAGE : The rollforward recovery phase completed with a return
code of
-2112880618 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Customers using LOGARCHMETH=USEREXIT *
****************************************************************
* PROBLEM DESCRIPTION: *
* A memory corruption when writing an error *
* messageforuserexit.This can cause DB2 to crash with SIGSEGV. *
* Thiscorruptionmay be possible inother functions. An *
* FODCdirectory will be created in whichtheagent receiving *
* SIGSEGVmay have a truncated stack.An error message like *
* thefollowing may be seen *
* inthedb2diag.log:2010-08-13-17.00.11.162122-420 *
* I1036874E498LEVEL:WarningPID : 10214 TID *
* : 1456PROC :db2sysc0INSTANCE: db2inst1 NODE : *
* 000DB : SAMPLEAPPHDL : *
* 0-1466APPID:*LOCAL.db2inst1.100813235706AUTHID : *
* DB2INST1EDUID :1456 EDUNAME: db2agent *
* (SAMPLE) 0FUNCTION:DB2 UDB, data protection *
* services,sqlufrol,probe:8181MESSAGE : The rollforward *
* recovery phasecompleted with areturncode of-2112880618 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 Fixpack 7. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 Fixpack 7. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC71796 IC76082
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2010
10.01.2011
31.10.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.7
|
 |
| 9.5.0.7
|
|
