The db2 get snapshot for database on dbname will give you.
The log file name of the first active log, which should contain either or
both of 1 or more transaction in flight or dirty (committed but not
externalized to the table).
The last active log file.
The application handle of the appl. holding the pldest in flight
transaction.
But not the contents of the logs, nor the number of transactions in those
states.
A snapshot at the application level will show you how many appls. there are,
which are holding what type of locks and how many locks are held. You could
also turn the statement switch on to get this at the statement lervel. This
could be a busy report!!!!!
Those holding locks would be the ones that have not rolled back or committed
and therefore have in flight stuff.
HTH, Pierre.
--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"Bernd Hohmann" <ho*****@harddiskcafe.de> a écrit dans le message de news:
4d*************@individual.net...
Hi,
is there any commandline option to see if there are uncommitted statements
and which statements aren't comitted? Or at least a hint that there are
uncommitted pages in the transaction log.
Bernd
