Charles,
Thanks for your input, let me answer your questions. What is strange about this corruption is that we use AK extensively and this is the only index we have had problems with. Regards, Tim, Six & a half thoughts: 1. You say 1:1 correspondence for ID:PHYS.PALLET.ID, meaning no multivalues, right? YES I ask about multivalues because if there are repeated identical mv entries in a record, SELECTINDEX performs differently in PI vs PICK flavours. See $OPTIONS PIOPEN.SELIDX. We are using PIOPEN flavour 2. And no null PHYS.PALLET.IDs, right? CORRECT 3. It is possible to corrupt an index if the primary data file were copied using an OS-level utility so that the header in the copy still contains pointers to the index. for example you CTRL+[mouse right click] and drag a copy to your sandbox to test with. To search for all indexes, in each VOC do: SELECTF SETINDEX INFORM Records only written using Basic. 4. Corruption can occur if there is a VOC pointer to the path of the type-25 index file itself. (i.e.,, VOC <2> will look something like ...\I_[datafilename]\INDEX.004). That allows you to edit or otherwise manipulate the index valued directly. For that matter basic's OPENPATH could do the same w/o a VOC reference. We use Q pointers to the account were the file actually resides. 4a. You might want to ~temporarily~ create such a VOC item so you can examine the contents of the index just for troubleshooting. Will try this after the next corruption. Thanks for the idea. 5. If you rebuild the index does it work right at first, then somehow get corrupted? Or is it always wrong? It works fine after a rebuild then we get corruptions hours, days, weeks later it is totally random. 6. TCL SELECT works correctly? only Basic's SELECTINDEX fails? How about BSCAN? After a corruption SELECT and SEELCTINDEX fails. Using NO.INDEX will find the records. Beyond that, maybe you could post an example of where it fails? (w/o =0D=OA's?) Not sure what example I can provide. cds Legal Disclaimer: The information contained in this message may be privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
