Thanks for the help all.  I ended up just restoring the file from last night, 
they weren't interested in waiting anymore.

-----Original Message-----
[] On Behalf Of Wjhonson
Sent: Thursday, April 18, 2013 1:05 PM
Subject: Re: [U2] blink error?

Where is this whitepaper at natively?




-----Original Message-----
From: andy baum <>
To: U2 Users List <>
Sent: Thu, Apr 18, 2013 10:56 am
Subject: Re: [U2] blink error?


You do not say what release of UV you are running but as of 9.5.1C you really 
should be using fixtool. See extracts from whitepaper below

1) Description
fixtool is the replacement for UVFIXFILE (uvfixfile from the OS shell) and was 
introduced at 9.5.1C to support
both 32-bit and 64-bit files. Initially it had a limited command line interface 
as it was intended to be used from
the UVAdmin GUI client. When 9.6 was introduced, fixtool was enhanced with a 
command line arguments
to provide logging of the groups it traced, but could not be limited to a 
certain number of groups. By 9.6.2.x, it
was further enhanced to permit group range traces, which no longer required 
exclusive access to the file.

11) Final details
fixtool was originally designed to by used with the UniVerse administration 
client, then UVAdmin (pre-release
10) and now UniAdmin (release 10 and higher). It was designed as the 
to UVFIXFILE, which is
has not been enhanced since UniVerse release 9.5.27. Of the two file repair 
tools it is the only one designed to
work with both 23-bit and 64-bit files. It was not documented in any UniVerse 
publication except in the
UniVerse Troubleshooting guide and this white paper.
The administration clients do not call it with any arguments other than 
specifying –file and –fix8. Enhancements
to UniAdmin to include more options from fixtool similar to the command line 
planned for UniVerse 10.1.
fixtool works only on 32-bit and 64-bit UniVerse files, and supports file types 
2 – 18 and 30.
fixtool requires UniVerse to be running. At releases earlier than 10.0, it may 
only run on the release for which it
was built as the signature in the program is compared to the disk shared memory 
signature. As of release 10.1,
fixtool from any 10.0.x release will work within 10.0.x. For example, a build 
fixtool at 10.0.4 for Windows
will work at 10.0.0 for Windows.

This is a very powerful tool and should be used in preference to uvfixfile. I 
have never found a file it couldn't fix/help fix. It is in the bin directory of 
the main uv account and should be run as root/administrator.



 From: "Holt, Jake" <>
To: U2 Users List <> 
Sent: Thursday, 18 April 2013, 18:23
Subject: Re: [U2] blink error?

Sorry, I hate to keep bombing this with questions especially since this
might be a totally unanswerable question, but generally is fixing the
file a long process?  It's a 268mb file and it's been running for 38
minutes.  Is that typical?  Just making sure it's not something that
should have taken 38 seconds and there is something else getting in the

Been sitting here since I started it:



ERROR: Processing Primary group 3786, Overflow group 134428.

Invalid group buffer chain at address 0x1068e000.

Bad link to overflow buffer 134428.

Attempting to unlink buffer at 0x1068e000.

-----Original Message-----
[] On Behalf Of Israel, John
Sent: Thursday, April 18, 2013 11:26 AM
To: U2 Users List
Subject: Re: [U2] blink error?

I have not seen that in a long time.  Used to occasionally get it in
UniVerse on an AIX box.  I think it stands for backward link (blink).

Simply listing or selecting the file will fail when it hits the
offending data.

If you can detect the key that is failing, the "simple" solution used to
be to try to copy the record to a temp file, delete the original record
(which fixes the link), then copy it back.

If that fails, you will likely need to run the fix file utility.

Again, I have not seen this in 10 years or so, so my memory may be a
little off.

Good luck!


-----Original Message-----
[] On Behalf Of Holt, Jake
Sent: Thursday, April 18, 2013 12:20 PM
To: U2 Users List
Subject: [U2] blink error?

Never seen this error message before, no sure on the severity but I hope
it's easy to fix:


  Computed blink of 0x765800 does not match expected blink of 0x765000!

  Detected within group starting at address 0x1068E000!  

Any input as to what I need to do to resolve it?


Jake Holt l samsill l Information Technology Director
(817) 536 - 1906 x 217 l

U2-Users mailing list
U2-Users mailing list

U2-Users mailing list
U2-Users mailing list

U2-Users mailing list

U2-Users mailing list

Reply via email to