Thanks for the reply. Tried that this morning and it seemed to work fine. Had to edit the .sql file created by the recovery tool to eliminate a record that it was attempting to insert that violated the primary key on a table. I assume because the corrupt index was not recognizing at the time that the record that was being inserted violated the unique constraint on the table.
Haven't verified, but I suspect that the corruption was the result of mix and matching a .mv.db file with a .trace.db file from an earlier/previous state on the database. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/e39b9c39-d4d1-4e1d-8dc0-3463b3d483b1%40googlegroups.com.
