Subject | OAT-Movement again |
---|---|
Author | guido.klapperich@t-online.de |
Post date | 2002-01-23T21:41:29Z |
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
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