At 08:10 AM 24/03/2006, you wrote:

>My apologies, it should say that the "next transaction" increases by 1
>and the OAT will never move afterwards. To summarize, after a backup
>the next transaction goes up by 1

Of course it does. Backup runs in a transaction.

>and the oldest active transaction freezes.

The oldest transaction *stays* frozen?

This could be from one of two causes:

1. You have set NoGarbageCollect in your backup options.
2. NoGarbageCollect was off, but GC had nothing to work on during
gbak, i.e. there is already a stuck transaction.

Consider also the possibility that you're looking at the stats before
the backup is finished. If gbak is able to collect any garbage, it
won't show up until gbak's transaction commits.

./heLen