Subject | Re: [firebird-support] Re: two machines - different resultsets for ORDER BY |
---|---|
Author | Helen Borrie |
Post date | 2006-05-22T12:27:41Z |
At 09:53 PM 22/05/2006, you wrote:
locally on different machines.
From what you said, it seems like you took a file copy of the
original database and assumed that it was "the same file". It's
not. The copy contains unfinished business that applies to the
server that was overseeing it. You appear to have corrupted an index
by file-copying an active database. This can happen because you have
garbage in the index pages that belong to transactions that are not
known to the server that you copied it to.
Run through the exercise again but this time, take a gbak of the
original database and restore it on the other machine.
Or, as others have suggested, try setting that index inactive/active
to rebuild it.
./heLen
>This is the same GDB file, and its always local to client application.That can't be true. Clients can't be looking at the same file
locally on different machines.
From what you said, it seems like you took a file copy of the
original database and assumed that it was "the same file". It's
not. The copy contains unfinished business that applies to the
server that was overseeing it. You appear to have corrupted an index
by file-copying an active database. This can happen because you have
garbage in the index pages that belong to transactions that are not
known to the server that you copied it to.
Run through the exercise again but this time, take a gbak of the
original database and restore it on the other machine.
Or, as others have suggested, try setting that index inactive/active
to rebuild it.
./heLen