Re: Database corrupted after power loss!

Thank you for your reply..

Currently, we suspect faulty RAM module to be a source of our problems.

We managed to recover a week old backup, which was not corrupted..

We also managed to recover .log files, which were filled by data during the
last week. Files .backup from during last week are damaged and we can not
use those.

Now the question is - is it reasonable to expect, that if we take week old,
correct DB and apply all lines from all .log files created during this week
(together over 20MB), we end up with current database?

Do the .log files contain simply all SQL commands (changing some data)
performed since start of DB?
Our app does not use CHECKPOINT, Shutdown Compact nor any similar HSQLDB
specific functions, therefore if .log contains all changes since start, it
should be possible to re-apply it on DB backed up just before that start,
correct?

One problem is that .log files do not use "update" SQL functions, but rather
"delete"&"insert".. 
Currently we work on code that would transform those "delete"&"insert" into
"update" queries, so we would not get into troubles with foreign keys etc.

What do you think about that?

Thank you very much for your help,
Jan



--
View this message in context: http://hsqldb.10974.n7.nabble.com/Database-corrupted-after-power-loss-tp3979p3981.html
Sent from the HSQLDB - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk