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

IGNORE SIGIO ON LINUX AFTER INITIAL DATA COLLECTION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The SIGIO signal (number 29) is not used by DB2 on linux.  To 
prevent the default action of process termination, DB2 will 
ignore SIGIO after an initial data collection. 
 
The first time a SIGIO signal is received, db2 will generate 
some diagnostic data and continue running.  Subsequent SIGIO 
signals will be ignored by the process.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Linux.                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The SIGIO signal (number 29) is not used by DB2 on linux.    * 
* To                                                           * 
* prevent the default action of process termination, DB2 will  * 
*                                                              * 
* ignore SIGIO after an initial data collection.               * 
*                                                              * 
* The first time a SIGIO signal is received, db2 will generate * 
*                                                              * 
* some diagnostic data and continue running.  Subsequent SIGIO * 
*                                                              * 
* signals will be ignored by the process.                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fix Pack 1 or later.                  * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 9.7 Fix Pack 1.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.10.2009
16.12.2009
16.12.2009
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList