I am pursuing understanding why I have some very old UOWs holding my
logs from archiving. I am pretty sure it is an application issue, but
I am trying to nail down how DB2 is behaving.
I the database snapshot I will see the applid holding the oldest
transaction. When I snapshot that appl id I have seen timeframes of
several hours since the beginning of the UOW. When I do a snapshot
locks for that application I will see that it may be holding a few
share locks primarily on catalog tables and one or two application
tables.
I believe what is happening is that a begin unit of work record is
being written to the log file. I also believe the application is
returning control to the user without having issued any commit meaning
the application is by default a conversational program.
When does DB2 actually mark on the log that the UOW has begun?
thanks
Jack Baker
