Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: neutral (nike.apache.org: 32.97.110.154 is neither permitted nor
 denied by domain of Stan.Bradbury@gmail.com)
Message-ID: <47FB845E.6040303@gmail.com>
Date: Tue, 08 Apr 2008 07:42:38 -0700
From: Stanley Bradbury <Stan.Bradbury@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: ERROR XSDG2: Invalid checksum on Page Page(0,Container(0, 1313))
References: <47F02F3E.40807@nuix.com> <47F065D0.6010404@sun.com>
 <47F074A0.40309@nuix.com> <47F16AD7.6090101@gmail.com>
 <47F1AEF3.8080603@nuix.com> <47F27834.4020701@gmail.com>
 <47F31746.6060800@nuix.com> <47F46DB8.2060304@nuix.com>
In-Reply-To: <47F46DB8.2060304@nuix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

David Sitsky wrote:
>> Ok - we are restructuring the application, so that now, we can get 
>> away with a primary key field of just an INTEGER, rather than the two 
>> BIGINT columns.  Also, because of the restructure, we don't need to 
>> check for the existence of a duplicate record before insertion, so we 
>> can now create the primary key once all of the data has been loaded.
>
> As expected, our loading doesn't exhibit the problem now with the 
> above change.
>
> Incidentally, we had a customer being hit with this problem yesterday, 
> on their own hardware, which was an AMD64 dual core 4200 with 4 GB of 
> ram running 32 bit XP pro.
>
> I will create the JIRA entry in the next day or two - the fact this 
> has now been seen on an external site on completely different hardware 
> / OS shows we are probably dealing with a software issue.
>
Thanks for thorough job in reporting this problem.