Results 1 to 4 of 4
  1. #1
    Join Date
    Jan 2003
    Location
    Zutphen,Netherlands
    Posts
    256

    Unanswered: deadlock on DB2 7.1 with ETL-tool

    During nightly sessions I am experiencing deadlock issues that are recorded in my ETL log as follows:

    Code:
    READER_1_2_1> Mon Nov 08 20:47:34 2004
    READER_1_2_1> RR_4035 SQL Error [
    [IBM][CLI Driver][DB2/NT] SQL0911N  The current transaction has been rolled back because of a deadlock or timeout.  Reason code "2".  SQLSTATE=40001
    
     sqlstate = 40001
    
    Database driver error...
    Function Name : Execute
    SQL Stmt : SELECT BIKE_ITEM_MASTER.IPROD FROM BIKE_ITEM_MASTER
    Deadlock error encountered.
    Database driver error...
    Function Name : Execute
    SQL Stmt : SELECT BIKE_ITEM_MASTER.IPROD FROM BIKE_ITEM_MASTER
    Deadlock error encountered.].
    READER_1_2_1> Mon Nov 08 20:47:34 2004
    READER_1_2_1> BLKR_16004 ERROR: Prepare failed.
    WRITER_1_2_1> WRT_8333 Rolling back all the targets due to fatal session error.
    WRITER_1_2_1> WRT_8325 Final rollback executed for the target [SFCC_COMBINATIONS] at end of load
    WRITER_1_2_1> WRT_8035 Load complete time: Mon Nov 08 20:47:34 2004
    I have not changed the isolation level of the connection yet (CS as yet), but would changing it to UR resolve this. What would be possible drawbacks?
    Ties Blom
    Senior Application Developer BI
    Getronics Healthcare
    DB2,ORACLE,Powercenter,BusObj,Access,
    SQL, SQL server

  2. #2
    Join Date
    Nov 2004
    Posts
    374

    deadlock

    the deadlock is probably on the prepare of the statement
    so the deadlock is probably on the catalog tables
    I don't think ur will help - this will be applied to the run of the statement
    Best Regards, Guy Przytula

  3. #3
    Join Date
    Apr 2004
    Posts
    64

    reply

    You must find the resource that was not in use and who or which job was holding it. Without knowing that, just changing ur isolation level may not be helpful. Usually this information is available in log.

  4. #4
    Join Date
    Jan 2003
    Location
    Zutphen,Netherlands
    Posts
    256
    After a lot of searching I noticed that an older version of the interfacing had rescheduled itself. This caused the deadlocks, cause the 2 versions were getting in each other's way.....
    A very obvious cause, but one tends to look for exotic causes first, I guess...
    Ties Blom
    Senior Application Developer BI
    Getronics Healthcare
    DB2,ORACLE,Powercenter,BusObj,Access,
    SQL, SQL server

Posting Permissions

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