Developing an OLAP cube, testing in Enterprise Guide or Web Report Studio, and suddenly you begin getting error messages from rebuilding the OLAP Cube stating that it's locked. Now what do you do? Restart the OLAP Server? Well, if you don't have access to the server itself or others are using the OLAP server this just won't do.
SAS Management Console 9.2 to the rescue!
If you can access management console as an administrator, connect to the OLAP Server, check sessions and stop the ones that are locking your poor cube into the old state. Whoohoo! No more restarting services!
BTW - If you 'X' out of your Web Report Studio Internet Explorer session while you are viewing an OLAP cube based report, you will lock the OLAP cube. Always be sure to log off the web application. I've seen this in BI and there is a SAS Note about this occurring in SAS Profitability Management.
2 Comments
I wish there was a way of kicking everyone off through scripts.I have a script that updates a cube every night and there is always some after hours worker locking it.
If it is done by SMC, then it is done with java code. Meaning it is close to a script. It probably requires a bit of research how to connect OLAP server to administer cubes, but for sure there must be a java interface for that.Do ask nearest SAS technical support :)
One Trackback
[...] This is awesome, as you then don't have to worry about users locking your cube by closing the Web Report Studio window or leaving their EG session running. However, at the same time, this can cause the size of space an OLAP cube to increase (usually the [...]