Subject | Re: [firebird-support] Can't find shared latch error |
---|---|
Author | Ann W. Harrison |
Post date | 2006-01-20T15:44:54Z |
remk_1 wrote:
to me, only 20 transactions are allowed to share a single page in cache.
The transaction in question tried to release a buffer, but the first
20 locks (called latches when applied to cache buffers) don't
include a lock for this particular transaction. The code is the same
(as far as I can see) in FB 1.5.x and FB 2.0, but completely changed
in Vulcan.
This is not a user level error, it's a bug, and should be sent to the
devel list. Please tell them I sent you, and please think of anything
that's different at this one client.
Regards,
Ann
> Hi,That's one of the internal "can't happen" errors. For reasons unclear
>
> one of our client sites has regular server stability problems (server
> termination and restarts). Log file shows many "fbserver terminated
> abnormally (-1)" messages, but also this strange message (repeatedly):
>
> internal gds software consistency check (can't find shared latch
> (300))
>
> Backup and restore cycle doesn't help, the same error comes again
> within several hours. Since I can't find anything about this message in
> archives, I believe it could help me identify source of problems. What
> could be cause of this error ?
>
to me, only 20 transactions are allowed to share a single page in cache.
The transaction in question tried to release a buffer, but the first
20 locks (called latches when applied to cache buffers) don't
include a lock for this particular transaction. The code is the same
(as far as I can see) in FB 1.5.x and FB 2.0, but completely changed
in Vulcan.
This is not a user level error, it's a bug, and should be sent to the
devel list. Please tell them I sent you, and please think of anything
that's different at this one client.
Regards,
Ann