|
Problem IT40864
|
Status: Closed |
ERROR -768 ON TABLE WITH COUNT OF ROWS > MAXINT
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
create table mbi_varia
(
var_id integer,
var_art_nr integer,
var_nr integer
);
create unique index tab1_ix1 on tab1 (var_id, var_art_nr) using
btree ;
create index tab1_ix2 on tab1 (var_art_nr,var_nr) using btree ;
The table has almost 2185682396 Rows.
When this query ran against the table:
SELECT var_id FROM tab1 WHERE var_id = 4711 ORDER BY
var_art_nr;
it returns this error:
768: Internal error in routine sqoptim: no valid query plan
generated
The problem stems from overflow in the sysindices.clust column
for the index, most commonly seen as a negative number. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC16 and 14.10.xC9. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC16 (if available) or *
* 14.10.xC9. *
**************************************************************** |
| Local Fix: |
After applying a version with the fix, the index(icies) with
the negative clust number(s) must be rebuilt. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC16 and 14.10.xC9. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC16 (if available) or *
* 14.10.xC9. *
**************************************************************** |
| Comment |
Fixed in Informix Server 12.10.xC16 and 14.10.xC9. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.05.2022
04.10.2022
04.10.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
