Transactions Cannot be Properly Flushed --STILL HERE (AREV Specific)
At 06 AUG 1998 05:04:03PM Diane Jackson wrote:
"LINK LIST IN THE TABLE !APPS*CMSNEW*18:21:27 07 JUL 95 IS BROKEN TRANSACTIONS CANNOT BE PROPERLY FLUSHED. TO CORRECT THIS PROBLEM, PLEASE REBUILD ALL THE I INDEXES IN THAT TABLE" is still the message i'm getting. Rebuilding the indexes is NOT working. This mess started with a lightning storm that knocked out the power in this area. Our remote office left their connection up overnight with Revelation open and that's when the fun began. I'm at my wits end, to say the least! Every time I stay late and rebuild, I come in the next morning and it starts all over again, and i get fatal errors, and GFEs. HELP!
At 06 AUG 1998 07:30PM Andrew P McAuley wrote:
Per my last response
When records are written to disk, transactions are created in the appropriate ! file. These transactions are numbered 0, 1, 2, 3 etc with each record pointing to the next one in the sequence. Occasionally this sequence will become corrupt. We have only seen this when there are more transactions being created than the indexer can deal with. The fix (to prevent) was to install a faster indexing machine or write a specialised indexing routine to ensure that transactions do not back up. The short term fix is to delete EVERY transaction in the ! file with a numeric key, then rebuild the indexes. Until the numeric rows have gone you will not be able to rebuild. Try :Select !MyFile With @Id between 0 and 999999 :Delete !MyFile then rebuild
amcauley@sprezzatura.com
World Leaders in all things RevSoft
At 06 AUG 1998 07:48PM K Gilfilen wrote:
Diane,
I tend to think Egbert was correct in his posting, that there is a network/hardware issue that was created in that lightning storm. Have you verified that these are fully functioning now? AREV depends more on hardware integrity than most systems, at least with regard to handling transmission fluctuations. Everything has to be just about perfect. If you can, run some network diagnostics and do a performance check on the PC to ensure all is correct.
good luck,
Kenny
At 07 AUG 1998 08:42PM Carl Jacobs wrote:
RE your GFE's AND LLE's - I recently upgraded to a windows NT (registered trademard of Microsoft Corporation) server. Every few hours I would experience a GFE or LLE indicating that the transactions cannot be properly flushed. We were also losing access to various "Drives" on the network.
We purchased the Revelation NT Service and our problems disappeared. After 4 months of Staying Late, Selecting and Deleterowing, VerifyingLH, and dumping and fixing GFE's, we are finally able to operate. And not only operate, but operate at a level of efficiency that has been unnatainable prior to purchasing the Revelation NT Service.
I am making NO RECCOMENDATONS nor am I offering advice. I am simply stating that we experienced nightmares involving data corruption. Now we sleep well.