home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC63967 Status: Closed

IGNORE SIGIO ON LINUX AFTER INITIAL DATA COLLECTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
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.
Problem Summary:
**************************************************************** 
* 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:
available fix packs:
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

Solution
Problem was first fixed in Version 9.7 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
16.12.2009
16.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList