|
Problem IT42034
|
Status: Closed |
UPDATE STATISTICS ON RANGE FRAGMENT TABLE IS NOT PICKING THE INDEX
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
When we run the Update statistics on a table, if we have index
defined on that column Update statistics
command uses that index and avoid doing sorting of rows. Where
as Update statistics on a table with range fragmentation
is not considering the index, instead choosing to do sort of
rows thus consuming more memory for sorting. If DBSPACETEMP
parameter is configured update statistics will create serveral
partitions in those temp dbspaces.
create table tab1 (
map_id serial not null, townid integer default null,
townname varchar(255))
fragment by range(map_id) interval(500000000)
partition part0 VALUES < 500000000 in dbspace1;
create index idx1tab1 on tab1 (townname ) using btree ;
update statistics high for table tab1 ( townname ) distributions
only; |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.FC10. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.FC10. *
**************************************************************** |
| Local Fix: |
NA |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.FC10. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.FC10. *
**************************************************************** |
| Comment |
Fixed in Informix Server 14.10.FC10. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.09.2022
23.02.2023
23.02.2023 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
