Blink Error

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Blink Error

Anmol Chandrakant Khopade
Hi,

I am receiving the following error:

Computed blink of 0xB44 does not match expected blink of 0x0!

Detected within group starting at address 0x80000000!

Internal data error.

I am having a 2GB Data 30 file, which got locked due to unix restriction on file size.

A unibasic program has been written to purge the data in this file.

I imported the 2GB file to another universe box which is a replica of the original box and also contains the above file, and reconfigured the VOC pointer of the local file to point to the 2GB file.

This error came in while selecting the records.

Please let me know if any one knows a work around or has any information about this.

Thanks in advance

Warm regards

Anmol



**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/
Reply | Threaded
Open this post in threaded view
|

Re: Blink Error - Backward Link error

Stephen O'Neal
Anmol,

I don't have good news.

You have a broken file due to a mismatched backward link (blink).  This
occurred when the file attempted to expand past the 2gb limit on a static
file by trying to extend an overflow block.

Any attempt to SELECT or SSELECT the file will fail when it reaches the
broken group.   :^(

Your alternatives at this point are:
1) restore the last know valid backup of the file and rebuild the data
2) contact the company where you purchased your U2 licenses.  Their U2
Support organization will put you in touch with someone that can fix the
file (for a fee).  When they fix the file, the file will be truncated at
the group where this occurred.  This can be anywhere in the file, because
the group extended for overflow can be anywhere in the file.  You may end
up with a file that is considerably smaller than your original file!

A wake up call for others:  Watch out for your 2gb file limits on static
files.

Good luck in recovering your data!

Regards,
   Steve

   Stephen M. O'Neal, CDP &  IBM U2 Certified
   Services Sales Specialist
   North America U2 Lab Services
   Information Management, IBM Software Group




"Anmol Chandrakant Khopade" <[hidden email]>
Sent by: [hidden email]
09/27/2005 07:37 PM
Please respond to
u2-users


To
<[hidden email]>
cc

Subject
[U2] Blink Error






Hi,

I am receiving the following error:

Computed blink of 0xB44 does not match expected blink of 0x0!

Detected within group starting at address 0x80000000!

Internal data error.

I am having a 2GB Data 30 file, which got locked due to unix restriction
on file size.

A unibasic program has been written to purge the data in this file.

I imported the 2GB file to another universe box which is a replica of the
original box and also contains the above file, and reconfigured the VOC
pointer of the local file to point to the 2GB file.

This error came in while selecting the records.

Please let me know if any one knows a work around or has any information
about this.

Thanks in advance

Warm regards

Anmol



**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
solely for the use of the addressee(s). If you are not the intended
recipient, please notify the sender by e-mail and delete the original
message. Further, you are not to copy, disclose, or distribute this e-mail
or its contents to any other person and any such actions are unlawful.
This e-mail may contain viruses. Infosys has taken every reasonable
precaution to minimize this risk, but is not liable for any damage you may
sustain as a result of any virus in this e-mail. You should carry out your
own virus checks before opening the e-mail or attachment. Infosys reserves
the right to monitor and review the content of all messages sent to or
from this e-mail address. Messages sent to or from this e-mail address may
be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/
Reply | Threaded
Open this post in threaded view
|

Re: Blink Error - Backward Link error

karlp-3
Correction, you should only see loss of data after the BLINK error in he
affected group only.

Karl Pearson
Senior uniVerse DBA and one who cut his teeth fixing blinks by hand
(thanks to Mark Baldridge and Joel Yates).

<quote who="Stephen O'Neal">

> Anmol,
>
> I don't have good news.
>
> You have a broken file due to a mismatched backward link (blink).  This
> occurred when the file attempted to expand past the 2gb limit on a static
> file by trying to extend an overflow block.
>
> Any attempt to SELECT or SSELECT the file will fail when it reaches the
> broken group.   :^(
>
> Your alternatives at this point are:
> 1) restore the last know valid backup of the file and rebuild the data
> 2) contact the company where you purchased your U2 licenses.  Their U2
> Support organization will put you in touch with someone that can fix the
> file (for a fee).  When they fix the file, the file will be truncated at
> the group where this occurred.  This can be anywhere in the file, because
> the group extended for overflow can be anywhere in the file.  You may end
> up with a file that is considerably smaller than your original file!
>
> A wake up call for others:  Watch out for your 2gb file limits on static
> files.
>
> Good luck in recovering your data!
>
> Regards,
>    Steve
>
>    Stephen M. O'Neal, CDP &  IBM U2 Certified
>    Services Sales Specialist
>    North America U2 Lab Services
>    Information Management, IBM Software Group
>
>
>
>
> "Anmol Chandrakant Khopade" <[hidden email]>
> Sent by: [hidden email]
> 09/27/2005 07:37 PM
> Please respond to
> u2-users
>
>
> To
> <[hidden email]>
> cc
>
> Subject
> [U2] Blink Error
>
>
>
>
>
>
> Hi,
>
> I am receiving the following error:
>
> Computed blink of 0xB44 does not match expected blink of 0x0!
>
> Detected within group starting at address 0x80000000!
>
> Internal data error.
>
> I am having a 2GB Data 30 file, which got locked due to unix restriction
> on file size.
>
> A unibasic program has been written to purge the data in this file.
>
> I imported the 2GB file to another universe box which is a replica of the
> original box and also contains the above file, and reconfigured the VOC
> pointer of the local file to point to the 2GB file.
>
> This error came in while selecting the records.
>
> Please let me know if any one knows a work around or has any information
> about this.
>
> Thanks in advance
>
> Warm regards
>
> Anmol
>
>
>
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
> solely for the use of the addressee(s). If you are not the intended
> recipient, please notify the sender by e-mail and delete the original
> message. Further, you are not to copy, disclose, or distribute this e-mail
> or its contents to any other person and any such actions are unlawful.
> This e-mail may contain viruses. Infosys has taken every reasonable
> precaution to minimize this risk, but is not liable for any damage you may
> sustain as a result of any virus in this e-mail. You should carry out your
> own virus checks before opening the e-mail or attachment. Infosys reserves
> the right to monitor and review the content of all messages sent to or
> from this e-mail address. Messages sent to or from this e-mail address may
> be stored on the Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
> -------
> u2-users mailing list
> [hidden email]
> To unsubscribe please visit http://listserver.u2ug.org/
> -------
> u2-users mailing list
> [hidden email]
> To unsubscribe please visit http://listserver.u2ug.org/
>


--
karl

     _/  _/      _/      _/_/_/       ____________   __o
    _/ _/       _/      _/    _/     ____________  _-\<._
   _/_/        _/      _/_/_/                     (_)/ (_)
  _/ _/       _/      _/           ......................
 _/   _/ arl _/_/_/  _/ earson    [hidden email]

--
IT Director, ATS Industrial Supply, Inc.
http://www.atsindustrial.com
Toll-free: 800-789-9300 x29
Direct2Desk: 801-978-4429
Facsimile: 801-972-3888
--
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/
Reply | Threaded
Open this post in threaded view
|

Re: Blink Error - Backward Link error

Stephen O'Neal
Good Catch Karl!

Light bulb went off... Yes it truncates the group, not the file.  I
remember Mark talking that if a file is tremendously undersized and has
lots of overflow groups, the damage would be more severe.  Really makes
sense now.
   Steve

>Correction, you should only see loss of data after the BLINK error in he
>affected group only.

>Karl Pearson
>Senior uniVerse DBA and one who cut his teeth fixing blinks by hand
>(thanks to Mark Baldridge and Joel Yates).

<quote who="Stephen O'Neal">
> Anmol,
>
>...When they fix the file, the file will be truncated at
> the group where this occurred.  This can be anywhere in the file,
because
> the group extended for overflow can be anywhere in the file.  You may
end

> up with a file that is considerably smaller than your original file!
>
> A wake up call for others:  Watch out for your 2gb file limits on static
> files.
>
> Good luck in recovering your data!
>
> Regards,
>    Steve
>
> "Anmol Chandrakant Khopade" <[hidden email]>
>
> Hi,
>
> I am receiving the following error:
>
> Computed blink of 0xB44 does not match expected blink of 0x0!
>
> Detected within group starting at address 0x80000000!
>
> Internal data error.
>
> ...
>
> Warm regards
>
> Anmol
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/
Reply | Threaded
Open this post in threaded view
|

Re: Blink Error - Backward Link error

Martin Phillips
Why, oh why, doesn't UV fail the write before it corrupts the file? It is
trivial to know that this is about to happen.


Martin Phillips
Ladybridge Systems
17b Coldstream Lane, Hardingstone, Northampton NN4 6DB
+44-(0)1604-709200
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/
Reply | Threaded
Open this post in threaded view
|

FW: Blink Error - Backward Link error

CStevenson-2
In reply to this post by Stephen O'Neal
Do I detect an enhancement suggestion?
Whether this is trivial or hard is beyond me, but I tend to believe Mr.
Phillips.
(On this subject, anyway.  I don't know his opinion of the British
Royals, for example.)

cds

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Martin Phillips
Sent: Wednesday, September 28, 2005 1:11 AM
To: [hidden email]
Subject: Re: [U2] Blink Error - Backward Link error

Why, oh why, doesn't UV fail the write before it corrupts the file? It
is trivial to know that this is about to happen.


Martin Phillips
Ladybridge Systems
17b Coldstream Lane, Hardingstone, Northampton NN4 6DB
+44-(0)1604-709200
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/
Reply | Threaded
Open this post in threaded view
|

Re: Blink Error - Backward Link error

karlp-3
In reply to this post by Martin Phillips
Wow, what a concept! But then, that would reduce a bit of job security for
folks like me, wouldn't it? I've always told clients going in that if I do
my job right, I'll be out of a job. Yes, I tell my clients that. It's
basically true, but there are certainly glaring exceptions.

Karl

<quote who="Martin Phillips">

> Why, oh why, doesn't UV fail the write before it corrupts the file? It is
> trivial to know that this is about to happen.
>
>
> Martin Phillips
> Ladybridge Systems
> 17b Coldstream Lane, Hardingstone, Northampton NN4 6DB
> +44-(0)1604-709200
> -------
> u2-users mailing list
> [hidden email]
> To unsubscribe please visit http://listserver.u2ug.org/
>


--
karl

     _/  _/      _/      _/_/_/       ____________   __o
    _/ _/       _/      _/    _/     ____________  _-\<._
   _/_/        _/      _/_/_/                     (_)/ (_)
  _/ _/       _/      _/           ......................
 _/   _/ arl _/_/_/  _/ earson    [hidden email]

--
IT Director, ATS Industrial Supply, Inc.
http://www.atsindustrial.com
Toll-free: 800-789-9300 x29
Direct2Desk: 801-978-4429
Facsimile: 801-972-3888
--
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/
Reply | Threaded
Open this post in threaded view
|

RE: Blink Error - Backward Link error

Glenn Herbert
In reply to this post by Stephen O'Neal
   Because of the manner in which the write subsystem was implemented, it
   is  NOT  a  trivial task to either pre-detect or recover from a system
   write  failure,  which  is  usually the cause of the corruption.   The
   group  structure  (which  will be comprised of one or more buffers) is
   modified  in  memory,  and then shipped off to the system for writing;
   there  is no way to determine if in fact any particular write actually
   made  it  TO  disk.   If a write() operation returned successful, then
   that is the only validation we can check;  if the system burps on that
   buffer  later down the chain, there is no way to detect that.   Having
   spent  better  than  10  years  in  the file system, there was serious
   discussion  of  how  to  do  this,  but  unfortunately required a very
   serious  rewrite  of  the  write subsystem; obviously, that work would
   never be done.  The various recovery tools shipped with the product do
   a pretty decent job of recovering as much of the file as possible.

   Hope this helps.

   ______________________________________________________________________

   From: [hidden email]
   [mailto:[hidden email]]  On  Behalf Of "Stevenson,
   Charles" <[hidden email]>
   Sent: Wednesday, September 28, 2005 8:10 AM
   To: <[hidden email]>
   Subject: FW: [U2] Blink Error - Backward Link error

   Do I detect an enhancement suggestion?
   Whether  this  is  trivial or hard is beyond me, but I tend to believe
   Mr.
   Phillips.
   (On this subject, anyway. I don't know his opinion of the British
   Royals, for example.)
   cds
   -----Original Message-----
   From: [hidden email]
   [mailto:[hidden email]]   On   Behalf   Of  Martin
   Phillips
   Sent: Wednesday, September 28, 2005 1:11 AM
   To: [hidden email]
   Subject: Re: [U2] Blink Error - Backward Link error
   Why, oh why, doesn't UV fail the write before it corrupts the file? It
   is trivial to know that this is about to happen.
   Martin Phillips
   Ladybridge Systems
   17b Coldstream Lane, Hardingstone, Northampton NN4 6DB
   +44-(0)1604-709200
   -------
   u2-users mailing list
   [hidden email]
   To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/
Reply | Threaded
Open this post in threaded view
|

RE: Blink Error - Backward Link error

karlp-3
This is a good explanation I'd forgotten about. You were probably the one
who explained it to me a little time ago... Long time...

Karl

<quote who="Glenn Herbert">

>    Because of the manner in which the write subsystem was implemented, it
>    is  NOT  a  trivial task to either pre-detect or recover from a system
>    write  failure,  which  is  usually the cause of the corruption.   The
>    group  structure  (which  will be comprised of one or more buffers) is
>    modified  in  memory,  and then shipped off to the system for writing;
>    there  is no way to determine if in fact any particular write actually
>    made  it  TO  disk.   If a write() operation returned successful, then
>    that is the only validation we can check;  if the system burps on that
>    buffer  later down the chain, there is no way to detect that.   Having
>    spent  better  than  10  years  in  the file system, there was serious
>    discussion  of  how  to  do  this,  but  unfortunately required a very
>    serious  rewrite  of  the  write subsystem; obviously, that work would
>    never be done.  The various recovery tools shipped with the product do
>    a pretty decent job of recovering as much of the file as possible.
>
>    Hope this helps.
>
>    ______________________________________________________________________
>
>    From: [hidden email]
>    [mailto:[hidden email]]  On  Behalf Of "Stevenson,
>    Charles" <[hidden email]>
>    Sent: Wednesday, September 28, 2005 8:10 AM
>    To: <[hidden email]>
>    Subject: FW: [U2] Blink Error - Backward Link error
>
>    Do I detect an enhancement suggestion?
>    Whether  this  is  trivial or hard is beyond me, but I tend to believe
>    Mr.
>    Phillips.
>    (On this subject, anyway. I don't know his opinion of the British
>    Royals, for example.)
>    cds
>    -----Original Message-----
>    From: [hidden email]
>    [mailto:[hidden email]]   On   Behalf   Of  Martin
>    Phillips
>    Sent: Wednesday, September 28, 2005 1:11 AM
>    To: [hidden email]
>    Subject: Re: [U2] Blink Error - Backward Link error
>    Why, oh why, doesn't UV fail the write before it corrupts the file? It
>    is trivial to know that this is about to happen.
>    Martin Phillips
>    Ladybridge Systems
>    17b Coldstream Lane, Hardingstone, Northampton NN4 6DB
>    +44-(0)1604-709200
>    -------
>    u2-users mailing list
>    [hidden email]
>    To unsubscribe please visit http://listserver.u2ug.org/
> -------
> u2-users mailing list
> [hidden email]
> To unsubscribe please visit http://listserver.u2ug.org/
>


--
karl

     _/  _/      _/      _/_/_/       ____________   __o
    _/ _/       _/      _/    _/     ____________  _-\<._
   _/_/        _/      _/_/_/                     (_)/ (_)
  _/ _/       _/      _/           ......................
 _/   _/ arl _/_/_/  _/ earson    [hidden email]

--
IT Director, ATS Industrial Supply, Inc.
http://www.atsindustrial.com
Toll-free: 800-789-9300 x29
Direct2Desk: 801-978-4429
Facsimile: 801-972-3888
--
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/
Reply | Threaded
Open this post in threaded view
|

Re: Blink Error

APflueger
In reply to this post by Anmol Chandrakant Khopade
May I suggest running "guide" on the data file to see if there is
corruption?

Andy


On 9/27/05, Anmol Chandrakant Khopade <[hidden email]> wrote:

>
> Hi,
>
> I am receiving the following error:
>
> Computed blink of 0xB44 does not match expected blink of 0x0!
>
> Detected within group starting at address 0x80000000!
>
> Internal data error.
>
> I am having a 2GB Data 30 file, which got locked due to unix restriction
> on file size.
>
> A unibasic program has been written to purge the data in this file.
>
> I imported the 2GB file to another universe box which is a replica of the
> original box and also contains the above file, and reconfigured the VOC
> pointer of the local file to point to the 2GB file.
>
> This error came in while selecting the records.
>
> Please let me know if any one knows a work around or has any information
> about this.
>
> Thanks in advance
>
> Warm regards
>
> Anmol
>
>
>
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
> solely for the use of the addressee(s). If you are not the intended
> recipient, please notify the sender by e-mail and delete the original
> message. Further, you are not to copy, disclose, or distribute this e-mail
> or its contents to any other person and any such actions are unlawful. This
> e-mail may contain viruses. Infosys has taken every reasonable precaution
to

> minimize this risk, but is not liable for any damage you may sustain as a
> result of any virus in this e-mail. You should carry out your own virus
> checks before opening the e-mail or attachment. Infosys reserves the right
> to monitor and review the content of all messages sent to or from this
> e-mail address. Messages sent to or from this e-mail address may be stored
> on the Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
> -------
> u2-users mailing list
> [hidden email]
> To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[hidden email]
To unsubscribe please visit http://listserver.u2ug.org/