RE: Informix 7.21.UC1 spontaneously corrupted indexes

Two issues: (1) Version numbers: 7.20.UC1 has been released, and there is work in hand on to produce 7.21.UC1, though as far as I am aware, it is not available for purchase or upgrade. There is a 7.20.UC2 release on Solaris, so you may have to get some version other than UC1 for whatever platform you use. (2) In old products, there was a limit of 65535 repetitions of a key in a non-unique index. This restriction was removed a long time ago -- I believe in 5.00 but quite possibly in an earlier or later version. It should not be an issue with 7.x versions of the software. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> }From: jvemo@cyberspace.com (Jon C Vemo) }Date: Mon, 24 Jun 1996 09:29:29 -0700 }X-Informix-List-Id: <list.10462> } }What's all this about 7.21....I thought 7.2 hadn't even been released yet. } }I presume you are talking about 7.12?? This release did have some problems..... } }From: Tom Downs[SMTP:down0041@maroon.tc.umn.edu] }Sent: Saturday, June 22, 1996 11:18 AM } }I don't claim to be an expert on 7.21. However, I have seen several }times when an index has spontaneously gone bad (v4.1). In these cases }it was due to an index on a field that had 64,000 or more of the same }values. For example, in a customer table with 300,000 rows. If there }is an index on a field "middle initial", the index will likely go bad if }any one letter appears more than 64,000 times. The solution in this }case is to make a composite index of "middle initial" and another field. }preferably an integer such as customer number. } }create index i_midinit on customers (midinit,custnum) } }Hope this is of some use...