|
Problem IC62713
|
Status: Closed |
DB2SUPPORT UTILITY MAY NOT GATHER ALL OPTIMIZER-RELATED DIAGNOSTIC DATA WHEN DIAGPATH IS SET |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The DB2 problem analysis and environment collection utility
(db2support) may not gather all Optimizer-related diagnostic
data generated during its execution.
This can happen if the following conditions are satisfied:
- DB2 Database Manager (DBM) configuration parameter DIAGPATH
has been set, i.e., changed from its default value of NULL
- The -cl or -collect db2support option is specified with a
value greater than or equal to 2 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* The DB2 problem analysis and environment collection utility *
* (db2support) may not gather all Optimizer-related diagnostic *
* data generated during its execution. *
* *
* This can happen if the following conditions are satisfied: *
* - DB2 Database Manager (DBM) configuration parameter *
* DIAGPATH has been set, i.e., changed from its default value *
* of NULL *
* - The -cl or -collect db2support option is specified with a *
* value greater than or equal to 2 *
****************************************************************
* RECOMMENDATION: *
* - Upgrade to DB2 V9.7 FixPack 1 *
**************************************************************** |
| Local Fix: |
Manually collect the contents of the default diagnostic
information dump (db2dump) directory (see DIAGPATH in the DB2
Information Center for the location of the default db2dump
directory) in addition to the generated db2support output. |
| 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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 |
To workaround the issue manually collect the contents of the
default diagnostic information dump (db2dump) directory (see
DIAGPATH in the DB2 Information Center for the location of the
default db2dump directory) in addition to the generated
db2support output. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.08.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
|
 |
