|
Problem IC69635
|
Status: Closed |
DB2TRC MAY HANG ENGINE WHEN IT IS INVOKED VIA A SCRIPT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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: *
* 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. |
| available fix packs: |
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
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.07.2010
03.05.2011
03.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
