完全可以修复,资料来自FIRBIRD 站
1. Define the following two variables, it makes life easier, in that you do not have to type in the user name and password every time you issue a command.
SET ISC_USER=SYSDBA
SET ISC_PASSWORD=masterkey
2. Always make sure you work on a copy of the database, not the production database. Use the operating system to make a copy of the database. You must have exclusive access to the database to do this.
copy employee.gdb database.gdb
3. Now check for database corruption. You must have exclusive access to do this, but since you're working on a copy of the original database, this is not a problem.
gfix -v -full database.gdb
4. If the previous command has indicated that there are problems with the database, we now need to mend it.
gfix -mend -full -ignore database.gdb
5. Now check to see if the corruption has been repaired.
gfix -v -full database.gdb
6. If you still see errors, you should now do a full backup and restore. In its simplest format the backup command line should be:
gbak -backup -v -ignore database.gdb database.gbk
7. However if gbak falls over because it is having trouble with garbage collection, then use the following command:
gbak -backup -v -ignore -garbage
database.gdb database.gbk
8. If there is corruption in record versions of a limbo transaction, then you may need to include the -limbo switch:
gbak -backup -v -ignore -garbage -limbo
database.gdb database.gbk
9. Now create a new database from the backup: