Tim

The error 8963 (BLOB buffers corrupt) can be raised in the same way of
described in #2157 error ?
I am using 4.22 build 4 in a C/S and my customer complains about it. If you
desire I have the table with this problem. I saw it error only was solved in
build 6 (not release yet). Am I right ?

Eduardo

Eduardo,

<< The error 8963 (BLOB buffers corrupt) can be raised in the same way of
described in #2157 error ? >>

No, that incident report only dealt with the "Invalid blob handle" error.

<< I am using 4.22 build 4 in a C/S and my customer complains about it. If
you desire I have the table with this problem. >>

Did you try repairing the table to see if it was actually corrupted ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

Yes, I've repaired the table and repair fix the error but it shouldn't be
possible in C/S. Server didn't crash. I can't think another reason to
produce this error ?

Eduardo

Eduardo,

<< Yes, I've repaired the table and repair fix the error but it shouldn't be
possible in C/S. Server didn't crash. I can't think another reason to
produce this error ? >>

So, the table was corrupted ?  Are you 100% sure that the database server
and/or machine were never shut down improperly ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>> So, the table was corrupted ?  
Yes it was.

>> Are you 100% sure that the database server and/or machine were never shut down improperly ?
Unfortunatelly yes but let's wait for another occurency because this table is used a lot and if the problem will occur again I will tell you.

Eduardo

Eduardo,

<< Unfortunatelly yes but let's wait for another occurency because this
table is used a lot and if the problem will occur again I will tell you. >>

The reason that I ask is that we haven't had any reports of the BLOB file
being corrupted that was traced back to a fault in DBISAM in any recent
version.  That could simply be due to chance, of course, but it sometimes is
an indicator of whether the problem may or may not lie.

--
Tim Young
Elevate Software
www.elevatesoft.com

In case it is the same issue, I thought I would mention that I have been
having a spate of file corruptions in one particular table.  When I repair
it, the log looks like...

Invalid BLOB offset in BLOB file for physical record # 232 (logical record ID
of 322), error fixed...

I have updated the server to the latest release and now wait to see if the
problem re-occurs.

For your info, I can also state categorically that these corruptions were
occurring without the server stopping.  I checked the "up time" and it proved
the process had been running continuously between the time I checked and
found it all ok, and the time I checked and found a corruption.

I note that the incident report referred to heavy activity being the trigger
of the problem, however, in my case, the app is not exactly stressing the
server!  There is very rarely more than one user accessing the system, and
there are no "programmed" accesses to the table in question, merely a bunch
of data aware controls responding to user interaction.

--Bill Sparrow--