Mailing-List: contact general-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@db.apache.org
Received-SPF: pass (athena.apache.org: domain of mcintyre.a@gmail.com
 designates 209.85.200.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=MDMtIBhgmDZeq6joetL0WOCc2k9hT3A7z3teyRt0VA/bzmyWByVGb2UmvzTztVH5D0HqmnudtP6fVouk4M1EGFRASmPt5QlTsdLPo4l8/P1rD+92ygBYbx0dtWcS9D2rkn+hQ8oNXj8gMYWyLQ/I1eHnOUAVlhm9/fAmkL+r/gY=
Message-ID: <54ac72d70805211242y29d4a0bcyf6ae518a7a8f1767@mail.gmail.com>
Date: Wed, 21 May 2008 12:42:25 -0700
From: "Andrew McIntyre" <mcintyre.a@gmail.com>
To: "Derby Discussion" <derby-user@db.apache.org>,
	"Derby Development" <derby-dev@db.apache.org>, general@db.apache.org
Subject: [ANNOUNCE] Apache Derby 10.3.3.0 released
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

The Apache Derby project is pleased to announce an important
maintenance release of Derby, 10.3.3.0.

Apache Derby is a subproject of the Apache DB project.
Derby is a pure Java relational database engine which conforms to the
ISO/ANSI SQL and JDBC standards. Derby aims to be easy for developers
and end-users to work with.

IMPORTANT NOTICE:

If you are currently using Derby 10.3.1.4 or Derby 10.3.2.1, it is strongly
recommended that you upgrade to Derby 10.4.1.3 or 10.3.3.0 to avoid
any chance of database corruption due to an issue with multiple threads
accessing a database that is documented in DERBY-3347.

This bug can cause unrecoverable database corruption during periods of
heavy, multi-thread I/O operations. The error produced in the test case
used to diagnose the problem was:

ERROR XSDB3: Container information cannot change once written: was 0, now 80.

It is felt that other errors might also be generated when this type of
corruption occurs. The corruption message will most likely refer to page 0
of the container. For example:

ERROR XSDG1: Page Page(0 ,Container(0, 5856)) could not be
written...

This bug corrupts the pages on disk and can go unnoticed. If you do not
run database consistency checks regularly it is recommended you begin doing
so as soon as possible after the upgrade. To insure that corruption has not
already occurred in existing databases, after upgrade run the database
consistency check at least once to validate all tables in the database. This
process is documented at:

http://wiki.apache.org/db-derby/DatabaseConsistencyCheck

If the corruption has already occurred there is no guaranteed recovery of data
other than to recover from the last good backup. When doing so one should
also check that the previous backup did not also have the corruption.

In some cases one may recover data from the existing
database, depending on the extent of the corruption, but will require
by hand data recovery. Depending on the type of corruption this may
be successful or not. one should consult the Derby list if attempting
this recovery - no automatic software solution to this recovery exists.

Version 10.3.3.0 can be downloaded from:
http://db.apache.org/derby/releases/release-10.3.3.0.cgi

Version 10.4.1.3 can be downloaded from:
http://db.apache.org/derby/releases/release-10.4.1.3.cgi

For help or questions, please post to the Derby User list.
For instructions on how to subcribe and post to the Derby User list,
please see:

http://db.apache.org/derby/derby_mail.html