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

DATA PARTITION CANNOT BE DETACHED AFTER A NON-RECOVERABLE LOAD IS
PROCESSED BY ROLLFORWARD.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Data partition cannot be detached or a specific range of data 
cannot be accessed after a non-recoverable load processed by 
rollforward. 
 
Errors similar to the following may be seen: 
 
db2 "select * from tempt1" 
 
SQL1477N  For table "schemaname.TEMPT1" an object "5" in table 
space "2" cannot be accessed. SQLSTATE=55019 
 
db2 alter table table1 detach partition part1 into tempt1 
 
SQL0204N  "Schemaname.TEMPT1" is an undefined name. 
SQLSTATE=42704 DB21034E  The command was processed as an SQL 
statement because it was not a valid Command Line Processor 
command.  During SQL processing it returned: 
SQL0668N  Operation not allowed for reason code "3" on table 
"schemaname.TABLE1". SQLSTATE=57016
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of data partitioned tables.                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* After a roll forward of a non-recoverable load into a        * 
* partition, that partition is not accessible and cannot be    * 
* detached.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to latest fix pack.                                  * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Problem is first fixed in DB2 UDB Version 9.7 fix pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.06.2009
05.01.2010
05.01.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList