Last night's error was on my A/P file, index.M, there's no consistency on which file or index it occurs on. There are no lookups being performed, it is a straight export ascii dump of the data, it is the exact same code in at least 35 of the files.<br>
<br>When I went into my A/P file this morning, index.M does not say it's an invalid index, and accessing the file via that index appears to be all in order.<br><br><br><br><div class="gmail_quote">On Tue, Mar 19, 2013 at 10:42 AM, Kenneth Brody <span dir="ltr"><<a href="mailto:kenbrody@spamcop.net" target="_blank">kenbrody@spamcop.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 3/19/2013 9:55 AM, Ian Wood wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
filepro 5.07.03.02<br>
Windows Server 2008<br>
<br>
We currently run an overnight process that exports data from about 50 files<br>
to feed another system. Periodically, we get an invalid index error on one<br>
of the files, not one in particular, just a random spot. I have the -ro<br>
flag set to run as read only.<br>
<br>
Is there a way to have rreport run on files and ignore automatic indexes?<br>
I'm not posting anything, just doing file dumps.<br>
</blockquote>
<br></div>
If you're running with "-ro", then the problem isn't when updating an index (which it won't do in read-only mode), but when reading an index. Assuming that the error doesn't occur on the temp index that *report built, then I can only assume that the error occurred on a lookup. (What index did the error occur on?) And the only index being accessed when executing the lookup it the index being used for that lookup, which you obviously can't avoid using.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't have enough time to do a dxmaint -ra -e on all files first as we<br>
run two shifts and the exports take approximately 5-6 hours to run.<br>
</blockquote>
<br></div>
If you are looking up to a file via a corrupted index, you may have no choice but to rebuild that index.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Kenneth Brody<br>
</font></span></blockquote></div><br>