Support Forums - View Thread

View Thread

The following is the text of the current message along with any replies.

Messages 1 to 8 of 8 total

#8963 BLOB Buffers Corrupt Error: What builds of DBISAM have this issue?

Fri, Aug 28 2009 9:50 PM	Permanent Link
Sam Jones	RE case #3039 Issue: Inserting and Deleting Records with BLOB Fields Can Cause #8963 BLOB Buffers Corrupt Error Question: Is this problem in all builds of 4.2x ? I have seen this in our application logs (we use a build from 1 or 2 years back). Please advise! Thanks!
Mon, Aug 31 2009 3:09 PM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Sam, << Is this problem in all builds of 4.2x ? >> Yes, that is most likely the case. << I have seen this in our application logs (we use a build from 1 or 2 years back). >> Are you using optimistic record locking ? (TDBISAMSession.RecordLockProtocol=lpOptimistic) -- Tim Young Elevate Software www.elevatesoft.com
Tue, Oct 6 2009 12:19 PM	Permanent Link
Sam Jones	>> Are you using optimistic record locking ? >> (TDBISAMSession.RecordLockProtocol=lpOptimistic) Looks like we are using the default for RecordLockProtocol, which appears to be pessimistic (right?)
Tue, Oct 6 2009 12:36 PM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Sam, << Looks like we are using the default for RecordLockProtocol, which appears to be pessimistic (right?) >> Correct. -- Tim Young Elevate Software www.elevatesoft.com
Tue, Oct 6 2009 1:02 PM	Permanent Link
Sam Jones	Sooooo what is the answer to the question? >>>>>>> RE case #3039 Issue: Inserting and Deleting Records with BLOB Fields Can Cause #8963 BLOB Buffers Corrupt Error Question: Is this problem in all builds of 4.2x ? I have seen this in our application logs (we use build 4.23 or 4.25). Please advise! <<<<<<<<<<<<
Tue, Oct 6 2009 3:16 PM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Sam, << Sooooo what is the answer to the question? >> I already answered your question. The resolution to the problem is to use the fixed version/build indicated in the incident report under "Resolution". -- Tim Young Elevate Software www.elevatesoft.com
Tue, Oct 6 2009 7:49 PM	Permanent Link
Sam Jones	>> I already answered your question. The resolution to the problem is to use >> the fixed version/build indicated in the incident report under "Resolution". Sorry, I misunderstood! When you asked: >> Are you using optimistic record locking ? It sounded like the fixed build is only needed if specific options are used for the optimistic record locking property. I misunderstood? The next step is to upgrade dbisam, regardless of record locking options? Thanks!
Wed, Oct 7 2009 1:04 PM	Permanent Link
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com	Sam, << It sounded like the fixed build is only needed if specific options are used for the optimistic record locking property. >> It is - the problem was with optimistic record locking. -- Tim Young Elevate Software www.elevatesoft.com