SAP Knowledge Base Article - Preview

2252721 - " being rolled back using an optimized scan" in errorlog and UPDATE/INSERT is not committed - SAP ASE


  • When running applications to do update/insert in the ASE database parallelly, sometimes the update/insert will not be committed in the database. 
  • After checking the ASE errorlog, everytime the issue happen, there is no any error messages, but only the message below will be printed out:

Transaction (page#, row#) is being rolled back using an optimized scan



SAP Adaptive Server Enterprise (ASE) 15.7 and 16.0


SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0


skewed, 3968, "Msg 2601", partial, rollback, tran, duplicate , key, insert, update , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.