| Subject | Internal GDS errors that cause corruption and unrecoverable databases |
|---|---|
| Author | Eduardo A |
| Post date | 2013-03-04T21:06:30Z |
Need a lot of help. Urgently. Using FB version 1.5.6.
I am having a few databases reporting Internal GDS errors that allow the database to be backed up but do not allow it to be restored. Most of them have reported I/O errors 10054 at one time or another. Most of these are databases of 40 GB or less.
What I need to know is how can I tell (by looking at the Firebird log or doing some other operation) that the database is in bad shape and may allow a back up and not restore, or may soon result in an internal gds error that require some time with GFIX to get it back to service.
I need to be able to create, or buy, an application that either reads the FB log or performs some actions that send me notification that a database is in the process of being damaged before they are beyond repair.
Thanks for you quick answer.
-Eduardo
I am having a few databases reporting Internal GDS errors that allow the database to be backed up but do not allow it to be restored. Most of them have reported I/O errors 10054 at one time or another. Most of these are databases of 40 GB or less.
What I need to know is how can I tell (by looking at the Firebird log or doing some other operation) that the database is in bad shape and may allow a back up and not restore, or may soon result in an internal gds error that require some time with GFIX to get it back to service.
I need to be able to create, or buy, an application that either reads the FB log or performs some actions that send me notification that a database is in the process of being damaged before they are beyond repair.
Thanks for you quick answer.
-Eduardo