In earlier releases before IQ 16.X, when several IQ clients attempted to perform write-operations against the same table, IQ server used a queuing mechanism to queue up waiting write requests while the table was locked by the write-transaction. Client applications used retry logic to send write-lock requests until the table was available for locking. However, the transaction snapshot version was created at transaction creation time, prior to obtaining the table write lock. It was possible, therefore, for a competing write-transaction to obtain the lock when the server put your transaction to sleep. In this scenario, when the server woke your transaction, the server noted that your version was older than the transaction committed by the other user, causing a future-version error and an inability to write.
SAP Sybase IQ 16.x
Connection Blocking,Transaction Blocking,BLOCKING,BLOCKING_TIMEOUT,write-lock , KBA , BC-SYB-IQ , Sybase IQ , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.