DB2 FOR LUW / DB2FORLUW / A10 - DB2

There have been two ways found to cause this condition. 
 
1. When a view is created from a UNION ALL of tables, and then a 
table is created LIKE the view.  For example: 
 
create view V1 as select ... from T1 union all select ... from 
T2 
create table TAB1 like V1 
 
The view will have an inline length of 0 for its LOB columns, 
and the inline length is incorrectly inherited by the table TAB1 
that is created like the view. 
 
2. When a table is created as a select from another table and a 
LOB column is added as part of the new DDL.  For example: 
 
create table employee_excpt as ( select employee.*, current 
timestamp as excpt_ts, cast ('' as clob(32k)) as excpt_msg from 
employee ) with no data; 
 
The new table will have an incorrect inline length of 0 for its 
LOB column. 
 
When you run a db2dart on one of these table, you will see the 
following: 
 
Table inspection start: DB2INST1.EMPLOYEE_EXCPT 
 
         Data inspection phase start. Data obj: 4  In pool: 4 
         Error: Unexpected LOB inline length. 
         Data inspection phase end. 
 
         Error: Unexpected LOB inline length. 
         Error: Unexpected LOB inline length. 
         Error: Unexpected LOB inline length. 
         Error: Unexpected LOB inline length. 
         Error: The tablespace object-table and the data 
disagree on the existance of LOB data! 
         Warning: Table descriptor record indicates LOB exist: 0 
         Warning: DMS Object table indicates LOB exist:        1

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users running servers on DB2 Version 10.1 GA on          * 
* platforms Linux, Unix and Windows, and running a db2dart on  * 
* a specific table.                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 Version v10.1 Fix Pack 1.                      * 
****************************************************************

alter the table column to the desired or default inline length: 
 
  alter table employee_excpt alter column excpt_msg set inline 
length <integer>

DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
 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
 

This problem is first fixed in DB2 Version v10.1 Fix Pack 1.

keiner bekannt / siehe Local-Fix

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

13.06.2012
31.10.2012
31.10.2012