SQL error "SQL code: -911" occurred while accessing table "GRACROLEMASTER"
SQL error "SQL CODE: 12207" occurred while accessing table "GRACROLEMASTER"
FYI - The SQL Code might change depending on different database vendors.
An exception has occurred which is explained in more detail below. The | | exception is assigned to class 'CX_SY_OPEN_SQL_DB' and was not caught in | | procedure | | "LOAD_ROLE_FAZZY" "(METHOD)", nor was it propagated by a RAISING clause. | | Since the caller of the procedure could not have anticipated this | | exception, the current program was terminated. | | The reason for the exception is: | | Database error text: SQL message: SQL0911N The current transaction has been | | rolled back because of a deadlock or timeout. Reason code "2". | | SQLSTATE=40001 row=1 | | Return value of the database layer: "SQL dbsl rc: 99"
Long running repository object sync
Performance issues in repository object sync
GRC Access Control 10.1
- Repository Object Sync
KBA , gracrolemaster , troubleshooting , performance issue , load_role_fazzy , long running repository object sync , GRC-SAC-ARA , Access Risk Analysis , GRC-SAC-ARQ , Access Request , Problem
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.