Fórum Erro no Banco #48891

Repairing a corrupt database

Let’s assume there are some errors in our database. Firstly, we have to check the existence of these errors; secondly, we have to try to correct these errors. We recommend the following procedure:

You should stop the InterBase server if it’s still working and make a copy of the file or the database files. All the restore activities should only be performed with a database copy, because it may lead to an unsatisfactory result, and you’ll have to restart the restore procedure (from a starting point). After creating a copy we’ll perform the complete database validation (checking fragments of records).

We should execute the following command for this (or use the IBExpert Services menu item Database Validation):

gfix –v – full corruptbase.gdb –user SYSDBA - password

In this case corruptbase.gdb – is a copy of the damaged database. This command will check the database for any structural corruption and produce a list of unsolved problems. If such errors are detected, we’ll have to delete the damaged data and get ready for a backup/restore using the following command (or using the IBExpert Services Menu item Backup Database):

gfix –mend –user SYSDBA –password your_masterkey corruptbase.gdb

After committing this command you should check if there are any errors left in the database. Run GFIX using the options –v –full, and when the process is over, perform a database backup:

gbak –b –v -ig –user SYSDBA –password corruptbase.gdb corruptbase.gbk

This command performs a database backup (option - b) and we’ll get detailed information about the backup process execution (option –v). Errors with regard to checksums will be ignored (option - ig).

Please refer to GBAK and Backup Database for further information.

If some errors are found during the backup, you should start it in another configuration:

gbak –b –v –ig -g –user SYSDBA –password
corruptbase.gdb corruptbase.gbk

Where option – g will switch off Garbage Collection during the backup. This often helps to solve backup problems.

Also it may be possible to make a backup of a database if it is set in the read-only mode beforehand. This mode prevents writing any modifications to the database and sometimes helps to complete the backup of a damaged database. For setting a database to read-only mode, you should use the the following command (or the IBExpert Services menu item Database Properties) :

gfix –m read _only –user SYSDBA –password masterkey
Disk:\Path\file.gdb

Following this, you should try to perform the database backup again using the parameters given above (or the IBExpert Service menu item Backup Database).

If the backup was completed successfully, you should restore the database from the backup copy, using the the following command (or the IBExpert Services menu item Restore Database):

gbak –c –user SYSDBA –password masterkey Disk:\Path\backup.gbk
Disk:\Path\newbase,gdb

When you are restoring the database, you may come across some problems, especially when creating the indexes.

In this case the –inactive and -one_at_a_time options should be added to the restore command. These options deactivate indexes when creating from the database backup and commit data confirmation for each table. Alternatively use the IBExpert Services menu item Restore Database.

Colega, acho que você não entendeu:



Já tentei o gfix com todas as opções possíveis...

gbak –b –v -ig –user SYSDBA –password corruptbase.gdb corruptbase.gbk