Once upon a time, I repaired uniVerse files fairly often. I was taught by Mark Baldridge and later took a refresher course from Joel Yates.
Fixing the file at v9.4.n.n (pre fixtool days) will require manual file work at the OS level using filepeek. Since filepeek doesn't prompt for errors, writing the wrong data can destroy the file. Incidently, if everyone is off the system and there are no processes running against the INVOICE file, uvfixfile may very well work just fine. It fails if there is any activity against the file. In later releases, uvfixfile wouldn't even run if there was file activity, similar to RESIZE. As for you question about not losing data, sometimes you don't lose data if the link is from a duplicate 'forward link' to 2 different groups. Fixing the Blink error will allow the hashing algorhythm for the correct group to be seen. There is a very real chance that you will lose the one record where the Blink error is and possibly the records that come after the error in the affected group. If the corrupt file is a type 30 file (dynamic on UV), then the repair is more difficult, but still relatively easy for someone with experience. Karl Pearson On Fri, 2004-02-27 at 08:04, TELRIS MAN wrote: > Our system is running on UV 9.4.1.3B on SCO Unix 5.0.5. > > I have encoutered the following error message when I SELECT a file 'INVOICE' > File /disk3/MYDATA/INVOICE > Computed blink of 0x312e3134 does not match expected blink of 0x158800 > Detected within group starting address 0x27e1e00 ! > Internal data error. > > Anybody over there can tell me how can I fix the problem and save all data? > > Please describe details > > Thks > > TM -- Karl L. Pearson Director of IT, ATS Industrial Supply Direct: 801-978-4429 Toll-free: 888-972-3182 x29 Fax: 801-972-3888 http://www.atsindustrial.com [EMAIL PROTECTED] -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
