Make sure you are doing a commit regularly. On batch imports like my
company does, we commit every 200 records. We also have to use 2
transaction objects at times, one to progress through the dataset that is
being processed, and another to actually to the updates to the same dataset.
It's this second one that we do commits on every 200 records. This method
solved a lot of our problems. Our data wasn't really getting corrupt before
this, it's just that we operate on several GDBs at a time on the same server
and the old method would eventually bog down IB because of memory
consumption, etc. It would get so slow that we would have to kill it and
start over. Haven't had that problem with the multiple transaction and
commit method.

""mivi71dk"" <Michael.Vilhelmsen@...> wrote in message
news:afabvp+506k@......

> Hi
>
> I have gotten some reply today which has given a little different
> view on some stuff.
>
> Now, just to be sure:
>
> Oldest transaction 47728
> Oldest active 62919
> Oldest snapshot 62166
> Next transaction 75362
>
> In the above example, the automatic sweep will kick in, when the
> difference between OLDEST ACTIVE and NEXT TRANSACTION is 20000.
> Is that correct ?
>
> Or is it the difference between OLDEST TRANSACTION and OLDEST ACTIVE ?
>
>
> Regards
> Michael
>
>
>
>
>
> 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/
>
>
>