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

ADMIN_MOVE_TABLE FAILS WITH SQL0206N WHEN RANGE PARTITION KEY REFERS TO A
COLUMN NAME GREATER THAN 8 CHARACTERS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Using admin_move_table against a table with range partition 
defined. 
And the range partition key refer to a column name that's 
greater than 8 characters. 
 
 
e.g. Create table: 
 
CREATE TABLE DWH_H.FACT_AJUSTES_PRUEBA ( 
 KEY_CERO               SMALLINT , 
 KEY_UNO                SMALLINT , 
 KEY_UNOMENOS           SMALLINT , 
 KEY_MEDIOPAGO          SMALLINT , 
 CLAVEHORA              SMALLINT , 
 KEY_CHAR               CHARACTER , 
 FECHAGRABACION         DATE , 
 FECHA                  DATE , 
 CLAVEENTIDAD           SMALLINT , 
 KEY_MARCA              SMALLINT , 
 KEY_CLASE              SMALLINT , 
 CLAVEAFINIDAD          INTEGER , 
 CLAVEENCARGADO         BIGINT , 
 KEY_CUENTA             INTEGER , 
 KEY_TARJETA            INTEGER , 
 CLAVETIPOAJUSTE        SMALLINT , 
 MONTO                  INTEGER , 
 RECCOUNT               SMALLINT , 
 CLAVE1                 SMALLINT , 
 CLAVE2                 SMALLINT 
 ) 
 PARTITION BY RANGE (FECHAGRABACION) ( 
 PARTITION PT_MINIMO STARTING FROM (MINVALUE) 
ENDING AT ('2006-01-01-00.00.00') EXCLUSIVE , 
 PARTITION PT_200601 STARTING FROM ('2006-01-01-00.00.00') 
ENDING AT ('2006-02-01-00.00.00') EXCLUSIVE , 
 
.. 
 
Note: PARTITION BY RANGE (FECHAGRABACION) 
 
db2 "CALL 
SYSPROC.ADMIN_MOVE_TABLE('DWH_H','FACT_AJUSTES_PRUEBA','A4R#BTAB 
D', 'A4R#BTABD', ' 
A4R#BTABD', NULL, ' ',' ', NULL, ' ', 'MOVE')" 
 
SQL0206N  "FECHAGR" is not valid in the context where it is 
used. 
SQLSTATE=42703
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fix Pak 3                               * 
****************************************************************
Local Fix:
Move table manually by export/import.
available fix packs:
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
Problem first fixed in DB2 v10.1 Fix Pak 3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95305 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.03.2013
24.10.2013
24.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList