DB2 - Problem description
Problem IT04365 | Status: Closed |
DB2 MIGHT NOT CREATE IMPLIED PREDICATES ON GENERATED COLUMNS IN ORA COMPATIBILITY MODE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Description: Under rare scenarios DB2 might not create implied predicates on generated columns leading to unoptimized access plans if the following conditions are true: 1. The DB is created with DB2_COMPATIBILITY_VECTOR=ORA 2. The query contains one or more partitioned tables 3. The partitioned table is partitioned on one or more generated columns 4. The generated expression contains mathematical operations such as DIV, MULT 5. The columns referenced in the generated expression are used in a local predicate example: create table test_sales (a int, b int generated always as (a / 5)) partition by range(b) (starting from (0) ending at (1000) every (50)); select * from test_sales where a > 500; An implied predicate: b> 100 can be generated for this scenario | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * First fixed in DB2 Version 10.1 Fix Pack 5 Recommendation: * * Upgrade to DB2 Version 10.1 Fix Pack 5 * **************************************************************** | |
Local Fix: | |
Solution | |
See Problem Description above | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.09.2014 13.07.2015 13.07.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.5 |