DB2 FOR LUW / DB2FORLUW / A10 - DB2

Regeneration of view updates the system catalog's. When this 
catalog update is replayed on standby replay only window should 
be enabled but it is not.  Due to this, applications trying to 
access the particular catalog table could see a corrupted LOB 
thus bringing down the standby database. A simple repro that 
could trigger this situation is 
 
create table t1 (c1 int) 
create view v1 as select * from t1 
drop table t1 
create table t1 (c1 int) 
select * from v1

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW HADR users with reads on standby enabled on standby  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Problem:                                                     * 
* ----------                                                   * 
* Regeneration of a view changes catalog tables and updates    * 
* LOB columns. This is a DDL operation but due to the way it   * 
* is designed it doesn't go through the normal DDL code path.  * 
* When a view is regenerated it's not enabling the Replay Only * 
* Window on Standby.                                           * 
*                                                              * 
* Impact:                                                      * 
* ---------                                                    * 
* When the log's records for the regen view stmt are being     * 
* replayed on standby, readers on standby will not be blocked. * 
* Applications trying to access the particular catalog table   * 
* could see a corrupted LOB thus bringing down the database.   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 fixpack 2.                              * 
****************************************************************

One can avoid the issue by manually terminating all applications 
on standby before a regen view is being replayed. No new 
applications should attempt to connect while the view 
regeneration log records are replayed on standby. 
In case, the database is brought down due to the mentioned 
issue, restart the standby database. There should be no impact 
to the database contents. It will come back normal.

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
 

The defect is fixed in DB2 v10.1 Fixpack 2

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

04.11.2012
18.12.2012
18.12.2012