Deadlock or Timeout

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
MURALI123
Participant
Posts: 46
Joined: Sun Jun 21, 2009 1:37 am
Location: CHENNAI

Deadlock or Timeout

Post by MURALI123 »

Hi,
i am using the same table as source and target to update the satatus codes while running the jobs which shows the following warnings:
(1)
SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001
(2)SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001

SQLTables: Error retrieving system catalog information for requested tables(s).

can anybody suggest me how to slove the problem with out changing the ds code.
Regards,
Malli
Top
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Not possible.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Top
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Deadlocks in server job it not frequent. Maybe timeout.

Can you provide more information on what is being locked / timed out and find what activity is causing the deadlock ? Also bit of your design info will be useful.

Reading and writing alone will not cause deadlock.
Top
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

What database are we talking about here? DB2? Knowing that can help determine what your options are.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Top
Post Reply

Return to “IBM<sup>®</sup> Infosphere DataStage Server Edition”