Corrupted Quickdex (AREV Specific)
At 12 MAY 2005 06:27:26PM Linda Mills wrote:
We are suddenly experiencing Quickdex corruption on many tables. If we do a SELECT or LIST on a table the following message appears:
Fatal Error -36 Reading Row
Sometimes it actually provides a record name, but it is not a valid row for that specific table.
We have removed and reset the Quickdex on the tables and everything appears to be working fine, but the next day when we check the Fatal Errors have reappeared.
The same tables have a Btree index as well. Anyone seen this before?
At 12 MAY 2005 09:02PM Mike Ruane wrote:
Linda-
What is the size of the %records% field in the file?
It's likely exceeding the 64K limit. Take off the quickdex and the problem will go away.
Mike
At 13 MAY 2005 12:49PM Linda Mills wrote:
There are several and most of them are small (i.e. 707 bytes, 820 bytes) with the largest at 32000 bytes.
We have used the quickdex on these tables for years and never experienced this problem. We need them in order to have the F2 popups show a sorted list.
At 14 MAY 2005 01:08AM Warren Auyong wrote:
Has anything changed on the network recently? Upgraded drives? Disc mirroring, transaction tracking, virus scanner, new routers, software upgrades etc.?
What network are you running on? Version of ARev and NT Service or NLM?
Have you checked the sizelock flags on the files in question? Use the DUMP command. If they are greater than 1 then use the minus key on keypad to lower it to zero.
At 15 MAY 2005 08:28PM dsig _at_ sigafoos.org wrote:
is this in Denver or on the ice? there were some changes (and back) on the ice .. yes? has it been happening since then?
dsig
At 16 MAY 2005 02:44PM Linda Mills wrote:
Warren,
We have narrowed down the start of the problem to about 2 months ago and there have not been any significant network changes. We are currently using Win2000 Service 1.5 and Network Performance Pack on a Windows2000 Server with the clients using Win XP.
I think we have found a work around that is a better solution. Under Popups "Explicit Popup Information" we have added "Select" statements to replace the sorting down by the Quickdexes. One table has grown to be almost too big for the Quickdex anyway.
One thing we did notice was that the one table without a Btree, but with a Quickdex was not having the corrupted Quickdex problem. It was all the other tables that had both a Btree and Quickdex exhibiting the problem with the corrupted Quickdexes.
Thanks for your help.