Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC69480 Status: Closed

DB2TRC MAY HANG ENGINE WHEN IT IS INVOKED VIA A SCRIPT

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users invoking db2trc via script.                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When you issue "db2trc -f <filename>" to trace to a file,    * 
* abackground daemon process is started to act as the          * 
* tracerecord writer process.  When db2trc is turned on from   * 
* withina script, the daemon process still has an association  * 
* backto the script process.  So, when CTRL-C was issued       * 
* againstthe script, that CTRL-C got propagated to the trc     * 
* daemonprocess as well and so it terminated too.  Now since   * 
* thetrace record writer process is gone, all DB2 processes    * 
* whichstill want to write out trace records end up waiting    * 
* foreverto write a buffer that no longer exists.              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* The fix is a code change in db2trc source code that          * 
* simplyinvolves ignoring the SIGINT signal which gets sent to * 
* aprocess and its children when a user hits CTRL-C.  Now      * 
* whenCTRL-C is issued against the script, the trace           * 
* recordwriting daemon ignores the signal and stays alive      * 
* thusallowing all DB2 processes to continue to write          * 
* tracerecords.  db2trc can then be turned of                  * 
****************************************************************
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.
available fix packs:
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fix in V95 FP7
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69634 IC69635 IC69636 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.06.2010
01.11.2010
01.11.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.7 FixList
9.5.0.7 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.