Deadlock situation

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
reddy
Premium Member
Premium Member
Posts: 168
Joined: Tue Dec 07, 2004 12:54 pm

Deadlock situation

Post by reddy »

Hello Sirs,


Can i avoid Deadlock situation with Transaction Isolation levels.

Please help me on different Isolation levels when and where to use.

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

Post by ray.wurlod »

Not really. Deadlocks are avoided by disciplined programming practices.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Deadlock requires stremlining your data access. You can control your job but cannot control other areas in the Org that will lock the db.

Isolation levels are ansi standard mechanism to handle data access.
reddy
Premium Member
Premium Member
Posts: 168
Joined: Tue Dec 07, 2004 12:54 pm

Post by reddy »

Hello Sirs,

Suppose somebody else updating table with table lock or record lock
then Datastage job waits for some time or aborts.
one morething is if it is record lock what i observed is datastage job
rejecting locked rejects.

Please explain me still i am confusing state

Thanks a lot
Narasa
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Those configurations are set by your DBA. Ask your DBA for the answers.
Post Reply