Lh_verify question (AREV Specific)
At 07 SEP 2001 01:12:54PM Todd Meuth wrote:
While attempting to run lh_verify on a few of our Arev 3.12 accounts, I receive the results "acct*revmedia Group 0 Code 5 Initial setup failed!! Overflow frame header type 64 is incorrect."
How do I go about fixing errors in the Revmedia file?
At 10 SEP 2001 10:12AM Frank Tomeo wrote:
Todd,
I have a client whose table size seems to always cause VERIFYLH to crash on me, so I wrote a routine that basically opens/reads every record and captures the groups that have GFE's as they come up.
However, in your case, since you have a Group 0 error in the Revmedia, you may have to approach it in a little different manner. Group 0 errors always seem to require a table rebuild in my past experiences. Since the Revmedia records are fairly small, it is easy to remake the bad records. I would go about your problem in the following way:
1) Go to SYSPROG and attach the Revmedia for one of your volume in question.
2) See if you can pinpoint the Revmedia records that are causing the problem by using a routine that will open/read each Revmedia entry.
3) Copy all the good Revmedia entries to a temp table.
4) See if you can find a good copy of Revmedia.lk and Revmedia.ov that you know has no problems with it. You can also just attach a new blank volume which will create an empty Revmedia.
5) Backup your bad Revmedia.
6) Use your clean Revmedia and overwrite the bad one. Attach (and clear if necessary) this Revmedia from SYSPROG.
7) Copy all your good Revmedia records from your temp table.
8) Re-create all the bad Revmedia records
9) Re-verify that your Revmedia records are good. If they are good, back them up, so you know you have a good copy if the error happens again.
Note… playing around with the Revmedia can be tricky. It is wise to probably backup up your system just in case (if that is possible). Minimally, make sure you back up your bad Revmedia.
Let me know if you need any help with this. I would be glad to walk you through the process.
At 12 SEP 2001 05:34PM Todd Meuth wrote:
Thank you for your quick reply Frank. I have not had the time to try this fix yet but will as soon as time will allow.