Sequential Execution on Db2 Causing Deadlock
Posted: Thu Nov 05, 2015 9:42 pm
Hi All,
I am trying to delete records from a mainframe DB2 table based on a key. I am using sequential execution on DB2 stage so I should see only one session on Db side from ETL.
But somehow, Datastage creating two sessions with same Autogenerated DELETE statement and causing the deadlock on DB2 end.
I verified the other jobs which are executing in sequential mode which are creating only one session. The only difference is, they have user defined SQL statement and my job has AUTOGENERATED sql and causing deadlock.
Question here is, how DB2 connector stage creating multiple sessions on DB2 when I am executing the stage in SEQUENTIAL.
I am trying to delete records from a mainframe DB2 table based on a key. I am using sequential execution on DB2 stage so I should see only one session on Db side from ETL.
But somehow, Datastage creating two sessions with same Autogenerated DELETE statement and causing the deadlock on DB2 end.
I verified the other jobs which are executing in sequential mode which are creating only one session. The only difference is, they have user defined SQL statement and my job has AUTOGENERATED sql and causing deadlock.
Question here is, how DB2 connector stage creating multiple sessions on DB2 when I am executing the stage in SEQUENTIAL.