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

SYSPROC.ADMIN_MOVE_TABLE MAY RETURN SQL0104N IF TARGET TABLE HAS A
DIFFERENT PCTFREE SETTING

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
SYSPROC.ADMIN_MOVE_TABLE() may return in error when PCTFREE is 
different between source and target tables and source table has 
the default PCTFREE value which is stored as "-1" in 
syscat.tables.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Using SYSPROC.ADMIN_MOVE_TABLE with different PCTFREE        * 
* between source and target tables                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The issue occurs when the source table of the                * 
* SYSPROC.ADMIN_MOVE_TABLE procedure has been defined with the * 
* default value for PCTFREE and the target has a different     * 
* PCTFREE value. Following is an example on how this issue     * 
* could occur:                                                 * 
*                                                              * 
* db2 create database test_1                                   * 
* db2 connect to test_1                                        * 
* db2 create tablespace systoolspace                           * 
*                                                              * 
* # 1. Create a table T1 with default PCTFREE                  * 
* db2 "CREATE TABLE S.T1 (I INT NOT NULL, C CHAR(1))"          * 
*                                                              * 
* # 2. Create a table T2 with the same definition as table T1  * 
* except for the PCTFREE setting                               * 
* db2 "CREATE TABLE S.T2 (I INT NOT NULL, C CHAR(1))"          * 
* db2 "ALTER TABLE S.T2 PCTFREE 10"                            * 
*                                                              * 
* # 3. Call ADMIN_MOVE_TABLES as follows:                      * 
* db2 "CALL SYSPROC.ADMIN_MOVE_TABLE('S','T1','T2','','INIT')" * 
* SQL0104N  An unexpected token "-" was found following "R     * 
* TABLE S.T2 PCTFREE".                                         * 
* Expected tokens may include:  "<space>".  SQLSTATE=42601     * 
*                                                              * 
* With the example above both source table T1 and T2 have a    * 
* different PCTFREE setting and source table T1 has the        * 
* default PCTFREE setting since it was not specified at table  * 
* creation. This can further be confirmed by looking at        * 
* PCTFREE value for source table T1 which is stored as "-1" in * 
* SYSCAT.TABLES. For the example above, this would be as       * 
* follows.                                                     * 
*                                                              * 
* $ db2 "select tabname, pctfree from syscat.tables where      * 
* tabname in ('T1','T2') and tabschema = 'S'"                  * 
*                                                              * 
* TABNAME                     PCTFREE                          * 
* ----------------------- ---------                            * 
* T1                                       -1                  * 
* T2                                       10                  * 
*                                                              * 
* 2 record(s) selected.                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 9.7 Fixpack 5                             * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in version 9.7 Fixpack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.02.2011
13.12.2011
13.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList