SI.MFS (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 23 DEC 1999 09:33:00PM Roger Steffen wrote:

AREV Specific

We are running AREV 1.16 and we believe our indexing file has been corrupted. We get two error messages: "Cannot Open Indexing Transaction File" and then "Unable to install SI.MFS filling system". Can anyone tell us how what is going on and how to fix this?

Thank you very much.

At 23 DEC 1999 10:58PM Steve Smith wrote:

AREV 1.16 uses the !INDEXING file in the INDEXING volume as a temporary repository for unresolved indexing transactions. SI.MFS is responsible for BTree indexing (as an indexed file is updated, the SI.MFS handles any index changes required). LISTINDEX is the TCL command to reveal indexes. RUNMENU INDEXING should give you some options.

Try, at TCL

ATTACH INDEXING

then

LIST !INDEXING

and see if the file is present.

Steve

At 26 DEC 1999 11:05AM Warren wrote:

There are several possibilities:

1) The !INDEXING file is corrupt, missing or not being attached (or unattached by some process). From TCL do a:

DUMP !INDEXING

This will tell you quickly if the file is there or not. If not there, do a LISTMEDIA INDEXING. If it is there try attaching INDEXING. Repeat the DUMP. If this is okay then you have to determine why the file is not be attached or is being detached. If the file is corrupt either restore it from backup or clear it or delete and recreate. Be sure that !INDEXING is bound to the account GLOBAL and a DICT portion is not needed for this file.

2) The DICT of the data file may be corrupt or the indexing information is damaged. When this happens the associated !file will not attach. Do a:

COUNT DICT filename

This usually reveals any GFE's in the file. If any, repair using DUMP.

3) The associated !file (e.g. DATAFILE=AR, !file=!AR) for the data file is missing or corrupt. Try the DUMP command on this file. Again, if the file does not seem to exist in DUMP it could be because of a corrupt DICT. A LISTMEDIA on the appropriate VOLUME will decide this. If it exists and not attached most likely you have a corrupt DICT file. If it does not exist, then remove indexing from the file and add it back on. If the !file should be corrupt (try a count !file), just do a CLEARFILE on !file name, remove all indexes from the file and add them back on.

4) You have duplicate dictionaries in different VOLUMES and an ATTACH statement attaches the incorrect version.

View this thread on the forum...