Quick note on cleaning up the SAP HANA Studio folders after upgrade installations

based on rev. 41 of SAP HANA Studio

Dear fellow SAP HANA users!

SAP HANA SPS5 has just been released which means it’s patch-o-clock for my system.

As usual, the actual update procedure was straightforward and hassle-free.

I still use the manual way to install the upgrade by running hdbsetup.exe – if you’re using the HANA software repository with automatic update enabled then you’re even better off.

So far so good, but when I had a look into the file system folders HANA studio uses on my computer I found that there are several folders that obviously belonged to older revisions and hadn’t been removed automatically.

Personally, I like it clean and simple and decided to get rid of those folders, even though they only contain a couple of MB worth of files.

The folders to look out for this are located in your

    <user profile folder>\hdbstudio
                           + .backup
                              + ...
                           + oss
                           + ...

    <user profile folder>\.eclipse  
                           + com.sap.ndb.studio.product_1.0.36.201208311914_511115836
                           + com.sap.ndb.studio.product_1.0.37.201209131958_511115836
                           + com.sap.ndb.studio.product_1.0...

Apparently, these folders are created by the P2 director installation tool, that is used for SAP HANA Studio provisioning.

During my testing, these folders and the files in them were never touched again by HANA Studio, so these can be safely deleted.

The ‘oss‘ folder located in <user profile folder>\hdbstudio is something that you may not find on your computer, as this is the separated workspace used for remote service connections to customer systems by SAP support.

For each and every customer system and every connection to those systems, a new workspace gets opened to provide clean environments every time

But also these workspaces are not required for the well functioning of SAP HANA Studio and can, therefore, be deleted.

On my system, this freed up 170MB of disk space and removed 4.554 files in 3.031 folders.

If you now argue that performing this cleanup task doesn’t add or improve any functionality, stability or productivity of SAP HANA Studio, you’re spot on.

But as I said: I like it clean and simple 🙂


You got to fight for your right to … setup tracing

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 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 set up 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 believe I never put so many checkmarks in onto a single screenshot – so this could easily be my most positive one ever 😉 ).

That’s all folks!


Travelling on to new exciting places…

Dear all!

It’s been a while since my last activity here in SCN – and boy what a while it was 🙂 .

In the last couple of months I was travelling to Canada, Australia and New Zealand – partly for SAP and partly as a long vacation Down Under.

And I also assumed a new position within SAP and left my job in AGS support.

As of September I’m rolling with the amazing colleagues of the Customer Solution Adoption (CSA) team and I’m really excited about this.

These are the guys’n’girls that e.g. are behind the SAP HANA materials available on http://www.saphana.com/community/resources.

There’s a lot more that this team does but to cut it short: we help customers to get a beautiful experience with SAP HANA.

One of my first duties in my new job is to visit the SAP TechEd in Madrid.

In fact I’m not only supposed to show off my newly acquired tan there, but I’ll be co-moderating two hands-on sessions on SAP HANA operations: http://madrid.sapevents.com/TechEd/sessions?sf=1224.

I also will likely be present in the HANA Distinguished Engineer Chat (http://madrid.sapevents.com/TechEd/sessions?sf=1225) on Thursday afternoon.

So, If you like to get your hands a bit dirty on a SAP HANA system or have a chat with me, you now know where to find me 😉 .

So, hope to see you all there and cheers,