At 10:33 13.06.2003 +0000, you wrote:

>normally only 1 or 2 user is connecting to the database. however, the
>diff is quite huge, which I don't know the actual reason.
>besides that how to make oldest active move ?

By committing or rolling back that transation - it is an old transaction
holding up everything from moving forward. Another likely implication of
this is that the size of the database grows quite a bit, but that isn't
dangerous as long as you have enough space and the database size doesn't
exceed 2 Gb. Do you by any chance have a program on the server that may
keep a transaction open?

>my application use odbc-api library to connect to database. before I
>run the application, the value for oldest active is 7 and next
>transaction is 13250. After i run the application, the oldest active
>is still 7 and the next transaction has increased to 19082.
>
>does it means that my application did not commit the activities to
>database ?

No, more likely it committed a lot of transactions (if no-one else was
interfering, almost 6000 transactions).

>I believed odbc-api is automatically commit the transaction to
>database. I even purposely add function, SQLEndTran to my applicaiton
>after some operation. the value of oldest active is still 7.

Yes, maybe it even commits after every record - sensible if inserted by
hand, but very time consuming and normally quite stupid if done as part of
a batch job. But I do not know how many records your application actually
inserted/changed.

HTH,
Set