Latest versionsfixlist
11.1.0.6 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC65752 Status: Closed

INTERACTIVE DB2TOP HADR SCREEN DOES NOT DISPLAY MILLISECONDS (MS) AFTER
THE VALUE FOR LOG WTIME

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Measure of unit (milliseconds) is not displayed for Log wtime in 
the interactive db2top HADR screen: 
 
[\]11:11:41,refresh=2secs(0.062)      HADR 
Sun,part=[1/1],DB2HADR:SAMPLE 
[d=Y,a=N,e=N,p=ALL] 
[qp=off] 
 
 
    Role......:             Standby    Status....: Connected 
    Time......: 2009/10/09 13:46:25    State.....:      Peer 
    Mode......:    Near synchronous    Log gap...:         0 
    Heartbeat.:                   0    Timeout...:        30 
    Log Writes:               38531    Log IOs...:     38531 
    Log Buff..:                   0    Log wtime.:      4.93 
    Rf type...:            Database    Rf status.:      Redo 
    Rf tms....:  2009/11/13 05:08:43
Problem Summary:
USERS AFFETCED: 
All 
 
PROBLEM DESCRIPTION: 
See ERROR DESCRIPTION 
 
PROBLEM SUMMARY: 
See ERROR DESCRIPTION
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.5 Fix Pack 6.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67787 IC67788 IC68798 IC68845 IC68868 IC68903 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.01.2010
10.09.2010
10.09.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.