APAR status
Closed as program error.
Error description
If you have a large table fragmented by expression with an index defined on the column used for fragmentation and you run a simple select using that column in the WHERE clause, the optimizer correctly applies the fragment elimination feature but it chooses an index-scan path, which is 3 times slower then a sequential scan.
Local fix
Use the optimizer directives to force the sequential scan.
Problem summary
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 11.70 * ****************************************************************
Problem conclusion
Problem Fixed In IBM Informix Server 11.70
Temporary fix
Comments
APAR Information
APAR number
IT04757
Reported component name
INFORMIX SERVER
Reported component ID
5725A3900
Reported release
B70
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-06
Closed date
2017-06-09
Last modified date
2017-06-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
INFORMIX SERVER
Fixed component ID
5725A3900
Applicable component levels
RA10 PSN
UP
RA10 PSY
UP
RB10 PSN
UP
RB10 PSY
UP
RB50 PSN
UP
RB50 PSY
UP
RB70 PSN
UP
RB70 PSY
UP
RC10 PSN
UP
RC10 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B70","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 June 2017