Does SQLCODE -913 and SQLCODE -911 behave differently for batch and online?
Posted: Tue Jan 05, 2016 3:06 pm
Hi,
Does SQLCODE -913 and SQLCODE -911 behave differently for batch and online? I have experience mostly in batch though I have got to work with some online system recently. There we get SQLCODE -913 for a contentions and that forces some transactions to issue commit. Why can't we get SQLCODE -911's instead?
SQLCODE -913 is Deadlock with no rollback while SQLCODE -911 is also Deadlock but with rollback. And I want transactions to rollback. Can someone advise on this, please.
Does SQLCODE -913 and SQLCODE -911 behave differently for batch and online? I have experience mostly in batch though I have got to work with some online system recently. There we get SQLCODE -913 for a contentions and that forces some transactions to issue commit. Why can't we get SQLCODE -911's instead?
SQLCODE -913 is Deadlock with no rollback while SQLCODE -911 is also Deadlock but with rollback. And I want transactions to rollback. Can someone advise on this, please.