DB2 FOR LUW / DB2FORLUW / A10 - DB2

When doing COMMIT to finish a transaction, DB2 agent receives 
SIGSEGV (segmentation violation) and then is stuck in signal 
handler. 
 
Following symptoms can help you identify the problem: 
 
1. The corresponding application stays in "Commit Active" status 
and can not be forced off. 
 
2. "FODC_Trap" directory is created with trap files and dump 
files, and the stack traces would be similar to the following: 
=========================================== 
sqlpgild 
sqlpWriteToLog 
sqlpWriteLR 
sqlptlog 
sqlpxcm1 
sqlrrcom_dps 
sqlrrcom 
sqlrr_commit 
=========================================== 
 
3. If a core dump file can be obtained for the 'db2sysc' 
process, the stack trace might be similar to the following: 
=========================================== 
sqlmStartIntervalWrapper 
pdLogInternal 
pdLogInternal 
pdLog 
sqleagnt_sigsegvh 
sqloEDUCodeTrapHandler 
sqlpgild 
sqlpWriteToLog 
sqlpWriteLR 
sqlptlog 
sqlpxcm1 
sqlrrcom_dps 
sqlrrcom 
sqlrr_commit 
=========================================== 
 
4. In 'db2pd -edu' output, the USR time continually increases 
indicated the EDU is looping. 
 
Since the application is holding log space and can not be forced 
off, a transaction log full (SQL0964C) error may ultimately be 
raised. 
 
The source of the issue is unclear from the existing diagnostic 
data. This APAR will enhance the available diagnostic data and 
will attempt to avoid the trap at the expense of some accurate 
time-spent monitor elements for the EDU.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 10.1 on Linux, Unix and Windows         * 
* platforms                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 LUW Version 10.1 Fix Pack 3 or higher levels.  * 
****************************************************************

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 LUW Version 10.1 Fix Pack 3.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

03.04.2013
31.10.2013
31.10.2013