Subject | Re: [firebird-support] database corruption without system restart |
---|---|
Author | Ann W. Harrison |
Post date | 2005-10-26T16:15:09Z |
Alexey Kovyazin wrote:
disk problem and the error happened to fall on an index
page. When that happens, the odds are good that a backup
without garbage collection will get the data out of the
database, but the root cause is unlikely to be Firebird
and should be identified and fixed. In short, get that
database onto a different server.
a data page and you won't be able to backup the table with
that page - a data pump may help.
A single table over 35Gb can cause problems - but the
problem won't show up on early pages like 4051 or even
1848263 which is only 30Gb with 16K pages (if I can
still multiply) for the whole database.
Regards,
Ann
>More than likely, the file was corrupted by a memory or
> >wrong page type
> >page 1849263 is of wrong type (expected 7, found 0)
>
> Index was corrupted.
disk problem and the error happened to fall on an index
page. When that happens, the odds are good that a backup
without garbage collection will get the data out of the
database, but the root cause is unlikely to be Firebird
and should be identified and fixed. In short, get that
database onto a different server.
>As above, except that this time the bad write went onto
> >wrong page type
> >page 4051 is of wrong type (expected 5, found 0)
>
> Table (data) was corrupted.
>
a data page and you won't be able to backup the table with
that page - a data pump may help.
A single table over 35Gb can cause problems - but the
problem won't show up on early pages like 4051 or even
1848263 which is only 30Gb with 16K pages (if I can
still multiply) for the whole database.
Regards,
Ann