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 IC98257 Status: Closed

AFTER PERFORMING AN OFFLINE REORG IN HADR ENVIRONMENT, INDEX SMS
TABLESPACES HAVE DIFFERENT SIZES ON PRIMARY COMPARED TO STANDBY

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
After performing an offline reorg in HADR environment, index SMS 
tablespaces have different sizes on Primary compared to Standby. 
The reason being is that the index manager does not write its 
own log record to trigger the truncate on redo. As a result, 
when the logs are replayed on the Standby this doesn't take 
effect. This causes a difference in the size of index SMS 
tablespaces. 
 
The index manager should write it's own log record to trigger 
the truncate on redo.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR Systems                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5.0.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
The problem is first fixed in DB2 version 10.5.0.4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.12.2013
22.09.2014
22.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