Datadirect JDBC driver on DB2: Locks not released

From: Matthew (mhampton_at_webmail.co.za)
Date: 03/22/04

  • Next message: Eric Kaun: "Recommendations on SQL Server JDBC driver?" 
    Date: 22 Mar 2004 06:52:49 -0800

    I am involved in a project that is porting a large database
    application from SQL server to DB2 and have run into some difficulty
    with DataDirect's level 3 JDBC driver for DB2 (running under linux).

    I have a number of CallableStatements created at the beginning of a
    process, used multiple times during the process and then closed at the
    end (all are created on the same connection - but are used by only one
    thread - i.e. no two statements are executed simultaneously).

    One of these statements inserts values into a table and another reads
    from it. The problem is that the statement that inserts acquires a
    lock on the table that isn't released until the statement is CLOSED
    (even though Autocommit is ON). This means that the select statement
    is locked out.

    If autocommit is turned off and the connection is commited after the
    insert statement then the locks are released - isn't it true that
    setting autocommit to true should make the connection behave exactly
    as if autocommit was off, but the connection was commited after every
    statement? Is this a bug?

    Any help will be appreciated as changing our approach (i.e. manually
    committing) has quite wide impact on the system and is going to cost
    us a lot of development time.

    Thanks,

    Matthew
    Software Developer
    Mosaic Software
    Cape Town

  • Next message: Eric Kaun: "Recommendations on SQL Server JDBC driver?"

    Relevant Pages

    • Re: Datadirect JDBC driver on DB2: Locks not released
      ... StarQuest has some DB2 connectivity solutions ... and a specific DB2 to SQL Server ... > (even though Autocommit is ON). ... > If autocommit is turned off and the connection is commited after the ...
      (comp.lang.java.databases)
    • Re: Datadirect JDBC driver on DB2: Locks not released
      ... Are you getting this connection from a managed pool or are you getting ... > (even though Autocommit is ON). ... > committing) has quite wide impact on the system and is going to cost ...
      (comp.lang.java.databases)
    • RE: Check on ODBC connection to IBM DB2 table
      ... MSDASQL will only call into DB2 driver's SQLDriverConnect with the DSN name ... So I define as recordset and try to make the connection of the table. ... Set db2con = New ADODB.Connection ... Another idea is to have a separate database to keep the status of the DB2 ...
      (microsoft.public.data.odbc)
    • RE: Check on ODBC connection to IBM DB2 table
      ... DB2 table. ... So I define as recordset and try to make the connection of the table. ... Set db2con = New ADODB.Connection ... Another idea is to have a separate database to keep the status of the DB2 ...
      (microsoft.public.data.odbc)
    • RE: SQL 2005: Microsoft OLE DB Providers for DB2 not working with
      ... When I connectet remotely direct on te server and tried it out, ... (With the Microsoft OLE DB Provider for DB2 that was made available November ... open the Connection Manager for your DB2 ...
      (microsoft.public.sqlserver.dts)