A production system with a database of about 400G received this error today and
it appears that Derby shutdown parts of itself because from that point on it
was spitting out errors saying it could not find the database. The system was
restarted and came up clean and is working with no issues
ERROR XSDG0: Page Page(1325564,Container(0, 30832)) could not be read from disk.
Caused by: java.io.EOFException: Reached end of file while attempting to read a
whole page.
Does the derby.log have any more detail about this specific exception?
Note that you can use the system tables
I will try to update that shortly. Thanks.
-Original Message-
From: Bryan Pendleton [mailto:bpendleton.de...@gmail.com]
Sent: Wednesday, September 02, 2015 11:08 PM
To: derby-dev@db.apache.org
Subject: Re: Need help understanding a database deadlock that was detected
> I guess what I
On 9/3/2015 3:35 PM, Bergquist, Brett wrote:
Reached end of file while attempting to read a whole page
You should probably take a close read through all the
discussion on this slightly old Derby JIRA Issue:
https://issues.apache.org/jira/browse/DERBY-5234
There are some suggestions about how
I agree with all of bryan's suggestions. If you can't get access to the actual
db there is not
much to be done. My usual customer support answer to this situation would be
to tell you to
shut the db and do a consistency check on it, which would read every page from
the table
and would
only should we vote on announcing with 10.12 release sunsetting jdk7 in
addition to jdk6 in 10.13?
On 8/30/2015 2:41 PM, Rick Hillegas wrote:
It's time to start buddy-testing 10.12.1:
http://wiki.apache.org/db-derby/DerbyTenTwelveOneRelease
I have published a preliminary version of the
