Results 1 to 5 of 5
  1. #1
    Join Date
    Jun 2007
    Posts
    3

    Unanswered: UnCommit Read in DB2 UDB Setting

    Is there any default settings in UDB(Version 8) "Control Center" where we
    can have default setting of UnCommit Read.
    ex: select a from table with ur

  2. #2
    Join Date
    Jun 2007
    Posts
    3
    I did find the answer. It is in CLI Settings.

  3. #3
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    Note that there are many other ways to connect to DB2. CLI is just one of them. Therefore, adjusting the CLI configuration is not a global change.

    p.s: You should have a very good reason to use uncommitted read. Usually, such a change indicates a problem in your applications.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  4. #4
    Join Date
    Jun 2007
    Posts
    3
    The uncomitted reads are taking place in the datamart and not in the online database. The reason for uncomitted reads is to let the incremental process update the database when adhoc users are accessing the datamart. Is there any gloabal settings that you are aware of ..Thanks for your reply .

  5. #5
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Quote Originally Posted by stolze
    Note that there are many other ways to connect to DB2. CLI is just one of them. Therefore, adjusting the CLI configuration is not a global change.

    p.s: You should have a very good reason to use uncommitted read. Usually, such a change indicates a problem in your applications.
    The DB2 Control Center uses the type 2 driver (I believe that is uses the CLI configuration?).

    Unfortuneatley, the DB2 Control Center has a major flaw (introduced in recent releases). If you select data with a query and the "grid" is displayed with your result set, then if you place the cursor on one of the boxes in the grid, and then move the cursor to another box in the result set grid, then DB2 updates the row where your cursor originally was in the first grid (regardeless of whether or not the data was changed).

    And worse, it does not autocommit, and holds an X lock on the row updated.

    This is a major problem in many situations, for both development and produciton systems.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

Posting Permissions

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