Hi Aage,

The original header page statistics are, unfortunately, unavailable,
since we have done a backup and restore since (replacing the existing
database). :-(

Further information: the database server is dedicated to a single
database. Also, the database operation that coincided with the crash
was the execution of a stored procedure (using "execute procedure"
syntax) which contained a single insert statement followed by
a "SUSPEND" statement. There are no recursive procedures and no
UDF's or custom collation drivers are used.

I hope that helps?

Thanks,
Riaan

--- In ib-support@y..., Aage Johansen <aagjohan@o...> wrote:
> The sudden increase in memory may indicate a 'stuck' transaction.
> Take a look at the header page, and report back with the numbers for
> Oldest transaction
> Oldest active
> Oldest snapshot
> Next transaction
>
>
> Regards,
> Aage J.