home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 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

DB2 - Problem description

Problem IC99286 Status: Closed

STANDBY_SPOOL_PERCENT MAY SHOW AN INCORRECT VALUE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
If the Primary Log File Position and the Standby Log File 
Position values are the same then the STANDBY_SPOOL_PERCENT 
should show as zero. 
In some situations the Primary Log File Position and the Standby 
Log File Position values may be the same but the 
STANDBY_SPOOL_PERCENT can be a non-zero value. 
Calculating the difference between the Primary Log File Position 
and the Standby Log File Position values will produce the 
correct replay gap.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW 10.5 FixPack 4                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Fixed in DB2 LUW 10.5 FixPack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.02.2014
08.09.2014
08.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList