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

ADMIN_MOVE_TABLE FAILS WITH SQL1191N IF TABLE CONTAINS A LOB COLUMN AND
COMPRESSION IS TURNED ON

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
ADMIN_MOVE_TABLE fails with SQL1191N if table to be moved 
contains a LOB column and compression is turned on. 
 
The error message the client receives is: 
 
SQL2102N  The ADMIN_MOVE_TABLE procedure could not be completed 
because of an internal failure during the execution of the 
procedure. 
Reason code: "22". SQLSTATE=5UA0M 
 
And the message file contains: 
 
SQL1191N  Column "<LOB columname>" specified in the METHOD 
parameter does not exist. 
 
This is similiar problem than reported in APAR IT02861 which is 
specific for XML columns.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7.                      * 
****************************************************************
Local Fix:
don't specify COPY_USE_LOAD if possible
Solution
First fixed in DB2 Version 10.5 Fix Pack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.10.2014
20.01.2016
20.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList