Index repair tool (AREV Specific)
At 25 APR 2000 03:28:30PM Peter Dunlap wrote:
One of the BTREE indexed fields, of one of my indexed files is damaged (not broken, no GFEs). The indexed field is a single character code. When an index request is made for the character "R", all records that have an "R" in that field are returned, plus 402 records that have the letter "I"! As the field changes according to the processing status of the record, the number of records returned, varies. However the 402 errant records are always present. The file is very large (] 6 million records), consequently a field-index-rebuild takes about a day. I would like to avoid this. Are there any tools available that can repair this type of index damage?
At 25 APR 2000 05:11PM Warren wrote:
Nice thought but the btree record structure used in the !files is not well documented (at least for public consumption) and changes dynamically as the nodes change size. Any index repair tool would have to make as many or more disk reads and queries as the normal index rebuild and as such would probably take as long or longer than a normal index rebuild.
As such it probably isn't worth the development time to reverse engineer the !file record structure, node splitting behaviour and debugging time to make sure that the valid reconstructions are done properly when an index rebuild does the job reliably.
At 26 APR 2000 01:57PM Larry Wilson - TARDIS Systems, Inc. wrote:
If you're not using AREV 3.12, you need to upgrade to insure that the SELECT bug that exists in prior versions is not causing the problem.
Larry
tardis_systems@yahoo.com
At 26 APR 2000 04:38PM Peter Dunlap wrote:
AREV 3.12 is the version I am using, with NLM 1.5, Netware client 3.1.
At 26 APR 2000 08:48PM Warren wrote:
ARev 3.12 has pretty fast index rebuilds. To help speed things along:
a) make sure the temp sort files write to a local hard disk and not a network drive
b) run it on the fastest workstation with the fastest hard drive available.
c) run the rebuild at a time when there is little other network traffic.
At 26 APR 2000 08:52PM Warren wrote:
ARev 3.12 has pretty fast index rebuilds. To help speed things along:
a) make sure the temp sort files write to a local hard disk and not a network drive
b) run it on the fastest workstation with the fastest hard drive available.
c) run the rebuild at a time when there is little other network traffic.