Solution : https://service.sap.com/sap/support/notes/965530 (SAP Service marketplace login required)
Summary :
SQL Server Error 601 in SAP environments can occur due to physical corruption or data movement. With physical corruption, repeated execution of the same SQL query always results in failure, indicated by persistent 601 errors in logs. Conversely, data movement errors, typically intermittent and noted with "NOLOCK due to data recommendation," suggest issues at the transaction isolation level but are not linked to on-disk corruption. Resolution approaches include running DBCC CHECKDB to check for physical corruption and updating SQL Server to the latest service pack to mitigate data movement errors. Specific query adjustments or SAP OSS notes may be needed for unresolved cases.
Key words :
select berid lgort charg vbtyp mbdat sum, select lgort charg vbtyp vbtyp sum, sql version specific detailed solutionsfor sql server 7, berid lgort charg vbtyp mbdat, terms corruption nolock data movement 9134 reason, lgort charg vbtyp mbdat, open sql server enterprise manager, solution note 356228 describes mass updates, sql version specific detailed solutions, short dump lists abap statements
Related Notes :
| 608651 | SQL Server 2000 Most Recent Hotfix |
| 539917 | SQL error 601 when accessing "ARFCRSTATE" table |
| 499858 | Storage parameter maintenance with MS SQL Server |
| 356228 | qRFC occupies all work processes on the R/3 backend or the C |
| 142731 | DBCC checks of SQL server |
| 62988 | Service Packs for Microsoft SQL Server |