|
Problem IC75943
|
Status: Closed |
DB2TRC IN CASE OF A CRASH DUMPS BUFFER IN DB2INSTHOME/SQLLIB/DB2DUMP EVEN IF DIAGPATH IS DIFFERENT |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
db2trc in case of a crash dumps buffer in
DB2INSTHOME/sqllib/db2dump even if DIAGPATH is set to a
different directory.
This can cause issues as there's a high chance that customer
changed the DIAGPATH for a reason ( most probably disk space )
and would not like the DB2INSTHOME directory to run out of space
due to this file in the directory. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* When a trap occurs while the DB2 trace is on, the trace *
* buffer is dumped to ~DB2INSTANCE/sqllib/db2dump even if *
* DIAGPATH is pointing to a different directory. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.5 FP8 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
With this fix, the trace memory buffer will be dumped in the
DIAGPATH in case of a crash while trace is running.
Fixed in:
DB2 v9.5 FP8 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC75990
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.04.2011
22.08.2011
22.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
