Subject | Re: [firebird-support] database corruption fixed with backup - restore |
---|---|
Author | Ann Harrison |
Post date | 2011-07-21T18:15:23Z |
On Thu, Jul 21, 2011 at 1:57 PM, Sergio H. Gonzalez <
shg_sistemas@...> wrote:
internal error, it will not allow other operations to continue because they
might corrupt the on-disk version of the database.
The primary error was:
PEPOSERVER (Server) Thu Jul 21 10:46:17 2011
Database: E:\SISTEMA\PEPO.FDB
internal gds software consistency check (cannot find tip page
(165), file: tra.cpp line: 2500)
The "tip" page is the Transaction Inventory Page - the place where
transaction state is maintained. There are several possible causes of
"cannot find tip page". One is that there have been more than 2**32
transactions since the database was created, but that should cause the
backup to fail as well. Another is a disk error, which should show up in
the system error log, and would also keep the backup from working. Do you
still have the file that gave the error?
[Non-text portions of this message have been removed]
shg_sistemas@...> wrote:
> Hello, I had this error with a FB2.1 database:That is a secondary error - once the server has encountered a serious
>
> *Error Internal gds software consistency check (canĀ“t continue after
> bugcheck)*
>
internal error, it will not allow other operations to continue because they
might corrupt the on-disk version of the database.
The primary error was:
PEPOSERVER (Server) Thu Jul 21 10:46:17 2011
Database: E:\SISTEMA\PEPO.FDB
internal gds software consistency check (cannot find tip page
(165), file: tra.cpp line: 2500)
The "tip" page is the Transaction Inventory Page - the place where
transaction state is maintained. There are several possible causes of
"cannot find tip page". One is that there have been more than 2**32
transactions since the database was created, but that should cause the
backup to fail as well. Another is a disk error, which should show up in
the system error log, and would also keep the backup from working. Do you
still have the file that gave the error?
>Ann
> Good luck,
[Non-text portions of this message have been removed]