In this blog post, you’ll learn more about the Sybase Error Statement terminated to prevent potential deadlock. Try again. %1 and the reason for receiving this error
Sybase SQL Error Message
Statement terminated to prevent potential deadlock. Try again. %1
Reason for this Error
Statement terminated to prevent potential deadlock. Try again. Bug 154803 [CR 809642] has made changes to allow users to set a timeout threshold on how much certain critical buffer manager functions need to wait on a mutex before giving up (cf., PARAMID_CORE_LOCK_TIMEOUT_DURATION; user visible name=’CORE_Options150′). The buffer manager relies on this threshold in combination with a timedlock() mechanism to prevent instances of potential deadlocks. In that case, statements may be terminated with the message above appearing in the IQ Message File. Note that this fix is not comprehensive, that is, it is impossible to address all possible deadlock scenarios with this approach.
