I am using DBISAM v4.21 Build 10 and have for quite a while.  We have a
customer who is getting a fair amount of errors: DBISAM Error #8965 -
Index page buffers corrupt in table 'whatever'.

He doesn't seem to ever get any other corruption.  Does anyone know how
this can occur?  I recently did change some of the transaction handling
code to only include the tables being edited in the transaction.  Could
that have anything at all to do with it?

--
Thanks,
Michael Binette

Michael,

<< He doesn't seem to ever get any other corruption.  Does anyone know how
this can occur?  I recently did change some of the transaction handling code
to only include the tables being edited in the transaction.  Could that have
anything at all to do with it? >>

Yes, it's this issue:

http://www.elevatesoft.com/scripts/incident.dll?action=viewaddr&release=4.22&type=f&incident=2141

It doesn't cause corruption because the error occurs during reads that are
basically performing a "dirty" read of the indexes due to the lack of the
required write lock by the transaction when it is committing the
transaction.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

>
http://www.elevatesoft.com/scripts/incident.dll?action=viewaddr&release=4.22&type=f&incident=2141
This link does not work.

> It doesn't cause corruption because the error occurs during reads that are
> basically performing a "dirty" read of the indexes due to the lack of the
> required write lock by the transaction when it is committing the
> transaction.

I am converting some v3.30 tables to v4.24 and I am getting lots of error #8965.  Should I
just ignore this error?

It is also hard for me to tell my customers to ignore a database conversion error.

Regards,
KK Aw

Michael

<<
I am using DBISAM v4.21 Build 10 and have for quite a while.  We have a
customer who is getting a fair amount of errors: DBISAM Error #8965 -
Index page buffers corrupt in table 'whatever'.

He doesn't seem to ever get any other corruption.  Does anyone know how
this can occur?  I recently did change some of the transaction handling
code to only include the tables being edited in the transaction.  Could
that have anything at all to do with it?
>>

Yes. You must update to any higher version. I was having this error in the same way you
report but after upgrade (now I am using 4.22 build 4). This error disapear completelly.

Eduardo

KK,

<< I am converting some v3.30 tables to v4.24 and I am getting lots of error
#8965.  Should I just ignore this error? >>

If you're getting the error during the upgrade process while running the
upgrade inside of the Delphi IDE then yes, you should just ignore the error.
It is normal in that context and is internally trapped and handled by
DBISAM.

--
Tim Young
Elevate Software
www.elevatesoft.com