> Thanks Helen.
>
> I guess I really must get my head fully around transactions....the
> subject seems so arcane. Is there a quick concise Guide for "Dummies"?
>
> I was under the impression that triggers and stored procedures
> automatically run in their own transactions and that they either fully
> complete or give an error and roll back. Also, if they call other
> stored procedures they all execute as a single transaction under the
> calling procedure?

only the client can start, commit, rollback a transaction.
Everything - including (readonly) selects, and backups run in the context of
a transaction.
Helen's book is a good source of information.
Alan

>
> Is the Next Transaction figure indicative of a problem?
>
> Database header page information:
> Flags 0
> Checksum 12345
> Generation 19334
> Page size 16384
> ODS version 11.0
> Oldest transaction 18857
> Oldest active 18858
> Oldest snapshot 18858
> Next transaction 19328
> Bumped transaction 1
> Sequence number 0
> Next attachment ID 0
> Implementation ID 16
> Shadow count 0
> Page buffers 0
> Next header page 0
> Database dialect 3
> Creation date Sep 18, 2008 12:10:41
> Attributes force write
>
> Variable header data:
> Sweep interval: 20000
> *END*
>
> Mitch

yep - your transactions are stuck. Your client app needs to exercise better
contorl over closing them
The exact implementation of this control depends on your connectivity layer
Alan