Re: Datadirect JDBC driver on DB2: Locks not released

From: DB2 (db2team_at_hotmail.com)
Date: 03/22/04 

Date: 22 Mar 2004 12:47:12 -0800

Matthew,

Not sure if this helps, StarQuest has some DB2 connectivity solutions
(including a JDBC driver for DB2) and a specific DB2 to SQL Server
replication product.

Bob

mhampton@webmail.co.za (Matthew) wrote in message news:<83165bf0.0403220652.2d34aa8e@posting.google.com>...
> 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

Relevant Pages

  • Datadirect JDBC driver on DB2: Locks not released
    ... with DataDirect's level 3 JDBC driver for DB2. ... If autocommit is turned off and the connection is commited after the ... committing) has quite wide impact on the system and is going to cost ...
    (comp.lang.java.databases)
  • Re: BUG Found : DB2 OleDB Connections not closing with Framework v1.1
    ... > with a OleDBConnection does not close the connection to DB2. ... > Any solution to this problem would be appreciated as SP1 fixes some other ... > This is working at another client who is using an UDB Gateway to their DB2 ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (microsoft.public.data.oledb)
  • RE: SQL Server 2000 Linked Server --> IBM DB2
    ... > I am trying to create a linked server connection in SQL Server 2000 to ... Creating a Linked Server to DB2 using Microsoft OLE DB Provider for DB2 ...
    (microsoft.public.sqlserver.server)
  • 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)