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

DB2DART ERROR - UNEXPECTED LOB INLINE LENGTH

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Any users that create a table like a view containing an      * 
* inline LOB or create a table from a select and append an     * 
* inline LOB to the definition                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See APAR description                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.7 Fixpack 6 or later            * 
****************************************************************
Local Fix:
alter the table column to the desired or default inline length: 
 
  alter table employee_excpt alter column excpt_msg set inline 
length <integer>
available fix packs:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem first fixed in Version 9.7 Fixpack 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84250 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2011
05.06.2012
05.06.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP6
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList