Locking the Table Jobs Failed

reddy · Post by **reddy** » Mon May 23, 2005 2:13 pm

Hello sirs,

My Job failed beacuse of Locking table please advise me how to set the job
means i have to set some properties,i am using ODBC Stages.

Please advise me.

Thanks in advance.

Thanks
Narasa

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Mon May 23, 2005 2:27 pm

Try resetting the job after it aborts.

You may have to reconsider your job design to avoid locking.

reddy · Post by **reddy** » Mon May 23, 2005 2:37 pm

Sainath.Srinivasan wrote:Try resetting the job after it aborts.

You may have to reconsider your job design to avoid locking.

Hi Sai,

Thanks for quick response.

While running my job some are locking the table while updating,how can i

tell with datastage hey wait some time like that.

are there any transaction handling techinques or isolation level types
helps on this.

please advise.

Thanks alot
narasa

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Tue May 24, 2005 3:55 am

You can define isolation levels for transactions in ansi standards. But before that, you need to check whether your job locks the table within itself. i.e. even if no other job is running which can lock them against yours.

If that is the case, you may have to change your design.

reddy · Post by **reddy** » Tue May 24, 2005 6:26 am

Sainath.Srinivasan wrote:You can define isolation levels for transactions in ansi standards. But before that, you need to check whether your job locks the table within itself. i.e. even if no other job is running which can lock them against yours.

If that is the case, you may have to change your design.

Sai,

because of some other mainframe jobs locking the table so please help me out.

Thanks
Narasa

reddy · Post by **reddy** » Tue May 24, 2005 6:26 am

Sainath.Srinivasan wrote:You can define isolation levels for transactions in ansi standards. But before that, you need to check whether your job locks the table within itself. i.e. even if no other job is running which can lock them against yours.

If that is the case, you may have to change your design.

Sai,

because of some other mainframe jobs locking the table so please help me out.

Thanks
Narasa

ray.wurlod · Post by **ray.wurlod** » Tue May 24, 2005 6:53 am

If something external to DataStage is locking the table there is nothing DataStage can do except wait for that lock to be released. All YOU can do is scheduled the DataStage job to run at a time (and lock the table) when the mainframe is not locking the table.

This isn't a DataStage problem. You would experience exactly the same problem with anything that was trying to update the table while it is locked.

reddy · Post by **reddy** » Tue May 24, 2005 10:22 am

ray.wurlod wrote:If something external to DataStage is locking the table there is nothing DataStage can do except wait for that lock to be released. All YOU can do is scheduled the DataStage job to run at a time (and lock the table) when the mainframe is not locking the table.

This isn't a DataStage problem. You would experience exactly the same problem with anything that was trying to update the table while it is locked.

Thanks for response.

But actual problem is datastage job is not waiting it's simply aborted..
please help me how to set job waited.
Thanks
Narasa

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Tue May 24, 2005 10:24 am

You can do that from your underlying dbms. Ask your DBA.

ranga1970 · Post by **ranga1970** » Tue May 24, 2005 4:21 pm

ask your dba to unlock the table, table lock could be for various resons like roll back when you abort a process or so on...