DB2 - Problem description
Problem IC76170 | Status: Closed |
DB2SUPPORT OPTIMIZER MODE WITHOUT -D <DBNAME> DOES NOT GATHER ANY OPTIMIZER SUPPORT DATA | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
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. 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 Summary: | |
**************************************************************** * 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> | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
V97FP5+ | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.05.2011 07.12.2011 07.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5+ | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |