Results 1 to 5 of 5
  1. #1
    Join Date
    Jan 2003
    Posts
    17

    Red face Unanswered: changes visible to other process before commit

    i am running a DB2 client with ODBC. AUTOCOMMIT mode is turned off and connection reuse is turned off. when i insert a new row it is visible to another process, when i rollback it disappears. is this due to wrong isolation level for the second process ?

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    That is what it sounds like to me.

    Andy

  3. #3
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: changes visible to other process before commit

    I think your other application might be using Isolation Level UR ...

    Cheers

    Sathyaram

  4. #4
    Join Date
    Jan 2003
    Posts
    17

    Re: changes visible to other process before commit

    Hi Sathyaram,

    the ODBC driver is configured for CR. if i change to a higher level, the second process blocks until i commit the writing connection. DB2 should know snapshots, doesn't it ?
    i'm a little bit confused.

  5. #5
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650

    Re: changes visible to other process before commit

    DB2 locks the rows if it is updated and not commited ... If you want to see such rows you will need to use Isolation Level UR ...

    When you say, 'Keeps Snapshots' I assume you are referring to the Oracle's Undo Logs ... There is not anything like that in DB2 ...

    HTH

    Cheers

    Sathayarm

    Originally posted by fidofox
    Hi Sathyaram,

    the ODBC driver is configured for CR. if i change to a higher level, the second process blocks until i commit the writing connection. DB2 should know snapshots, doesn't it ?
    i'm a little bit confused.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •