Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 4 of 4 total |
8965 Error with Memory Table |
Thu, May 7 2015 5:03 PM | Permanent Link |
Xazzy | Hi
I have an in-memory table (i.e. database name: "Memory"). Sometimes after I fill it and commence navigation I receive an 8965 Error: Index page buffers corrupt in table MemTable3. The table is filled with folder files, and it always fails on a specific folder, so clearly it is something about the data I insert that is causing the error. I'm just looking for some advice on things to look for, i.e. what might corrupt the index of a memory table? Thanks DBISAM Version: 4.26 Build 3 Delphi 2007 Windows 8 |
Thu, May 7 2015 5:39 PM | Permanent Link |
Raul Team Elevate | On 5/7/2015 5:03 PM, Xazzy wrote:
> I have an in-memory table (i.e. database name: "Memory"). Sometimes after I fill it and commence navigation I receive an 8965 Error: Index page buffers corrupt in table MemTable3. The table is filled with folder files, and it always fails on a specific folder, so clearly it is something about the data I insert that is causing the error. > I'm just looking for some advice on things to look for, i.e. what might corrupt the index of a memory table? You're not giving us much to work with here. Can you share what is the data (folder name) that is in the record that causes the error ? What are the indexes defined on the table ? Is the app multi-threaded and is there any chance it's multiple thread accessing the table type of issue ? You might want to contact support direct (support@elevatesoft.com) for faster response if this is urgent. Raul |
Thu, May 7 2015 7:16 PM | Permanent Link |
Xazzy | Hi Raul
Sorry, yes that was a bit vague, but I just needed some advice on when this kind of error might arise on a memory table, so I knew what to check. As it happens, I since fixed an AV in a totally unrelated bit of code and that seems to have resolved it. Thanks |
Thu, May 7 2015 8:10 PM | Permanent Link |
Raul Team Elevate | On 5/7/2015 7:16 PM, Xazzy wrote:
> As it happens, I since fixed an AV in a totally unrelated bit of code and that seems to have resolved it. Thanks for the update. Depending on how you handled the AV this might have an effect as it might reasult in improper close/finalization (for example killing a process/thread that has DBISAM objects open (and maybe even in the middle of an operation like insert) might result in problems with table). Raul |
This web page was last updated on Friday, April 19, 2024 at 07:09 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |