HELP! Slow/Locked on specific table (AREV Specific)
At 24 MAR 1998 08:38:40PM Wendy T. wrote:
We are running a Novell network, DOS based, and are using AREV 31. Two days ago, we started to experience delays/slowness in one of the tables on our database. It started out just being slow, ie. when you seleted that screen from the main menu that is associated with the table, it took 30 seconds or so for the screen to even come up. This got slower yesterday, and today we are at the point where it will come up only if you wait about a 1/2 hour. The other tables appear to be OK. Naturally, this is a problem because no one can get in and work, and this is our most used table. I was working on the phone with our local AREV guy who designed our database (he's most familiar with the earlier Revelations); we tried just pulling up a record from the command line (typed "edit (table name) (record number)" and it still did not want to pull it up. So it doesn't appear to be a problem with the screen start up or indexes. We also did a Verify on the table, and got the message: Group 0; Code 4; Initial setup fail
ed!! Table size 2048, framesize 1024, modulo 1; table size/framesi" , but not sure if that means anything. My AREV guy says that AREV stores data in something like "buckets", and you could have 10 buckets with 1,000 records in each, or 10,000 buckets with 1 record each, and something maybe messed up with the way it is putting it in "buckets" ("I'm not too high-tech, so this is how he has to explain it to me so I can understand - keep that in mind when you respond!)
Please help, we are all dead in the water!
At 25 MAR 1998 09:41AM Aaron Kaplan wrote:
Something happened to the alpha record in the header which told the file there were too many unused frames and it kept compressing.
What you'll need to do is create a temporary file and copy all the records into there. This could take some time, based on your message. When this is done, delete the original file and rename the temp to the original.
If you can't get to the original file any longer, restore the file from backup before doing the copy.
