db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: Record not found in some SQL - Bug?
Date Thu, 29 Jan 2009 10:35:27 GMT
Rick Hillegas <Richard.Hillegas@Sun.COM> writes:

> jrgchip wrote:
>> Can you point me to information about that corruption bug?
> Please see the release notes for (
> http://db.apache.org/derby/releases/release- ) Detailed
> information can be found on the associated bug report:
> http://issues.apache.org/jira/browse/DERBY-3347 The symptoms in that
> bug report do not match your bug report but maybe the bug manifests
> itself in other ways. Upgrading to will remove this theory
> from consideration.

Just to clarify, upgrading to will not fix the corruption on an
existing database. Only recovery from an uncorrupted backup will do
that. But if it's data corruption, I don't think it's the same as
DERBY-3347 because

  1) DERBY-3347 only caused corruption on parts of the page, so it's
  very likely that we'd see a checksum error when reading the page from

  2) even if the checksum didn't detect the corruption, I think it's
  very unlikely that the exact same row should be affected both in the
  base table and in the index (as one experiment in DERBY-4032
  indicates) if this is DERBY-3347

Knut Anders

View raw message