This is the command line<br><br>\fp\dreport gr_ap -fp file_dump -u -a -v file_dump_s -y none -ro -r "3CON" -h "gr_ap"<br><br>No index is specified, and I can assure you that there are no lookups at all in either the selection process (which does contain a call, but that's only to set a date, again no lookup) nor the output process.<br>
<br>I guess I was just looking for a PFNOINDEX=ON or something of that ilk so as not to even try to read any indexes.<br><br><div class="gmail_quote">On Tue, Mar 19, 2013 at 12:57 PM, 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 10:50 AM, Ian Wood wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Last night's error was on my A/P file, index.M, there's no consistency on<br>
which file or index it occurs on. There are no lookups being performed, it<br>
is a straight export ascii dump of the data, it is the exact same code in<br>
at least 35 of the files.<br>
</blockquote>
<br></div>
Because you are running with "-ro" and not modifying anything, unless you are running the report off of index M, I can think of no reason why filePro would be accessing that index, aside from a lookup.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
When I went into my A/P file this morning, index.M does not say it's an<br>
invalid index, and accessing the file via that index appears to be all in<br>
order.<br>
</blockquote>
<br></div>
You may not have accessed the corrupted part of the index.<div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tue, Mar 19, 2013 at 10:42 AM, Kenneth Brody <<a href="mailto:kenbrody@spamcop.net" target="_blank">kenbrody@spamcop.net</a>>wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 3/19/2013 9:55 AM, Ian Wood wrote:<br>
<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<br>
files<br>
to feed another system. Periodically, we get an invalid index error on<br>
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>
<br>
</blockquote>
<br>
If you're running with "-ro", then the problem isn't when updating an<br>
index (which it won't do in read-only mode), but when reading an index.<br>
Assuming that the error doesn't occur on the temp index that *report<br>
built, then I can only assume that the error occurred on a lookup. (What<br>
index did the error occur on?) And the only index being accessed when<br>
executing the lookup it the index being used for that lookup, which you<br>
obviously can't avoid using.<br>
<br>
<br>
I don't have enough time to do a dxmaint -ra -e on all files first as we<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
run two shifts and the exports take approximately 5-6 hours to run.<br>
<br>
</blockquote>
<br>
If you are looking up to a file via a corrupted index, you may have no<br>
choice but to rebuild that index.<br>
</blockquote></blockquote>
<br>
-- <br>
Kenneth Brody<br>
</div></div></blockquote></div><br>