To work around this, connect to database with isql tool using -nodbtriggers option and then disable those triggers. For example, a database trigger might use some table which has a broken index, etc. One of the reasons why backup or restore can fail is if some broken database triggers exist, and prevent connection to the database. If not, you can try to create an empty database with the same structure and pump the data to it (see FAQ #20). If you succeed, you have fixed the problem and have a functional database. * use GBAK -c to restore backup to a new database. * use GFIX -mend to prepare corrupt database for backup If problem is not too serious, you can try to backup the broken db and restore under a new name: * use GFIX with -v and -f to do full validation * use GFIX with -v option to validate the database file * make a copy of database file (or two copies) and work on that * disconnect users and disable incoming connections to the database (FAQ #64) How to repair a corrupt Firebird database?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |