Getting error deadlock detected while waiting for resource.

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
nilesh
Participant
Posts: 17
Joined: Tue Aug 08, 2006 5:02 am
Location: Mumbai

Getting error deadlock detected while waiting for resource.

Post by nilesh »

Hi,

I am using one source table,one lookup table and finally in the end i am using the same source table to update the records.

I am getting error in the job as deadlock detected while waiting for resource.

What properties needs to be set in the stage so that it will not keep source table locked?

As in server jobs if we are useing the same table as look up and update we set its property as Read Uncommited.

Like this is there any property in parallel ?

Thanks in advance.
Nilesh
Nilesh Malekar
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You are trying to update the same table as you are selecting from ? The (self-)deadlock is in the database. Consider a better design, where you are not causing a deadlock. You might consider an array size and transaction size of one row (effectively "auto commit"). Or you could use two jobs - one to extract, one to load - with a staging area (Data Set) for the persistent storage component.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply