Isolation Level on DB2 UDB 9.1.1

RG wrote:


From SQL, you can query the CURRENT ISOLATION special register. For
example:

$ db2 VALUES CURRENT ISOLATION

1
--


1 record(s) selected.

However, if CURRENT ISOLATION hasn't been explicitly set, this will
simply return a blank string, as shown above (indicating that the
default isolation level for the package should be used). You can also
set the current isolation level in a similar fashion:

$ db2 SET CURRENT ISOLATION UR
DB20000I The SQL command completed successfully.

$ db2 VALUES CURRENT ISOLATION

1
--
UR

1 record(s) selected.

Or specify the isolation level for a query explicitly by appending
something like "WITH UR" to the SQL. See the following link for more on
the CURRENT ISOLATION register:

http://publib.boulder.ibm.com/infoc...com.ibm.db2.udb
..admin.doc/doc/r0010945.htm


Cheers,

Dave.

On Jan 13, 12:12 pm, "RG" <nob...@nowhere.comwrote:

I have a hunch that there's more to this question. I'm just guessing,
but I bet you want to find the current isolation level for active SQL
statements.

The only way I've found to get this is using the db2pd command, and it
only works for dynamic SQL.

db2pd -db <dbname-dynamic will get you there. It's somewhat of a
pain as you have to correlate different sections of the output using
StmtUID. The column you may be after is the one labeled 'Iso'.

Join Bytes! wrote:


Correct - because static SQL uses the isolation level that was specified
when the package was (re)bound.

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany