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

DATA ROW COMPRESSION SETTING DISABLED ON TARGET TABLE WHEN ADMIN_MOVE_TABLE
COPY_USE_LOAD FAILS WITH SQL3508

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When 
ADMIN_MOVE_TABLE('XXX','SOURCE','TARGET','COPY_USE_LOAD','MOVE') 
fails with: 
SQL3508N  Error in accessing a file or path of type "MSGFILE" 
during load or load query.  Reason code: "1". 
PATH:"xxx", the TARGET table will end up with data row 
COMPRESSION NO, regardless of the data row compression setting 
on the SOURCE table.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2.                      * 
****************************************************************
Local Fix:
* Drop TARGET table. 
* Alter table TRAGET and set COMPRESSION accordingly.
available fix packs:
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

Solution
First fixed in DB2 Version Fix Pack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.11.2012
11.04.2013
11.04.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList