db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mike matrigali <mikema...@gmail.com>
Subject Re: Getting fail to start database and unknown page format Exception
Date Wed, 14 Jan 2015 17:43:17 GMT
On 1/14/2015 6:34 AM, Bryan Pendleton wrote:
>> It looks like derby database is corrupt, and it is causing critical
>> problem
>> in our e derby.log
>> <http://apache-database.10148.n7.nabble.com/file/n143610/derby.log>
>> nd with
>> the huge business impact. And the path which its saying derby not
>> found is
>> valid and correct path . Still why suddenly derby got corrputed and
>> what are
>> the reasons for the corruption ?
>
> There are various possibilities:
>
> 1) You experienced a hard-disk failure on the disk holding
> /usr/ironhide/var/db
> 2) or, you experienced a power-failure which caused the operating system to
>     write incorrect data to the filesystem, or fail to flush its buffers
> properly,
>     perhaps because write-caching was enabled on the filesystem hardware
> 3) or, you filled up the filesystem /usr/ironhide/var/db, and all the
> databases
>     and their redo logs were on the same filesystem and all were damaged
>     simultaneously
> 4) or, some other piece of software, not Derby, wrote updates to the
> Derby files
>     directly
>
> There are certainly other possibilities.
>
> Have you inspected your system logs and talked to your system
> administrators
> for more information about what was going on at the moment that you noticed
> the problems?
>
> Do you have backups of these databases?
>
> Can you print the *full* exception logs from your attempts to access
> the databases (http://wiki.apache.org/db-derby/UnwindExceptionChain)
>
> thanks,
>
> bryan
>
>
I agree with bryan's suggestions.  A full derby.log may help.
The following also may be helpful:
https://wiki.apache.org/db-derby/DatabaseCorruption

Mime
View raw message