DB2 - Problembeschreibung
Problem IC76170 | Status: Geschlossen |
DB2SUPPORT OPTIMIZER MODE WITHOUT -D <DBNAME> DOES NOT GATHER ANY OPTIMIZER SUPPORT DATA | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
db2support options -st, -sf, -se, or -cl with -d <dbname> will invoke optimizer mode, sometimes the user could forget to issue -d <dbname> along with these options, so no optimizer data would be collected in such case. E.g. "db2support -cl 0" only collects normal DB2 system info without any optimizer data. In order to actually gather optimizer support information, "db2support -d <dbname> -cl 0" must be used. With this fix, db2support will give a syntax error and terminate. E.g. $ db2support -cl 0 Error: the database name needs to be specified for -st, -sf, -se or -cl option. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * N/A * **************************************************************** * PROBLEM DESCRIPTION: * * db2support options -st, -sf, -se, or -cl with -d <dbname> * * will invoke optimizer mode, sometimes the user could forget * * to issue -d <dbname> along with these options, so no * * optimizer data would * * be collected in such case. * * * * For example, "db2support -cl 0" only collects normal DB2 * * system info without any optimizer data. In order to actually * * gather optimizer support information, "db2support -d * * <dbname> -cl 0" must be used. * **************************************************************** * RECOMMENDATION: * * Upgrade to V97FP5+ * **************************************************************** | |
Local-Fix: | |
Re-issue db2support optimizer options with -d <database name> | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
V97FP5+ | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.05.2011 07.12.2011 07.12.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5+ | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |