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

OPTIMIZER NOT WORKING CORRECTLY WHEN ONLY PART OF THE PARTITIONS HAVE DATA
IN PARTITIONED TABLE.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Optimizer not working correctly when only part of the partitions 
have data in partitioned table. 
 
[ENV]: 
Operating system and level 
Operating system is: AIX 64BIT 6.1.0.0 
 
Server is running MPP/EEE (single node). 
DB21085I  This instance or install (instance name, where 
applicable: "db2srmp") 
uses "64" bits and DB2 code release "SQL09078" with level 
identifier 
"08090107". 
Informational tokens are "DB2 v9.7.0.8", "s130316", "IP23426", 
and Fix Pack 
"8". 
 
 
Optimizer not working correctly (Using TBSCAN not IXSCAN) when 
only parts of the partitions have data in a partitioned table.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 fp11 or later.                               * 
****************************************************************
Local Fix:
As a work-around, customer can try removing the empty 
partitions.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.05.2015
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList