At 08:38 PM 28/02/2005 +0900, you wrote:

>hi,
>
>is there any other tools that can restore the database file aside from gbak?

For backing up a damaged database file, for the purpose of analysis and
repair, you could look at dbak (http://www.telesiscomputing.com.au). But
there is no freely-circulated tool that can repair a bad gbak
file. Commercial database recovery services like those offered by
ibphoenix.com and ibsurgeon.com may be able to assist.

>a more sophisticated tool that can fix that particular problem?

Which "particular problem"? Do you have a database file that that you can
log into? If so, you can use your schema script to redefine the lost
procedures and triggers (and constraints and indexes?). You DO have a
schema script, right?

>also, can you point me to any documentation that discusses the byte-per-byte
>structure of the backup file so i can perform byte-level modification?

There is no such document in circulation, that I know of, other than the
source code (the "burp" module).

In future, NEVER use gbak -replace_database. Always restore a backup with
gbak -create, using a different name for the database file. Log into this
new database after restoring, to ensure that it is a good database. If
this restore should fail, you will know what you have to do to the existing
database to repair it.

./hb