|
Problem IC71072
|
Status: Closed |
DB2DIAG -FAC OPTSTATS DOES NOT WORK WHEN DB2_OPTSTATS_LOG WAS SET TO A NEW DIRECTORY |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When the environement variable "DB2_OPTSTATS_LOG" is set with a
path other than the default one, the command db2diag does not
find the logs.
ie. db2diag -fac OPTSTATS does not work when DB2_OPTSTATS_LOG
was set to a new directory.
For example:
- # db2set
DB2_OPTSTATS_LOG=ON,NUM=10,SIZE=2,NAME=db2optstats,DIR=/home/db2
dbm84/sqllib/db2dump/statslog
- stop/start db2 instance
- wait for the first logfile...
- # db2diag -fac OPTSTATS
db2diag: No messages found for facility "OPTSTATS". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users on DB2 v9.7 Fix Pack 3 and below *
****************************************************************
* PROBLEM DESCRIPTION: *
* When the environement variable "DB2_OPTSTATS_LOG" is set *
* with a *
* path other than the default one, the command db2diag does *
* not *
* find the logs. *
* *
* ie. db2diag -fac OPTSTATS does not work when *
* DB2_OPTSTATS_LOG *
* was set to a new directory. *
* *
* *
* *
* For example: *
* *
* *
* *
* - # db2set *
* *
* DB2_OPTSTATS_LOG=ON,NUM=10,SIZE=2,NAME=db2optstats,DIR=/home/d
* dbm84/sqllib/db2dump/statslog *
* *
* - stop/start db2 instance *
* *
* - wait for the first logfile... *
* *
* - # db2diag -fac OPTSTATS *
* *
* db2diag: No messages found for facility "OPTSTATS". *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.7 Fix Pack 4 *
**************************************************************** |
| Local Fix: |
If db2optstats log files are in
/home/db2dbm84/sqllib/db2dump/event path
db2optstats.0.log db2optstats.1.log db2optstats.2.log
Now, if you run "db2diag db2opt*" from this directory or
"db2diag /home/db2dbm84/sqllib/db2dump/event/db2opt*" from any
directory, you should be able to get from all the optstats log
files. |
| available fix packs: |
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 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem firest fixed in DB2 V9.7 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.09.2010
02.05.2011
02.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
