On 18/10/2010 12:41, Helen Borrie wrote:

>
> Actually, it is so good it is unbelievable. ;-) I assume you did this
> whilst you were the only user, having just performed a sweep or gbak.
> That is a pleasant way to start a day.
>

:) I am glad that it was not disappointing. Yes, I was the only user
and I had started and closed my application just to see if it was
cleaning up after or not. I also have in the mean time tried to reset
the computer right when in the middle of a data-entry and see what
happened on reboot, still just a diff. of 1.

> If you are looking at these numbers whilst multiple users are busy,
> then it is nothing.
>

No actually, single user (me), opening, not doing much and closing the
application and then checking gstat -h again. If this is worrisome
then, not sure what I can do much in this regards (I will ping the
respective lists) as I probably have 2 degrees of separation due to the
programming language, remote views and ODBC.

> Yes, there is. I just can't remember what it is right now...something
> in the order of two billion, though.
>

Oh! As this was on the development machine. Thanks, I will take the
temperature on the clients end.

> ..erm, you should aim to do a backup and restore considerably sooner
> than when the transaction counter is approaching the limit.
> ... Preempt via good housekeeping practice. If your sites are
> completely unsupervised then you need to show a responsible user how
> to perform and store backups and how to perform a safe restore - and
> provide very good documentation of it all.
>

Can I read these numbers using ODBC / SQL? Else I can always else
capture the gstat output and parse it. (FYI With such numbers which I
read at app start and I can try to stop them or point them to do the
needful at the earliest.)

> COMMIT RETAINING is unrelated to Force write. C-r does commit the work
> but it holds all the resources open for use by the next transaction.
> This causes garbage to be held back from clearance indefinitely. If
> you are performing a full controlled shut-down of the database every
> day then C-r won't impact things so much.
>

Oh, these are small sites and server too is shutdown at the end of the
day. Okay, I found out that I can use gfix to set Forced Writes, but
where can I see it's current setting?

Thanks and regards
Bhavbhuti