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: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.26 as permitted sender)
Message-ID: <33214577.post@talk.nabble.com>
Date: Fri, 27 Jan 2012 06:47:10 -0800 (PST)
From: Mojo Nixon <steve.b.ferguson@gmail.com>
To: derby-user@db.apache.org
Subject: Really Strange Database Corruption. Help!
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I recently received a database from a user. They said they were viewing a
record in the application, and went back to open it a bit later and the
record was gone. In the database the record is indeed gone, but when I look
at the table .dat file in a binary editor, I can see the record information! 

So I have the following questions: 
 - How could this happen? The table is corrupt, but the database continues
to function? 
 - Is there any way to get the record back? 
 - Are there any derby tools for this sort of forensic recovery of records,
like some low level tools that can read and dump what is in a single dat
file? 
 - Could it just be an issue of the record being deleted? They insist they
did not, but you know users... 

Thanks for any advice. 
-- 
View this message in context: http://old.nabble.com/Really-Strange-Database-Corruption.-Help%21-tp33214577p33214577.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.