I have a client running AREV 3.12 on a Novell 3.x network who reported

an error while the system was indexing. I do not have the exact verbage of the error but indicated that;

The index for file XXX can not be properly flushed. To correct this

problem you need to rebuild the indexes for this file.

Ok, I rebuilt the index last week. The system ran fine for a few days, and now the same error has occourde again on the same file.

Can you tell me waht I should look for to permanently fix this problem?

Thanks as always,

Gary M. Breeding

Hi Gary-

This problem might occur due to the following:

-a DUMP/FIX was done on the table and a record was deleted (due to corruption) that still needed to be flushed from the transaction buffer

-transactions needed to be flushed on an index that doesn't exist anymore (it doesn't sound like this is your problem)

-the linked list holding the transactions has a bad pointer (this results in the broked linked list error message that goes along with the error about being unable to flush the index)

When you rebuilt the indexes, did you remove them and rebuild them? If not, try that.

Tracy

Some things to look for:

* Are all users using the same language set? Different language sets can have different sort orders, so an index created in one language set cannot be updated using a workstation set up in another language set.

* Are normal indexing processes being interrupted? Ask users if their workstations are locking up. Ask them if they get messages indicating waits for indexes, etc.

* Do you have a dedicated indexer?

* Are there batch processes that update large quantities of indexes, creating a backlog?

* Attempting to delete records that don't exist can create index transactions that are not flushed by the background indexer. This causes the indexer to thrash, looking for a "good" index to update. INDEX.FLUSH will take care of this problem.

That's about all I can suggest without an exact message.

Victor

Thanks to Victor and Tracy,

I did not remove indexes, just selected the system menu option to rebuild then for that table. If I see the same message again, I'll make a note as to the exact verbage, and get back to you.

Thanks again,

Gary

Hi again,

I just got the same error again, but on a different table. This time the error message has been copied 

verbatim as follows in a black message box:

B323——-…

Link list in the table OP_SHIPMENTS*GPDP*13:13:32 07 OCT 1992 is broken.

Transactions cannot be properly flushed.

To correct this problem

please rebuild all the indexes in the table "OP_SHIPMENTS*GPDP*13:13:32 07 OCT 1992".

—–…

Since this same error message has occurred on a 'different' file this time, I'm quite concerned that the

problem is more global in nature.

I intend to take the stated advice to completely remove all indexes from this table and then recreate them,

but I still would like to know exactly what the problem is.

Please let me know what you think.

Thanks again,

Gary M. Breeding

View this thread on the forum...