APAR status
Closed as documentation error.
Error description
IFX_ROW_ID feature is undocumented but the equivalent "with rowid" is said deprecated in the documentation: Using the WITH ROWIDS Option Nonfragmented tables contain a hidden column called rowid, but by default, fragmented tables have no rowid column. You can use the WITH ROWIDS keywords to add the rowid column to a fragmented table. Each row is automatically assigned a unique rowid value that remains stable for the life of the row and that the database server can use to find the physical location of the row. Each row requires an additional four bytes to store the rowid. Important: This is a deprecated feature. Use primary keys as an access method rather than the rowid column. IFX_ROW_ID can be used to address the need of rowids for fragmented tables. When used to search for a particular row like in: SELECT col FROM tab WHERE ifx_row_id like 'val%' the engine is reading through all rows of the table and does not read only in the page where the given row can be found.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Informix 11.70, 12.10 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * See problem conclusion. * ****************************************************************
Problem conclusion
The database server might not use an index scan if ROWID shadow columns are defined on fragmented tables. If you want the query optimizer to use an index scan on fragmented tables, you should define a primary-key on the table, rather than precede the FRAGMENT BY clause with the WITH ROWIDS keywords in ALTER TABLE, ALTER FRAGMENT, or CREATE TABLE statements of SQL.
Temporary fix
Comments
APAR Information
APAR number
IC94738
Reported component name
INFORMIX SERVER
Reported component ID
5725A3900
Reported release
B70
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-08-08
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
Applicable component levels
[{"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