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

SET INTEGRITY IMMEDIATE UNCHECKED FAILED WITH SQL20209N IF THE PARTITIONING
KEY CONTAINS GENERATED COLUMN

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
create table t1 (i1 int not null, i2 int, i3 int, i4 int 
generated always as (i2+i3)) partition by range (i4) (starting 1 
ending 100 ) 
DB20000I  The SQL command completed successfully. 
 
set integrity for t1 off 
DB20000I  The SQL command completed successfully. 
 
set integrity for t1 all immediate unchecked 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL20209N  The "GENERATED COLUMN" option is not valid for table 
"TANJINXU.T1" 
with reason code "8".  SQLSTATE=428FH
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who issue SET INTEGRITY command or use                 * 
* ADMIN_MOVE_TABLE against range partitioning table with       * 
* generated columns                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fix Pack 4 or higher                    * 
****************************************************************
Local Fix:
N/A
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
First fixed in DB2 V10.1 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.10.2013
02.06.2014
02.06.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