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

ADMIN_MOVE_TABLE MIGHT FAIL WITH SQL2102N RC=22 WHEN USING COPY_USE_LOAD

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
ADMIN_MOVE_TABLE might fail if the following conditions are met: 
- the admin_move_table is run with option COPY_USE_LOAD 
- the table has LOB columns 
- the table is compressed 
- the length of data in the lob columns is bigger than the 
implicit inline length 
- MESSAGES ON SERVER clause gets used 
 
The admin_move_table will fail with the following error: 
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 
 
The following snippet will be shown in the load trace: 
SQL0445W  Value "xxxxxxxxxxxxxxxxxxxxxxx" 
has been truncated.  SQLSTATE=01004 
SQL3185W  The previous error occurred while processing data from 
row "109993" 
of the input file.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************
Local Fix:
Perform the table move without COPY_USE_LOAD option.
Solution
First fixed in Db2 10.5 Fix Pack 9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.02.2017
29.09.2017
29.09.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)