DB2 EE Stage

[ramudwhelp]

HI ,


We have two ETL server say X and Y , from both the server we are connecting to same database say D1. Server X is uses db2connect ver1 and Server Y uses db2connect ver1.5 to connect the D1 database by using the DB2 EE Stage.Issue is if we trigger the jobs from both the servers then only jobs from one server is running fine other once getting abort saying deadlock or time out and db2 bind fails. If we run the jobs individually then both the server's jobs are running fine.

Any clues on this...

Thanks in Advance.

[chulett]

Talk to your DBA about the "deadlock or time out" errors so you understand what they mean. Run the jobs individually in the meantime.

[ramudwhelp]

Thanks chulett
Run the X server jobs when none of the Y server jobs are running vice versa.

When we got the issue we contacted the DBA as per them There were no locks on the table.

[DSguru2B]

Ask them to monitor while you run your jobs. Anything after the fact will always show clear on their part.

[chulett]

No, not literally "none", it should just be an issue of not running jobs that target the same table until you understand the issue. What kind of loads are you doing, exactly?

Can you please post the actual, complete and unedited errors you are seeing? That way people who know may be able to get a better idea of the scope of the issue.

[ramudwhelp]

This is the error message :

DB2udb_PS_TGT_L_BUS_UNIT: Error Idx = 1;
DB2 Driver Embedded SQL message: SQL0911N The current transaction has been rolled back because of a deadlock or
timeout. Reason code "68". SQLSTATE=40001
;
sqlcode = -911;
sqlstate = 40001
A timestamp conflict occured
Attempting to re-bind to the database /apps/Ascential/DataStage/dseax203/Ascential/DataStage/PXEngine/bin/db2esql.bnd ....failed

[DSguru2B]

There may be other reasons. Check with your dba on the number of requests going in from your user id.
Read the explanation of the sql code here, specifically the last para where it talks about queing threshold.