db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: Derby db files get corrupted
Date Thu, 16 Feb 2006 09:10:15 GMT
wegorkie@interia.pl writes:

> Hi,
>
> I use Derby in my product which is personal finance manager written
> in Java. The app is standalone and has derby as embedded database
> which of course starts together with an app.
>
> The version of derby.jar (from manifest) is:
> Bundle-Name: Apache Derby 10.1
> Bundle-Version: 10.1.1000000.208786
>
> and I use embedded driver from the same jar:
> org.apache.derby.jdbc.EmbeddedDriver
>
> Now. I have a serious problem. The application is used by many
> users, and from time to time the database gets corrupted. I do not
> know what way. I have never such a corrupt on my desktop (I use my
> app as a user as well). I can maybe suppose that users are doing
> something wrong, or the other way that I do.  Anyway, after db files
> are corrupted, the data is lost. I don't know how to get them
> back. Are there any diagnostic tools for Derby? I don't see any.
> Well this is sample fragment from stacktrace from JDBC trying to
> open corrupted db:
>
> (...)
> Page Page(3,Container(0, 976)) is at version 755, the log file
> contains change version 5 564, either there are log records of this
> page missing, or this page did not get written out to disk
> properly. ERROR XSDB4: Page Page(3,Container(0, 976)) is at version
> 755, the log file contains change version 5 564, either there are
> log records of this page missing, or this page did not get written
> out to disk properly.

I have seen this error when I have deleted the database directory and
recreated the database, but not deleted the log directory. Could that
be your problem too?

-- 
Knut Anders


Mime
View raw message