Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Is there a way to find a Long Transaction before it reaches
the "Long Transaction High Water Mark" and is automatically
rolled back ?
We are having problems with active transactions that span all
of the logical logs, but no way to tell which module of the
program has that transaction.
If anybody knows a way to quickly tell which users (or pid)
have Long Transactions and the time when the transaction began
I would really appreciate knowing about it.
Thanks a lot.
Your privacy choices
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.