Quickly Resolve SAP HANA Authorization Errors and Issues

  • by Kehinde Eseyin, Security Architect, Turnkey Consulting Ltd.
  • June 14, 2017
See how to activate tracing to resolve authorization errors in SAP HANA. You then can troubleshoot authorization errors related to repository role activation, SQL privileges, and analytical privileges.
Learning Objectives

Reading this article you will learn:

  • The different types of authorizations in SAP HANA
  • How to work with traces in SAP HANA
  • How to troubleshoot and resolve SAP HANA authorization issues
Key Concept

All access to data and execution of actions in the SAP HANA database requires authorization, which can be assigned in the form of roles or privileges. To ensure that a user has the relevant authorizations when he or she performs an action such as accessing objects, users are subject to authorization checks. If you do not know or have the required authorizations and encounter authorization errors, you can use the system trace or the authorization error analysis to determine the appropriate authorization.

The following typical but fictitious business scenarios describe how to troubleshoot and resolve SAP HANA authorization issues. I cover these topics:

  • The SAP HANA authorization concept
  • The tracing functionality in SAP HANA
  • How to activate tracing
  • How to deactivate a trace
  • Troubleshooting and resolving role activation errors
  • Resolving missing SQL privileges and analytical privileges errors

 I explain the differences in the details of the trace files in:

  • SAP HANA prior to and up to Support Package 11—specifically, the screenprints used in this article are from Support Package 09
  • SAP HANA starting from Support Package 12—specifically, the screenprints used in this article are from Support Package 12

This article addresses the following commonplace SAP HANA authorization errors:

  • Insufficient privilege: not authorized at ptime/query/checker/query_check.cc:3302
  • Cannot get the data provider outlin.: SAP DBTech JDBC: [258]: insufficient privilege
  • Error executing the query. SAP DBTech JDBC: [258]: insufficient privilege: Not authorized

Kehinde Eseyin

Kehinde Eseyin is a security architect at Turnkey Consulting. He holds a bachelor’s degree in computer science. He has about 12 years of IT security, governance framework, IS risk, and compliance experience gained by working in numerous global organizations. Over the years, he has demonstrated competencies in security design, information assurance, cyber security, data privacy, threat and vulnerability management, penetration testing, business architecture, project management, IT audit, IS controls framework, and identity and access management.
 

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.