Indexing Problem (AREV Specific)
At 06 MAR 1998 02:46:16AM Jim Dierking wrote:
We have a dedicated indexing station. The other workstations
do not index. We have had this configuration for several
years and it has worked fine. Occasionally we will get
a corrupted index and arev at the indexor workstation will got
to the debugger. We then usually have a message that tells
us in which file the problem exits and we rebuild it. However,
this time the indexing workstation is just hanging. The
workstation menu bar shows indexing but when a keystroke it
made it there is no response. We checked out our cabling and
used different workstations and had the same result.
We also checked several of the indexed files by running
Rlist reports using the indexes and it seems to work fine.
I am assuming there is a bad index somewhere. Any suggestions
on some code to find it? Also, I am curious on how AREV
gives priority to which indexes are updated when it updates?
TIA, Jim
At 06 MAR 1998 04:33AM Andrew P McAuley wrote:
A possibility is that one of your indexing files has a sizelock ] 2 and the OV file has gotten very big but is empty. The indexing process will then be scanning until it finds a record. It will not look for a keypress until it finds a row so will not respond.
The indexing system picks files to work on randomly from the list of files in memory.
At 06 MAR 1998 10:22AM ed mantz wrote:
We had the same problem - twice!
1. I checked the file server and the indexing machine was missing from thte list of logged in connections. Somehow the indexing machine connectio was being dropped. We checked all of the cabling and found a very intermitant "t" connector.
2. The next time is appeared that the 486 indexing machine was just shutting down. But it was not regular - runn for weeks and then wham - reboot - OK for a day; reboot OK for a week, etc. SUspect the processing was at fault, but I ran test continually for a week - not a hiccup. Finally decided it was the processor overheating because of the location of the machine. Put a fan inside the case to stir up the air a bit and it has been running for 6 months continually with no problems!
ed
At 06 MAR 1998 04:48PM Jim Dierking wrote:
Andrew can you give me an idea how to approach this. Is there
a way to create a report list indicating the sizelocks for
the indexing files? Should I simply rebuild all the index
files one at a time. I went to explorer and sorted the rev
files by size and found around 50 or so .ov files that showed
"0" file size. TIA for your help!
At 06 MAR 1998 04:54PM Jim Dierking wrote:
Andrew,
I forgot to mention that our customer and invoices indexing
files are around 10mb in size, but I could locate them
in the "0" size files. Do you recommend we delete records
to keep the index files smaller or is there another way to
avoid the problem you described?
At 12 MAR 1998 10:31AM Aaron Kaplan wrote:
0 byte OV files are fine. Truth be told, 0 byte OV files are what you want to achieve. A 0 byte LK file is serious trouble though.
Best way to get sizelocking info on a file is to use a program/function that determines sizelocks and place it in DICT.FILES/DICT.SYSTABLES and just do a listing on it.
