home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC98078 Status: Geschlossen

OPTIMIZER DB2SUPPORT COLLECTION IS NOT SUCCESSFUL

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 FixPack 4                        * 
****************************************************************
Local-Fix:
Ensure the physical hostname is used in the db2nodes.cfg file 
(same as returned by 'hostname' command).
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 version 10.5 FixPack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.12.2013
09.09.2014
09.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList