hwasilk.blogg.se

The direct recovery is intended to fix the original corrupted database in place.

Two options to recover Firebird or InterBase database with FirstAID IBSurgeon FirstAID 6.0 can perform 2 kinds of recovery operations: direct recovery and data extraction. IBSurgeon FirstAID is designed to work with the database directly, on very low-level it allows bypassing erroneous places where engine crashes and either fix broken links or export all users data to the new database. If it was not possible to fix corrupted Firebird (or InterBase) database with standard means (gfix.exe and gbak.exe), it is time for IBSurgeon FirstAID. Usually, such error prevents normal work with the database, and the recovery procedure should be executed. The first part of this error is a common prefix for bugcheck (i.e., serious error), and in the parentheses, there are details of the error. When the database engine sees a broken reference to missed record or database page, it stops to work with a message like this: Internal gds software consistency check () Or, for recent Firebird versions: Internal Firebird software consistency check () Such error messages are reported by gbak tool, by gfix (it writes them into firebird.log), and by end-users applications (you can see the full list of software consistency check errors here).

Make sure to read FirstAID (Firebird and InterBase) Recovery Guide before recovery actions What is a database corruption and how FirstAID repairs it Usually, the database corruption means that some links between internal structures of Firebird (or InterBase) database are broken. If you decide to recover data you see in FirstAID, purchase the license (youll get your password in 15 minutes after completed purchase).

Open the corrupted database with FirstAID and double click on the table name, then browse through tables data pages. How to repair Firebird database: Download FirstAID - no registration required.

It uses its own layer for low-level database access without using the InterBase or Firebird engine, so it can perform real surgical operations and repair your database when all other standard mechanisms (gfix and gbak) cannot. It is expected in this instance that neither gbak nor gfix will be able to repair your database (except in the case of a Read Only database).