Database corrupted after power loss!
giri <[email protected]>
| Newsgroups | gmane.comp.java.hsqldb.user |
|---|---|
| Message-ID | <[email protected]> |
Hello, after power loss, our HSQLDB 2.3.1 database does not start. We created this DB about month ago, using HSQLDB 2.3.0. We then imported ~700 MB data from another DB, so the new DB was "fresh". Then we upgraded to HSQLDB 2.3.1 without performing Shutdown Compact command (at that time, we were not aware that it is needed). Now, beside of .lobs .script and .properties files, there is 800MB .data file (all tables are cached) 14 MB .backup file 100kB .log file. When I try to start DB, it gives me error which I attach into error1.txt attachment. When I delete .log and .backup file (I suppose they contain "changes" made since last shutdown. Those changes, I am willing to loose), the DB starts... However when I browse thru tables with some SQL client, it gives me error attached in error2.txt attachment. So I am not able to read my data.. When I perform Shutdown compact (with deleted .log and .backup), it fails on exception in attachment error3.txt. Could you please help me to get access to my data back? We kind of really need them back as soon as possible, they are essential for us. Is it for example possible to edit DB files by hand and fix / remove faulty segments? Thank you very much, Jan error1.txt <http://hsqldb.10974.n7.nabble.com/file/n3979/error1.txt> error2.txt <http://hsqldb.10974.n7.nabble.com/file/n3979/error2.txt> error3.txt <http://hsqldb.10974.n7.nabble.com/file/n3979/error3.txt> -- View this message in context: http://hsqldb.10974.n7.nabble.com/Database-corrupted-after-power-loss-tp3979.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