INDEXING ERROR (AREV Specific) [Revelation On-Line Wiki]

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 15 NOV 1999 11:10:45AM kau wrote:

AREV Specific

I have the following error message that flahses every so often:

"link list in the table "validate_file*BILLING*14:06:17 15 JAN 1996"
             transaction cannot be proberly flushed
                  To correct this problem,
Please rebuild all the indexes in the "VALIDATE_FILE*BILLING*14:06:11"

According to the knowledge base, index file should consist of

datafilename*account_name*volume, but it looks like the volume is replaced by the date and time. Is that something that I should take into consideration before reindexing? Thank you for your help.

At 15 NOV 1999 03:38PM Warren wrote:

This has been discussed numerous times. Perhaps RTI should create a FAQ.

There is a logical index record corruption in the indexing file. Basically an indexing node points to a non-existing node and the BTREE chain cannot be traced properly.

The easiest way to eliminate this problem is to:

1) Document the existing indexing settings on the file

2) Do a CLEARFILE !filename (this is recommened because sometimes you'll get the error message while removing the indexes)

3) Remove all the indexes from the file (confirm that the !filename has been deleted)

4) Add indexing back to the file using settings from (1)

Note: No other user should be in the system while the above is being done. Shut down any dedicated indexing stations also.

At 16 NOV 1999 07:24PM K Gilfilen wrote:

I might add, if I recall correctly, that the date/time are the default volume name, if you haven't specified one.

At 16 NOV 1999 10:56PM Victor Engel wrote:

Your problem could be a symptom of a more serious problem. You could have sessions that are not honoring record locks. This situation could be causing the problem you refer to, although you would likely also see GFEs if this were the case. Anyway, it couldn't hurt to perform a thorough record lock test on all your workstations. If you do any PCPERFORMs or SUSPEND …. then you should include these in your testing because they can clear locks on some platforms.

At 18 NOV 1999 03:28PM KAU wrote:

Thank you all for the info. I selected all records inte !file between 0 and 99999, deleted them and rebuilt the indexes. So far so good!

View this thread on the forum...