Re: Getting fail to start database and unknown page format Exception

2015-01-14 Thread Bryan Pendleton

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



Re: Getting fail to start database and unknown page format Exception

2015-01-14 Thread mike matrigali

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


Getting fail to start database and unknown page format Exception

2015-01-14 Thread thanmayi
Hi,
We are in the Apache Derby - 10.8.2.2 version. We are getting repeated
exception in derby logs stating 1)java.sql.SQLException: Database
'/usr/ironhide/var/db/piprepository/derby' not found. 
2)java.sql.SQLException: Database '/usr/ironhide/var/db/remote/derby' not
found.
3)java.sql.SQLException: Database '/usr/ironhide/var/db/agent/AgentDB' not
found.
4)java.sql.SQLException: Database '/usr/ironhide/var/db/thirdparty/derby'
not found.
5)java.sql.SQLException: Database
'/usr/ironhide/var/db/connectorrepository/derby' not found.
6)Failed to start database '/usr/ironhide/var/db/thirdparty/derby' 
7) ERROR XSDBB: Unknown page format at page Page(302,Container(0, 560)),
page dump follows: Hex dump:


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 ? 

Our Product Environment is , we have Java application where 2 java processes
connects to derby and perform operations. Both the java processes contacts 
derby databases (sometime same database) asynchronously frequently. We are
using network Derby.  

We suspect its a bug in the derby ?? do we get any patch for this ? 
we have attached the logs for further analysis.



--
View this message in context: 
http://apache-database.10148.n7.nabble.com/Getting-fail-to-start-database-and-unknown-page-format-Exception-tp143610.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.