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 IC69635 Status: Geschlossen

DB2TRC MAY HANG ENGINE WHEN IT IS INVOKED VIA A SCRIPT

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
db2trc may hang engine when it is invoked via a script. 
 
Reason for hang 
 
When you issue "db2trc -f <filename>" to trace to a file, a 
background daemon process is started to act as the trace record 
writer process.  When db2trc is turned on from within a script, 
the daemon process still has an association back to the script 
process.  So, when CTRL-C was issued against the script, that 
CTRL-C got propagated to the trc daemon process as well and so 
it terminated too.  Now since the trace record writer process is 
gone, all DB2 processes which still want to write out trace 
records end up waiting forever to write a buffer that no longer 
exists.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Unix users                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* db2trc may hang engine when it is invoked via a script.      * 
*                                                              * 
*                                                              * 
*                                                              * 
* Reason for hang                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* When you issue "db2trc -f <filename>" to trace to a file, a  * 
* background daemon process is started to act as the trace     * 
* record writer process.  When db2trc is turned on from within * 
* a script, the daemon process still has an association back   * 
* to the script process.  So, when CTRL-C was issued against   * 
* the script, that CTRL-C got propagated to the trc daemon     * 
* process as well and so it terminated too.  Now since the     * 
* trace record writer process is                               * 
* gone, all DB2 processes which still want to write out trace  * 
* records end up waiting forever to write a buffer that no     * 
* longer exists.                                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP 4                                         * 
****************************************************************
Local-Fix:
Do a "db2trc off" at any command prompt first and then CTRL-C 
the script after it is confirmed that db2trc is off.
verfügbare FixPacks:
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 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
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.07.2010
03.05.2011
03.05.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList