Why it returns -60 sqlcode
652398Feb 9 2011 — edited Feb 9 201109:01
Session A:
delete table using where clause one by one without commit.
09:02
Session B:
delete table using where clause the same as session A one by one.
Normally, every delete statement will return 1403 sqlcode for not commiting by session A.
09:10
Session A:
Commit. It will take several seconds for many records at a time.
09:10
Session B:
It return -60 sqlcode (deadlock detected while waiting for resource).
My question is why Session B in 09:10 returns -60 sqlcode? The reason is that Session A and Session need the same memory or resource? In my mind, Session B should return time out sql error not -60. Could someone explain that? Thanks a lot.