LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Transaction Aborted due to Deadlock

    Employee
    Posted 12-26-2013 12:20

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: RodC80

    I'm trying to upload a list to a temp table I'm creating in our data warehouse. I have a DB Store, DB Execute and 2 DB Query Nodes connected to complete the steps. The process is logging onto the data warehouse and creating the temp table fine. When I run with a small list, 300, of accounts the process completes. I'm now trying to load 360,000 records and am getting a deadlock error. Anyone know how to fix this?


  • 2.  RE: Transaction Aborted due to Deadlock

    Employee
    Posted 12-27-2013 08:08

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    Unless you NEED for all of the records to be considered one transaction, try setting your CommitThreshold to 1000.
    The database server may be struggling with holding 360k records as one single transaction. Breaking it up into chunks with the CommitThreshold may help with the problem.

    You may need to play with the value a bit to come up with the optimum results:
    CommitThreshold=0 (all records/single transaction) can cause the problem you are seeing
    CommitThreshold=1 (each record is a separate transaction) can make your updates very slow

    I have found that a value between 1000 and 10,000 seems to work well.


  • 3.  RE: Transaction Aborted due to Deadlock

    Employee
    Posted 12-27-2013 09:50

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: RodC80

    In the DB Store Node, tab "Parameters 2" I have Load Method set to Optimized, Commit Frequency was 1,000, changed to 100
    In the DB Execure Node, I set Commit Frequency to 1,000, tried 100 too.

    Still getting the deadlock issue.


  • 4.  RE: Transaction Aborted due to Deadlock

    Employee
    Posted 12-30-2013 06:20

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: RodC80

    I figured out the issue. It had to do with the way the nodes were linked and the order they were processing.