Ann,

Ok, I will try, but the issue is that this application is now
running in a production mode and I am trying to prevent this from
happening again. I noticed that I also do not have automated
sweeping activated, is this something I should do?

Regards,

Bernie

--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@i...> wrote:

> berniebialt wrote:
> > Ann:
> >
> > Thanks for respond to me. I ran gstat and here are some of the
> > details that I see:
> >
> > Oldest Transaction 434143
> > Oldest Active 446334
> > Oldest Snapshot 446334
> > Next Transaction 446335
> >
> > Is the issue the difference between Oldest Transaction and

Next

> > Transaction?
>
> No, the problem would be between the oldest active and the next.

In

> this case, there's only a single transaction running. To analyze

the

> problem, you're going to have to run gstat -h when the performance

is bad.

>
> > I noticed it is a differnce of over 12000. If this is
> > the problem, what would cause this to occur? and how could I

keep

> > this from happening going forward.
> >
>
> The oldest transaction - also called the oldest interesting

transaction

> - is the oldest transaction in any state other than committed.

Sweep

> moves that number along. 12000 is not very bad.
>
> Regards,
>
>
> Ann