>> Uncommitted or committed with a soft commit (= commit retaining).
>>
>> A soft commit might be used behind the scenes when using some kind
> of
>> AutoCommit mode.
>>
>> The (SQL Server) user indicates that a Sweep is running. If you
> didn't
>> start a Sweep manually, then it got started automatically. This is
>> defined via the Sweep interval which kicks in when OAT-OIT > Sweep
>> interval. A stuck OIT can cause an automatic Sweep periodically.
> The
>> reasons for a stuck OIT can be:
>>
>> - Long-running transaction which has been left open (does not
> apply when
>> it's a read-only read committed transaction)
>> - A large data manipulation transaction got rolled back and not
> committed
>> - Soft commits without doing hard commits from time to time
>
> Thomas,
>
> Thank you for your quick answer.
>
> I have been trying to get through to the damaged database using
> Sweep because I could not get it to report on Statistics other than
> the Header stuff. But, it ran Sweep all night and never finished.
> I'll keep at it to see what table(s) are being affected.
>
> Anyhow, are there any tools that we can use to log or be aware of
> all the SQL statements that run against the server so we may narrow
> down to what transactions are hanging or not being properly
> committed?

Not with 1.x and 2.0. The monitoring tables in 2.1 will be a great help
in such a scenario.


--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com