home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC86290 Status: Geschlossen

DB2 APPLICATION MIGHT BE STUCK IN "COMMIT ACTIVE" STATUS.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.7 on Linux, Unix and Windows          * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 LUW Version 9.7 Fix Pack 8 or higher levels.   * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 LUW Version 9.7 Fix Pack 8.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC91277 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.09.2012
06.05.2013
06.05.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP8
Problem behoben lt. FixList in der Version
9.7.0.8 FixList