Subject | Re: Firebird 2.1 Database Lockout |
---|---|
Author | dr_john_mp |
Post date | 2008-05-30T08:04:22Z |
--- In firebird-support@yahoogroups.com, "dr_john_mp" <dr.john@...> wrote:
One issue relates to the MON$ tables, reading these on a busy system
can cause a lock-up. In this forum it was reported as fixed, but
elsewhere further issues were found. This is fixed in 2.1.1 RC1.
The other was that if an application exits due to an exception (not
necessarily related to Firebird) and it had transactions open at the
time, the transactions don't always close. This is similar to a
problem reported with embedded 2.1. This appears fixed in 2.1.1 RC1
>of are
> Sweep interval is set to the default 20,000. We get through 20 times
> that per day and it has neer even caused a ripple before.
>
>
> --- In firebird-support@yahoogroups.com, "Leyne, Sean" <Sean@> wrote:
> >
> >
> > > However we have had 2 ocurances of the databases 'freezing'.
> > > In short IBExpert, etc. can see and query the server, but the
> > > databases themselves are not accessible, as if they don't exist
> > > off-line (even to SYSDBA).Problem has been identified as 2 issues with Firebird 2.1
> >
> > What is the "Sweep Interval" value for your databases?
> >
> > It sounds to me like the databases are simply being sweeped.
> >
> >
> > Sean
> >
>
One issue relates to the MON$ tables, reading these on a busy system
can cause a lock-up. In this forum it was reported as fixed, but
elsewhere further issues were found. This is fixed in 2.1.1 RC1.
The other was that if an application exits due to an exception (not
necessarily related to Firebird) and it had transactions open at the
time, the transactions don't always close. This is similar to a
problem reported with embedded 2.1. This appears fixed in 2.1.1 RC1