DB2 - Problem description
Problem IC74111 | Status: Closed |
DB2DIAG UTILITY MAY RETURN INCORRECT RESULTS WITH SEARCHING FILTER APPLIED | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
db2diag utility may return incorrect results with filtering key in case database START or STOP messages are the last messages recorded in db2diag.log As example 1) db2diag -A 2) db2 activate db <dbname> 3) 2) db2 deactivate db <dbname> 4) db2diag -g 'msg:=ADM7513W' Result is a DB deactivation message that has nothing to do with the message type ADM7513W: ************************ 200000-00.00.00.000000 E25191A471 LEVEL: Event PID : 1 TID : 1 PROC : db2sysc 0 INSTANCE: XXXX NODE : 000 DB : XXXXXXXX APPHDL : 0-1 APPID: *LOCAL AUTHID : XXXXXXXXX EDUID : 1 EDUNAME: db2agent (idle) 0 FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::TermDbConnect, probe:20 00 STOP : DATABASE: Q11YD84D : DEACTIVATED: YES ************************ | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.7 Fixpak 6 * **************************************************************** | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 9.7 Fixpak 6 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.01.2011 13.11.2012 13.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |