Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Message-ID: <452681E1.4080206@sbcglobal.net>
Date: Fri, 06 Oct 2006 09:18:41 -0700
From: Mike Matrigali <mikem_app@sbcglobal.net>
Reply-To: mikem_app@sbcglobal.net
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: SQLSTATE: XSDG0Page Page(7,Container(0, 848)) could not be read
 from disk.
References: <45259FBC.8040200@nuix.com.au>
In-Reply-To: <45259FBC.8040200@nuix.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

There may or may not be more information in the derby.log.  Are you 
getting any disk errors, does the file seg0/c350.dat exist and have 
reasonable permissions.  My guess (but there really is not enough
info here) is that recovery is trying to access page 7 of container 848 
(seg0/c350.dat), and for some reason it can't.  Those reasons could be
that the file does not exist/bad permission, disk error reading that
sector, file is not that long.

What derby version are you using?


David Sitsky wrote:
> Hi,
> 
> we have a client using a derby database, sometimes accessed in networked 
> mode, and sometimes as an embedded database.  It can no longer be opened 
> successfully, as Derby is now returning the following messages when the 
> database is being opened:
> 
> DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ040, SQLERRMC: Failed to start 
> database '...', see the next exception for details.
> 
> SQLSTATE: XSDG0Page Page(7,Container(0, 848)) could not be read from disk.
> 
> Is this a sign that the database has been corrupted, or is there another 
> issue here?  Is there anything which can be done about this?
>