> In the DB2 Admin Client (8.2.4), when the results of a query are displayed
> in the grid that looks like a spreadsheet (using Command Editor or double
[quoted text clipped - 11 lines]
> data with tool without attempting updates just because they place the cursor
> on a row in the grid.
To add to this, DB2 holds row locks -- so when the unsuspecting user
clicks on a row, they hold a lock on the row. Or, if a select query
returns more than the "page limit" of the output (i.e. Command Editor
defaults to fetching 100 rows at a time, I think), DB2 will hold a
row lock for the current position of the cursor.
My experience has been that these situations always happens just before
the user leaves for lunch or some other extended absence, which wreaks
havoc for other users.
Mehmet Baserdem - 01 May 2006 17:38 GMT
Mark A,
One option is to create a schema which only has read privilege on the
tables and ask users to use this schema when they are querying the DB.
FYI: TXNISOLATION = 1 (i.e. Uncommitted Read) in db2cli.ini didn't work
Regards,
Mehmet
Mehmet Baserdem - 01 May 2006 17:43 GMT
read privilege => select privilege