SAP Knowledge Base Article - Preview

2273421 - Can deadlocks envolving pages with indid=255 be eliminated by converting a table from APL to DOL? - SAP ASE

Symptom

  • Deadlocks on a table containing a text column.
  • Pages involved in these deadlocks have indid=0 and indid=255

Deadlock Id 237: Process (Familyid 0, Spid 48) was waiting for a 'exclusive page' lock on page 135264049 of the 'mytable' table in database 'mydb' but process (Familyid 0, Spid 301) already held a 'shared page' lock on it.
Deadlock Id 237: Process (Familyid 0, Spid 301) was waiting for a 'shared page' lock on page 135341920 of the 'mytable' table in database 'mydb' but process (Familyid 0, Spid 48) already held a 'exclusive page' lock on it. 

  • Do pages with indid=255 belong to an internal index to support the text column?
  • Will converting the table from all-page-locking (APL) to datapage (DOL) locking eliminate deadlocks on the indid=255 pages?


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 15.x

Product

SAP Adaptive Server Enterprise 15.7 ; Sybase Adaptive Server Enterprise 15.0 ; Sybase Adaptive Server Enterprise 15.5

Keywords

blocking, image, In-Row, LOB , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To

About this page

This 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.