Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 10 of 17 total |
Having Corrupt headers using 4.25 build 3 |
Thu, Jan 25 2007 5:19 PM | Permanent Link |
"Bern Rudisill" | Hello I have been using 4.25 build 1, in our the last update of our
applicaiton I updated to 4.25 build 3, now we are having quite a few of our customers getting corrupt headers in various tables multiple times in the day. This did not happen in 4.25 build 1. The only things that changed DB wise is update to build 3 and adding the DBISAM server to enable large file support. Any Ideas Bern -- |
Fri, Jan 26 2007 3:28 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bern,
<< Hello I have been using 4.25 build 1, in our the last update of our applicaiton I updated to 4.25 build 3, now we are having quite a few of our customers getting corrupt headers in various tables multiple times in the day. This did not happen in 4.25 build 1. The only things that changed DB wise is update to build 3 and adding the DBISAM server to enable large file support. >> Are there any applications besides the DBISAM server directly accessing the database tables ? If so, then they must *all* be using LargeFileSupport=True or else you'll get all sorts of corruption because they won't respect each other's locks. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Jan 26 2007 4:59 PM | Permanent Link |
"Bern Rudisill" | Tim Young [Elevate Software] wrote:
> Bern, > > << Hello I have been using 4.25 build 1, in our the last update of > our applicaiton I updated to 4.25 build 3, now we are having quite a > few of our customers getting corrupt headers in various tables > multiple times in the day. This did not happen in 4.25 build 1. The > only things that changed DB wise is update to build 3 and adding the > DBISAM server to enable large file support. >> > > Are there any applications besides the DBISAM server directly > accessing the database tables ? If so, then they must all be using > LargeFileSupport=True or else you'll get all sorts of corruption > because they won't respect each other's locks. Ok That would explain it, I do have 2 services that access the tables that large file support was not turned on in. Thanks Bern -- |
Mon, Jan 29 2007 11:02 AM | Permanent Link |
"Bern Rudisill" | Bern Rudisill wrote:
> Tim Young [Elevate Software] wrote: > > > Bern, > > > > << Hello I have been using 4.25 build 1, in our the last update of > > our applicaiton I updated to 4.25 build 3, now we are having quite a > > few of our customers getting corrupt headers in various tables > > multiple times in the day. This did not happen in 4.25 build 1. The > > only things that changed DB wise is update to build 3 and adding the > > DBISAM server to enable large file support. >> > > > > Are there any applications besides the DBISAM server directly > > accessing the database tables ? If so, then they must all be using > > LargeFileSupport=True or else you'll get all sorts of corruption > > because they won't respect each other's locks. > > Ok That would explain it, I do have 2 services that access the tables > that large file support was not turned on in. > > Thanks > Bern Ok I turned off large file support in my app for the moment and that has stopped the most of corruption we were getting. But I do have one table that keeps getting corrupted. This is a read only table and there is nowhere in my code that writes to the table, any idea why the headers keep getting corrupt? Bern -- |
Mon, Jan 29 2007 6:23 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bern,
<< Ok I turned off large file support in my app for the moment and that has stopped the most of corruption we were getting. But I do have one table that keeps getting corrupted. This is a read only table and there is nowhere in my code that writes to the table, any idea why the headers keep getting corrupt? >> Something must be writing to it in order to cause a header corrupt error message. The header corrupt message is caused by the reader not respecting the locks of the writer, so that the reader tries to read data (like the table header) while it is in an inconsistent state. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Jan 29 2007 8:13 PM | Permanent Link |
"Bern Rudisill" | Tim Young [Elevate Software] wrote:
> Bern, > > << Ok I turned off large file support in my app for the moment and > that has stopped the most of corruption we were getting. But I do > have one table that keeps getting corrupted. This is a read only > table and there is nowhere in my code that writes to the table, any > idea why the headers keep getting corrupt? >> > > Something must be writing to it in order to cause a header corrupt > error message. The header corrupt message is caused by the reader > not respecting the locks of the writer, so that the reader tries to > read data (like the table header) while it is in an inconsistent > state. I thought of that also, but trust me there is nothing writting to the table, the only code in my program is a select statement and when I create the query I set readonly to true. This one has me baffled. Would a hiccup in network traffic make it look like the header is corrupt? This is in a file share enviroment by the way not client server. Bern -- |
Tue, Jan 30 2007 5:34 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bern,
<< I thought of that also, but trust me there is nothing writting to the table, the only code in my program is a select statement and when I create the query I set readonly to true. This one has me baffled. Would a hiccup in network traffic make it look like the header is corrupt? >> Not normally, no. Normally network issues show up as OS read or write errors, not DBISAM-specific errors. What OS is being used here ? -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Jan 31 2007 11:57 AM | Permanent Link |
"Bern Rudisill" | Tim Young [Elevate Software] wrote:
> Bern, > > << I thought of that also, but trust me there is nothing writting to > the table, the only code in my program is a select statement and when > I create the query I set readonly to true. This one has me baffled. > Would a hiccup in network traffic make it look like the header is > corrupt? >> > > Not normally, no. Normally network issues show up as OS read or > write errors, not DBISAM-specific errors. > > What OS is being used here ? Workstation is Windows XP SP2, server is windows 2000, running in file share mode. -- |
Wed, Jan 31 2007 2:59 PM | Permanent Link |
"Robert" | "Bern Rudisill" <bernr@no-sp.am.exitcare dot com> wrote in message news:69C75E07-156D-4EA5-A0BC-3CAAC10C83C5@news.elevatesoft.com... > > Ok I turned off large file support in my app for the moment and that > has stopped the most of corruption we were getting. But I do have one > table that keeps getting corrupted. This is a read only table and there > is nowhere in my code that writes to the table, any idea why the > headers keep getting corrupt? > Does the file date change? Robert |
Wed, Jan 31 2007 4:31 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Robert,
<< Does the file date change? >> Good question. I was also going to ask if the LastUpdated timestamp changes for the table in DBISAM. -- Tim Young Elevate Software www.elevatesoft.com |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |