Determine Authorisation Errors Quickly and Efficiently
From HANA 1.0 up to HANA 2.0 SPS 03, analyses for authorisation errors in the SAP HANA database were only possible through laborious searches in the traces and logs. In order for the authorisation errors to be found in the logs, tracing had to be activated accordingly. As a consequence, performance losses that varied depending on the tracing level had to be taken into account.
Life Made Easier with SAP HANA Version 2.0 SPS 04
Now, with SAP HANA Version 2.0 SPS 04, SAP has made it much easier to analyse database authorisation errors. In the database schema SYS, there is now a procedure “SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS“, which uses the GUID to determine the database objects to be authorised. In the following, we will show you in simple steps how to identify authorisation errors in the SAP HANA database and thus save yourself time and effort.
Now, with SAP HANA Version 2.0 SPS 04, SAP has made it much easier to analyse database authorisation errors. In the database schema SYS there is now a procedure
“SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS“, which uses the GUID to determine the database objects to be authorised. In the following, we will show you in simple steps how to identify authorisation errors in the SAP HANA database and thus save yourself time and effort.
Three Simple Steps to Success
The key to success lies in the database object “SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS”.
The key to success lies in the database object “SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS “.
In order to be able to execute the procedure for error analysis of database permissions, you need the following rights:
- Privilege: EXECUTE
- Database object: SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS
- The procedure is called as follows:“CALL SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS(”, ?)”
- Input parameters: GUID (displayed in the console)
- Output parameters: ? (authorisation object)
The GUID is now passed into the procedure as an input parameter and the procedure is executed.
“CALL SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS (‘5842EF7AAEA79D408D8C70FA37156F36’, ?);”
As you can see, the user lacks the SELECT privilege for the Calculation View “_SYS_BIC.bigcube.app.test.vha/MyCalcView“.
All images on this page © 2021. BIG.Cube GmbH. All rights reserved.
In order to be able to execute the procedure for error analysis of database permissions, you need the following rights:
- Privilege: EXECUTE
- Database object: SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS
- The procedure is called as follows:“CALL SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS(”, ?)”
- Input parameters: GUID (displayed in the console)
- Output parameters: ? (authorisation object)
The GUID is now passed into the procedure as an input parameter and the procedure is executed.
“CALL SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS (‘5842EF7AAEA79D408D8C70FA37156F36’, ?);“
As you can see, the user lacks the SELECT privilege for the Calculation View “_SYS_BIC.bigcube.app.test.vha/MyCalcView“.
All images on this page © 2021. BIG.Cube GmbH. All rights reserved.
Conclusion
With simple steps it is now possible to analyse which authorisation objects are missing for a user. This reduces the effort and performance losses caused by searching the database traces or logs.
Written by Veli Hasanca
More Exciting Topics from our Newsroom
Our Summer Party 2024: Beach more. Worry less!
Our Summer Party 2024 under the motto "Beach more. Worry...
Read MoreOur project close to our hearts: The AKM Foundation in Munich
For some time now, we at BIG.Cube GmbH have been...
Read MoreWe are certified according to ISO 22301
BIG.Cube is a reliable partner and employer, even in crisis...
Read More