One of our clients is receiving Fatal Errors in a very large much used file. Attempts to verify this file have for some time been unsuccessful whether they do on the main application or a regularly refreshed local copy.
Therefore, its impossible identify any GFE's which are undoubtedly lurking in the file. The problem has become worse and is preventing specific calculation activities. One of the things they have reported is that the OV files for the relevant table is :-
REV64392.OV- by the way, this file is now 2,201,340KB hug
I am currently checking on the size of the corresponding LK file. CAn the OV fle be resized and if so how do I do that?
Also, is there any other option for fixing the table when it cant be verified?
Further to my post the LK file is only 160,214 KB
Ouch - sounds like your sizelock might be non zero UNLESS your average row size is in the order of 14K.
If the row size is a lot smaller than 14K and the system can be taken out of commission for say a weekend it might be an idea to recreate the file, presizing to be say twice the size of the number of records x average size.
Given that this has the potential for data loss it'd be a very good idea to have a recent backup to hand.
If the row size is around 14K you will either have to archive off some records or implement an MFS to physically split the logical file over several physical files. This isn't a trivial project.
World leaders in all things RevSoft
Thanks for that - I will check the sizelock. I'm not sure how to check the row size?
Try LIST FILENAME SIZE
and just get a "visual average" by looking at a few pages of row sizes.
World leaders in all things RevSoft