Results 1 to 7 of 7
  1. #1
    Join Date
    Mar 2004
    Posts
    6

    Question Unanswered: DB2 System error

    HI, guys. It is an emergency here! Please help me out...

    We have 2 java transactions(say servlets) trying to update the same record in mytable in DB2, like:

    Transaction1: select * from mytable where A=B for Fetch only
    ....Java Processing .....
    update attr1=C where attr3=B

    Transaction2: select * from mytable where A=B for Fetch only
    ....Java Processing .....
    update attr2=D where attr3=B

    and we don't have any "lock table" statements..
    I think it never causes a dead lock, but when I try to run those 2 transactions at the same time, a severe DB2 error is thrown out..

    What is this?

  2. #2
    Join Date
    Jul 2003
    Location
    Austin, TX, USA
    Posts
    278

    Please Post

    Hi,

    Please post us the db2 version, the fixpack if any, the operating system and a piece of the db2diag.log which describes the error.

    Please also supply us with your db and dbm configuration files.

    You have written such a blank post that no one will be able to answer you. Please read the must read before posting section that will give you clarity in posting next time.

    Regards

    Nitin
    HTH

    Nitin

    Ask the experienced rather than the learned

  3. #3
    Join Date
    Mar 2004
    Posts
    6

    Re: Please Post

    thank you so much for reminding... appreciate a lot. So sorry for being nonsense. I'm very new to here..

    We are using DB2 8.1, FixPack4 on AIX5.1. 'Cos I'm not the DBM, don't have the right to get more info... but I'm in charge of this Java program..

    The JAVA ERROR message is here:

    error codeF_ESY3S100
    message Fsystem error occured while processing.
    error levelF5
    error typeFE



    the DB2 LOG message is :

    2004 03/08 18:19:12 E5 Not Logon _ESY3S083 SQL erorr occured.-91140001[IBM][CLI Driver][DB2/6000] SQL0911N a Deadlock or a Timeout occured. The transaction is rolled back. Reason code "2"B SQLSTATE=40001


    I just don't get why it causes a deadlock?


    Best regards,

    iceall.


    Originally posted by nitingm
    Hi,

    Please post us the db2 version, the fixpack if any, the operating system and a piece of the db2diag.log which describes the error.

    Please also supply us with your db and dbm configuration files.

    You have written such a blank post that no one will be able to answer you. Please read the must read before posting section that will give you clarity in posting next time.

    Regards

    Nitin

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

    Re: Please Post

    It looks timeout to me ...

    Reasoncode for timeout is 68 ...

    Cheers
    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  5. #5
    Join Date
    Mar 2004
    Posts
    6

    Smile Re: Please Post

    Thank you so much for replying, Sathyaram.

    The reasoncode doesn't match? What else could it be? how should I prevent such kind of errors from showing up?

  6. #6
    Join Date
    Jul 2003
    Location
    Austin, TX, USA
    Posts
    278

    Locktimeout

    Hi,

    To start off you can increase the lock timeout by around 10 seconds and see what happens.

    Also create an event monitor for deadlocks and if there is some data recorded then you are sure there is a deadlock and that is a bad situation to be in.

    There has been a lot of discussion on the above topics and search the forum, I am sure you will come across a lot of information especially comments from Marcus_A which are really helpful.

    HTH

    Nitin.
    HTH

    Nitin

    Ask the experienced rather than the learned

  7. #7
    Join Date
    Mar 2004
    Posts
    6

    Re: Locktimeout

    Thank you so much, Nitin!

    it helps a lot!

Posting Permissions

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