DB2 - Problem description
Problem IC64501 | Status: Closed |
DB2DIAG UTILITY NOT RETURNING THE PROPER TIME RANGE ENTRIES WHEN THE -TIME OPTION IS SPECIFIED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
db2diag utility not returning the proper time range entries when the -time option is specified. It may also hang in some cases with the following callstack 0x000000000000e88c memset64_overlay() + 0x84 0x0000000100038a44 pdDiagGetNextLogRecord(??) + 0x884 0x000000010003807c pdDiagGetNextRecordFromBuffer(??) + 0x1dc 0x0000000100032854 pdDiagGetNextRecord(??) + 0x674 0x00000001000341b4 pdDiagProcessFile(??, ??, ??) + 0x554 0x0000000100033404 pdDiagToolEngine(??) + 0x404 0x0000000100062de8 main(??, ??) + 0xb68 0x0000000100000320 __start() + 0x98 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using the db2diag utility with the "-time" option. * **************************************************************** * PROBLEM DESCRIPTION: * * If this APAR is not applied, it is possible the * * db2diagutility to not return the proper time range entries * * when the-time option is pecified. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fixpack 2 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7, Fixpack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.11.2009 22.06.2010 03.01.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |