I don't know....

What development environment are you using / components.

Three possible solutions:
1) IB / FB has a lazy reporting structure, insofar it only records for
reporting purposes the OAT at the point of a start transaction.
2) The component set you are using terminates without rolling back /
commiting.
3) The tool used to report the OAT started TX 2865, 2867, outside your
application (you can't observe without changing the behaviour....).

I could believe any or all of them. They all have an air of plausibility
about them.

JAC.

<guido.klapperich@...> wrote in message
news:3C4F2E09.50F98082@......

> I have still some problems to understand the OAT-movement of my DB. I
> have done some tests. Initialstate of the statistics was:
> OAT=2865
> Next=2866
>
> Now I start my app, open some queries and close the app. Result:
> OAT=2867
> Next=2875
>
> Now no user is connected to the DB, so there is no possibility to commit
> the OAT anymore (except sweep). Is this right ? I don't see any chance
> to access the OAT and commit it.
>
> Now I start my app again, open some queries and close the app. Result:
> OAT=2876
> Next=2884
>
> Now to my question. How is it possible, that the OAT has moved. At the
> second run, the first transaction, that my app has opened is 2875. But
> who (and how) has commited the OAT=2867 ?
> Can anybody explain this to me ?
>
>
> Guido
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>