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

WHEN USING ADMIN_MOVE_TABLE WITH COPY_STATS OPTION ON SWAP PHASE, IT COULD
FAILS WITH SQL2102N, REASON CODE 28.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The prerequisite is to face this problem; 
 
1. The table being moved by ADMIN_MOVE_TABLE has double byte 
character data. 
2. A column value in the table being moved is > 33 bytes. 
3. ADMIN_MOVE_TABLE is run with COPY_STATS option(if it is run 
with manually, COPY_STATS is used on SWAP phase) 
 
SQL2102N 
 
The ADMIN_MOVE_TABLE procedure could not be completed because of 
an internal failure during the execution of the procedure. 
Reason code: reason-code. 
 
28 
 
    An error occurred while copying statistics from the source 
table to the target table.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using db2_v101                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v101fp4                                       * 
****************************************************************
Local Fix:
Use ADMIN_MOVE_TABLE without COPY_STATS option.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Upgrade to db2_v101fp4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.11.2013
17.08.2014
17.08.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList