- You need clarification for which tables
- DisAllowPageLevelLocks should be set to true
- AllowPageLocks should be set to false
- Section Tables With Special Locking Setting of your Early Watch Report (=EWA) reports that the option DisAllowPageLocks or AllowPageLocks is set incorrectly for one or more tables
Recommendation: Disallow page locking for tables VBHDR, VBMOD, VBDATA, ARFCSDATA, ARFCRDATA, EDIDC, EDIDS, EDI40, TRFCQOUT, TRFCQIN, D010TAB, D010INC, REPOLOAD, REPOSRC, COVREF and TRFCQUEUE (if it exists) as described in SAP Note 1609057
Implementation: This can be done using SQL command: EXEC sp_indexoption <tablename>, "DisAllowPageLocks", "TRUE"
Background: For some tables, disallowing page locks improves the concurrency of accesses from different users to these tables, therefore avoiding deadlocks.
SAP systems based on an ABAP or Java stack and Microsoft SQL Server
Page Level Lock, Lock Escalation, SQL Server, AllowPageLocks, DisAllowPageLocks, sp_indexoption, VBHDR, VBMOD, VBDATA, ARFCSDATA, ARFCRDATA, EDIDC, EDIDS, EDI40, TRFCQOUT, TRFCQIN, D010TAB, D010INC, REPOLOAD, REPOSRC, COVREF , TRFCQUEUE , EXEC sp_indexoption , KBA , BC-DB-MSS , SQL Server in SAP NetWeaver Products , How To
About this pageThis 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.