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 IC97756 Status: Closed

OPTIMIZER DB2SUPPORT COLLECTION IS NOT SUCCESSFUL

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Collection of an optimizer support output is not successful if 
physical host name is not used in the db2nodes.cfg. 
 
e.g. running the following command: 
 
db2support -d SAMPLE -c -s -f -sf statement1.txt -ol 5 -cs 
db2usr 
 
fails with warning: 
 
Output file is "/db2/db2ra2/db2support.zip" 
Optimizer data collection failed 
Error invoking "optimizer mode on CF-only host"
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 FixPack 4                        * 
****************************************************************
Local Fix:
Ensure the physical hostname is used in the db2nodes.cfg file 
(same as returned by 'hostname' command).
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 FixPack 4
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC98078 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.11.2013
03.06.2014
03.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList