Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 10 of 17 total |
What means: DBISAM Engine Error # 8962 Data record buffers corrupt in the table" |
Mon, Jan 7 2008 2:23 PM | Permanent Link |
Sam Jones | Hello!
We are getting this message: DBISAM Engine Error # 8962 Data record buffers corrupt in the table ... What does it mean? |
Mon, Jan 7 2008 2:25 PM | Permanent Link |
Sam Jones | I should note: We are running 4.25, though it is hard to tell which flavor of
4.25. |
Mon, Jan 7 2008 2:26 PM | Permanent Link |
Sam Jones | OK, I see now:
ENGINE_VERSION = '4.25'; ENGINE_VERSION_NUM = 4.25; ENGINE_BUILD = '6'; ENGINE_BUILD_NUM = 6; |
Mon, Jan 7 2008 7:17 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Sam,
<< We are getting this message: DBISAM Engine Error # 8962 Data record buffers corrupt in the table .... What does it mean? >> Usually it means that the table in question is corrupt and needs to be repaired. If a repair doesn't report anything, then you should let me know the circumstances under which it occurs and I'll see if I can reproduce it here. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Jan 8 2008 12:44 PM | Permanent Link |
Sam Jones | Hello!
The dbisam repair functionality is not helping (we ran it, it makes no difference), The customer site is DOWN. What can I do to repair this problem? (URGENTly!!!) Cause: I have no idea what happened.... customer reports all was fine, and this happened out of blue. Please advise! |
Tue, Jan 8 2008 2:08 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Sam
On the (rare) occasions I have had this a repair has always fixed it. The following scenarios suggest themselves: 1. The repair wasn't done properly, or missed the corrupted table 2. The table was repaired but your software immediately corrupted it again 3. The disk is corrupt 4. You're operating in fileserver mode and there are bad network connections 5. You have a mixture of software accessing the tables with large file support enabled in some but not in others (not sure this one would give the error you're getting) Can you post some extra details 1. Is the application fileserver, clientserver or what 2. If multi user how many workstations, which OS's 3. Is the data stored on a separate server 4. Is the app single threaded or multi-threaded Roy Lambert |
Tue, Jan 8 2008 2:33 PM | Permanent Link |
Jason Lee | Also, make sure to do a repair **with index rebuilding** (there is a
checkbox that must be checked when selecting the table(s) to be repaired) ~J. Lee Roy Lambert wrote: > Sam > > > On the (rare) occasions I have had this a repair has always fixed it. The following scenarios suggest themselves: > > 1. The repair wasn't done properly, or missed the corrupted table > 2. The table was repaired but your software immediately corrupted it again > 3. The disk is corrupt > 4. You're operating in fileserver mode and there are bad network connections > 5. You have a mixture of software accessing the tables with large file support enabled in some but not in others (not sure this one would give the error you're getting) > > > Can you post some extra details > > 1. Is the application fileserver, clientserver or what > 2. If multi user how many workstations, which OS's > 3. Is the data stored on a separate server > 4. Is the app single threaded or multi-threaded > > Roy Lambert > |
Tue, Jan 8 2008 2:52 PM | Permanent Link |
Sam Jones | This db is local to the software that access it. Only a single process touches the db
(ever). There is no network between the code and the db. I will look into how the repair is being done. Thank you for the detail!!! |
Tue, Jan 8 2008 9:38 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Sam,
<< The dbisam repair functionality is not helping (we ran it, it makes no difference), >> Did you run it in the Database System Utility interactively ? If so, did the repair report anything in the repair log ? -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Jan 9 2008 8:35 PM | Permanent Link |
Sam Jones | I regret to report that this issue is wide open, the customer is completely down, and we
are unable to see or resolve the problem. The issue: The customer system reports error: DBISAM Engine Error # 8962 Data record buffers corrupt in the table ... and cpu use peaks in our process, permanently until we terminate the process. Now, the software at the customer prem is running a pre-4.25 version of DBISAM (either 4.21 or 4.23, I believe) We have a copy of the db here. Our current code is DBISAM 4.25 (as reported up this thread). Here, we see the problem that CPU utilization spikes and stays spiked, but there is no error from DBISAM. We have tried using the DBISAM tools, both from the earlier version of DBISAM and 4.25, to do repairs, with all the options, No problems are reported by the tools. But the repair process makes no difference. What do we do next? (the db is about 100MB zipped) |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Thursday, March 28, 2024 at 06:05 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |