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

ADMIN_MOVE_TABLE MAY RETURN SQL20242N IF DEEPCOMPRESSION_SAMPLE IS SET TO A
SMALL VALUE FOR A LARGE SOURCE TABLE.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
call 
admin_move_table_util('tabschema','tabname','UPSERT','DEEPCOMPRE 
SSION_SAMPLE','1') 
 
  Return Status = 0 
 
call 
admin_move_table('tabschema','tabname','table_space','table_spac 
e','','','','','FORCE,COPY_USE_LOAD,NON_CLUSTER,NO_STATS','COPY, 
TRACE') 
SQL20242N  The sample size specified in the TABLESAMPLE clause 
is not valid. 
SQLSTATE=2202H
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 Version 10.5 Fix Pack 4                        * 
****************************************************************
Local Fix:
Reset the DEEPCOMPRESSION_SAMPLE to a larger value (at least 
20MB) for optimal deep dictionary creation, or just remove the 
setting so that AMT will use default sample size for optimal 
dictionary creation.
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

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