|
Problem IC84530
|
Status: Closed |
DB2DIAG -E RETURNS INCORRECT DB2DIAG.LOG ENTRY |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The following command returns incorrect log entry:
$ db2diag -e DIA8309C
2011-05-30-15.29.20.856163+000 E178071A468 LEVEL: Event
PID : 1089590 TID : 19225 PROC : db2sysc 0
INSTANCE: xxxxxx NODE : 000 DB : xxxxxx
APPHDL : 0-44441 APPID:
10.215.247.174.40682.1105301529
AUTHID : xxxxxx
EDUID : 19225 EDUNAME: db2agent (idle) 0
FUNCTION: DB2 UDB, base sys utilities,
sqeLocalDatabase::TermDbConnect, probe:2000
STOP : DATABASE: xxxxxx : DEACTIVATED: NO
This entry does not match the error code DIA8309C. Moreover,
DIA8309C is not present in db2diag.log. Therefore, the above
command is not expected to return any output.
The problem occurs when the following is true:
- When it is the above probe
- When the above entry is the last log entry in db2diag.log file
Also, it does not matter what -e value is. For example,
db2diag -e SAMPLESTRING also returns the same entry. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v101fp1 *
**************************************************************** |
| Local Fix: |
n/a |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
db2_v101fp1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
11.02.2013
11.02.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
