Subject | Re: rdb$relations system table |
---|---|
Author | philc_pcm |
Post date | 2004-02-05T20:40:34Z |
Peter McLeod wrote:
up a damaged database. This is why you should always restore to
another file and then replace your existing database. Under the
circumstances you mention a restore without activating Indexes (-I
option for gbak) would most likely be able to recover your database.
I understand that checking would be too much at backup, especially if
you are trying live backups. I only wish that I would still be able
to restore it...
I tried it again with the -I option to another file, here is the
message I get:
gbak: ERROR: attempt to store duplicate value (visible to active
transactions) in uique index "RDB$INDEX_0"
I'm wondering if the -I option only applys to NON system tables?
Have a nice day,
Phil.
> Checking a database is resource hungry so Interbase / firebirdchecks the restore and not a backup so it is possible to have backed
up a damaged database. This is why you should always restore to
another file and then replace your existing database. Under the
circumstances you mention a restore without activating Indexes (-I
option for gbak) would most likely be able to recover your database.
> RegardsI tried to reply to you, but I'm getting an error from the mail server.
>
>
> Peter Mc Leod
>
>
>
I understand that checking would be too much at backup, especially if
you are trying live backups. I only wish that I would still be able
to restore it...
I tried it again with the -I option to another file, here is the
message I get:
gbak: ERROR: attempt to store duplicate value (visible to active
transactions) in uique index "RDB$INDEX_0"
I'm wondering if the -I option only applys to NON system tables?
Have a nice day,
Phil.