Hi,
I am getting the below error while reading the data and writing into same table in db2 stage at db2 database.
IBM][CLI Driver][DB2/AIX64] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001
SQLFetch: Error retrieving results from server.
How can overcome this one suggest on this.
rolled back because of a deadlock or timeout
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 39
- Joined: Sat Jul 05, 2008 3:25 am
- Location: chennai
rolled back because of a deadlock or timeout
MALLI MURALI
-
- Participant
- Posts: 39
- Joined: Sat Jul 05, 2008 3:25 am
- Location: chennai
i talked DBA Guys they confirm on that no lock on those tables.
is there any way to change the my SQL code.
i am using the following SQL then updating into the MCY.PAPERWORK_HEADER using the db2 stage.
SELECT col1,col2,col3,table1.col4,tabl1.PWH_ID FROM schema.tabl2,schema.table2 WHERE INT(ORIGINAL_PMT_ID) = SUPPLIER_PMT_NUM AND PMT_SYSTEM = 'xxxx'
AND STATUS = 'EPD' AND BENE_APPROVED = 'Y' AND HOLD = 'N'
is there any way to change the my SQL code.
i am using the following SQL then updating into the MCY.PAPERWORK_HEADER using the db2 stage.
SELECT col1,col2,col3,table1.col4,tabl1.PWH_ID FROM schema.tabl2,schema.table2 WHERE INT(ORIGINAL_PMT_ID) = SUPPLIER_PMT_NUM AND PMT_SYSTEM = 'xxxx'
AND STATUS = 'EPD' AND BENE_APPROVED = 'Y' AND HOLD = 'N'
MALLI MURALI