Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
lbreddemann
Active Contributor
Based on revision 41 of SAP HANA Studio and Database

Dear HANA database tribe,

I know the title of this is cheesy but the topic is actually so not exciting that I had to come up with something to draw your short attention span over

I've been asked a couple of times what roles or rights or permissions or privileges (I simply mention these synonyms to make sure this blog post will be found by whatever search terms) are required to allow setting up traces in SAP HANA.

When you start the Administration perspective with your vanilla DBA/MONITORING user and switch to the the Trace configuration tab you may get pretty disappointed as you face this screen:

Irritated and annoyed we figure out that we're actually not allowed to change any of the trace settings and specifically not the performance trace that might be most interesting to many.

The reason for this is that the usage of these trace settings are governed by some system privileges.

So in order to allow changes to these settings we need to pimp up our DBA/MONITORING user by granting some of these system privileges:

Out of all the available system privileges TRACE ADMIN suspiciously sounds like the one we're looking for right now.

Let's give it a go, grant the privilege and close & reopen the Administration perspective so that the current user privileges get re-evaluated.

What we see now should be similar to this:

OKAY - we got the Performance Trace unlocked and the Kernel Profiler (anybody ever used this one so far?), so that's not too bad.

But why the heck are the other trace options still blocked?

The answer is simple but leaves the impression of a bit inconsistent permission approach to the tracing options.

For the other traces, the current settings are setup by HANA parameters.

In order to change e.g. the Database Trace settings I need to modify the relevant database parameters!

Therefore (and now it should make sense again) the required system privilege for these tracing options is the INIFILE ADMIN privilege.

Switching back to the trace settings (don't skip the close & reopen part!) sure enough now provides us with all the tracing options we ever dreamed but not dared to ask for *cough*:

Beautiful and amazing, isn't it?

(I believer I never put so many checkmarks in onto a single screenshot - so this could easily be my most positive one ever :wink: ).

That's all folks!

Cheers,

Lars

8 Comments