Post reply

Unexplained rollback of commited transaction

  • September 18, 2009 at 2:51 pm

    #211088

    I've got an issue with an application administrator trying to manually update a few rows in a table based on an order number. When she updates the table and then queries to see the result it updates properly. When she runs the query again, the updated columns are set to null (as they were prior to running the update transaction.)

    Here is the query (sans actual data)

    begin transaction

    update ORDERS set RELSTS = 'Released', RELBY = 'USER', RELDATE = '9/18/2009' where ORDNO = 'C09000900'

    commit

    and

    select * from ORDERS where ORDNO = 'C09000900'

    I was able to commit same transaction and verify that it stuck in the dev environment. This makes me think that it is an issue with the app that access the DB. But I am not sure how to go about proving that. Any suggestions are greatly appreciated.

    Thanks.

    Kurt Kapferer

  • September 21, 2009 at 5:17 am

    #1056145

    I'm not sure what's happening in your environment - maybe some other process "resets" your data and sets the fields to NULL? Can you be more specific?

  • September 21, 2009 at 6:39 am

    #1056174

    Thanks for your response. It appears as though this was an issue with two queries running against the row simulaneously and blocking the commit from occurring. I killed a process that had been been hanging for over a day, and then the row was updated.

    Thank you for your reply though.

  • September 21, 2009 at 7:34 am

    #1056213

    Thanks for the update. My other suggestion for checking (for others reading this) is to look for triggers. Sometimes they prevent something from committing.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply