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: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=sbcglobal.net;
  h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
  b=htjQGjFi5wtfhZJK1tMy6Sl9ilrRDtpsUZsMSDh0QefYPnrhHLHakoRCKGNdwW2XzKYJ79oI+Of8VMGHR69gQF53ppsvAngHnNeTkUXaBhSDn5beKLRtJz+v71jGkGowEweybujVXZLWoGUOHJ1JOVicHf2LpYOFvHjB+BbY3TY=
  ;
Message-ID: <4F22D6E3.8010203@sbcglobal.net>
Date: Fri, 27 Jan 2012 08:54:59 -0800
From: Katherine Marsden <kmarsdenderby@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: derby-user@db.apache.org
Subject: Re: corrupt database
References: <33198924.post@talk.nabble.com> <33214528.post@talk.nabble.com>
 <x6y5st5bx7.fsf@oracle.com>
In-Reply-To: <x6y5st5bx7.fsf@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 1/27/2012 8:48 AM, Dag H. Wanvik wrote:
> Mojo Nixon<steve.b.ferguson@gmail.com>  writes:
>
>> I am no derby expert, but I have done the following before, with good
>> results. Make a backup copy of all the database files, in case it doesn't
>> work. Then delete the files in the log directory and try to boot the
>> database. You might lose some transactions, but should be able to open the
>> database again.
> If you do this there is no guarantee the database is in a transactionally
> consistent state: some transactions may be half persisted, so do this at
> your own risk, and vet the data after.
>
The only times I have ever done this I have only done so to salvage data 
and create a new database using dblook and import/export or something 
like Ddlutils. Then throw the one intentionally corrupted by deleting 
the log files away.   Don't use that one in production as you could end 
up with things like partial large objects etc that are not caught on a 
consistency check, but show up during usage.