by Shan » Thu, 02 May 2002 22:04:29
by Lee Dilwort » Thu, 02 May 2002 22:11:09
db2 list command options
for your session you can turn it off using then +c option
db2 +c .....
also the default for CLI / ODBC apps it to commit after each stmt.
You can alter this by editing your db2cli.ini file for the required db
ie.
[MYDB]
autocommit=0
Quote:> I opened two DB2 CLP sessions on Solaris. I did a update on session 1;
> then did a select on session 2. What surprised me is that the session
> 2 saw the changes made in session 1 even I did not commit session 1.
> This is different from Oracle. Does DB2 automatically commit in CLP?
by Bob Harbu » Thu, 02 May 2002 22:35:04
Try using db2 +c if you do not want to commit the statement.
Bob Harbus
by Knut Stolz » Fri, 03 May 2002 10:23:48
> Try using db2 +c if you do not want to commit the statement.
--
Knut Stolze
DB2 Spatial Extender
IBM Silicon Valley Lab
We are attempting to do uncommitted reads against UDB. We have made
the change in our db2cli.ini file to add in the following line
TNXISOLATION=1. However we are noticing that in some instances we
appear to be blocking other users. What is a valid test to ensure
that we are indeed connecting and doing Uncommitted Read's?
Spencer
2. utl_file problem when accessed from OWS
4. how to reset a unique identifier
5. Is it possible to do uncommitted reads with BO ?
7. Isolation level READ UNCOMMITTED
9. Read Uncommitted and image data
10. read uncommitted AS DEFAULT behaviour
11. SQL 2k not honoring READ UNCOMMITTED
12. READ UNCOMMITTED - Exclusive table locks.