DB2 FOR LUW / DB2FORLUW / A10 - DB2

The APAR IC79996: Enhance the db2cat tool to identify table 
which may still be impacted by the consequences of the APARs 
IZ39997 & IZ40001 
 
Does not detect the situation when we have a regular view of the 
same 
name as the orphaned MST. 
 
Example: 
 
          Dependent MST DESCRIPTION 
          ------------------------- 
 
 
 Schema of the dependent Table     : MARIAJ 
 Table name of the dependent Table : V_TEST 
 Refresh Option                : 
 MST type                      : Sts View 
 Isolation Level             : 1 
 Arithmetic Warning Level    : 78 
 
$ db2 drop table test 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
SQL0901N  The SQL statement failed because of a non-severe 
system error. Subsequent SQL statements can be processed. 
(Reason "Dependent MST's packed Descriptor not found".) 
SQLSTATE=58004 
 
1. If there are no views defined with the same name as the 
orphaned statsview , db2cat with APAR IC79996 will report the 
corruption: 
 
db2cat -d test_db -s mariaj -n test -v 
 
**************************************************************** 
Validating Packed Descriptor: MARIAJ  .TEST 
 
Orphan dependent MST (count = 0) found in packed descriptor: 
MARIAJ  .V_TEST 
 
 
2. 
If we have a view with the same name (it does not need to have 
the same columns) as the Orphan dependent MST, the db2cat 
enhanced with APAR IC79996 will not detect this corruption. 
 
 
db2 create view v_test as select c1,c3 from test 
**************************************************************** 
Validating Packed Descriptor: MARIAJ  .TEST 
 
No Corruption Detected. 
 
---------------------------------------------------------------- 
 
 
This APAR will make additional improvements to db2cat so the 
corruption is detected in both cases.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 and Fix Pack 2                   * 
****************************************************************

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
 

Problem was first fixed in DB2 Version 10.1 and Fix Pack 2

keiner bekannt / siehe Local-Fix

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

04.11.2012
31.05.2013
31.05.2013