> I have not seen a problem since about UV9.6. 4 corrections to my own claim.
There are 3 common sources of index corruption, all user-related: 1. Indexing a computed value, whose calculation does not depend ENTIRELY on the record being written. E.g.: - trans(), xlate(), T-correlatives - date(), time() - @variables such as @logname, @date, @who - SUBR(), where the subroutine READs anything. 2. Copying the primary data file using OS-level or Non-UV-aware utilities, but not correcting the file header's pointer to production index files. Updates to the copy will be indexed on the primary! Use SET.INDEX INFORM & SET.INDEX TO NULL on the _copy_ of the data file. 3. Updating the index files explicitly. Usually happens when there is a voc pointer to the .../I_fname/INDEXnnn type-25 file. There is a 4th that I consider it a long-standing bug. It is known to IBM. And to Informix, Ardent, & Vmark before them. 4. CNAME will not update any index on part of an id, e.g., FIELD( @ID, '*', 1 ). I was told CNAME uses an i/o mechanism different from every other update. cds ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
