TM1 Forum

My predecessor setup a cube security for dimensions. I want to eliminate it. It is not as simple as deleting the security cube, is it?

Eric wrote:My predecessor setup a cube security for dimensions. I want to eliminate it. It is not as simple as deleting the security cube, is it?

I've never had the "pleasure" of needing to do this, but if I did I think I'd prefer to take the server down and move the relevant .cub file out of the data directory. I just get... shall we say, a bad feeling about having a server session which may still think in some corners of its mind that there's security on a dimension. At least if it can't find a .cub file to load, it should start afresh with the dimension completely unsecured.

The client will not allow you to delete security cubes (from my experience). You have two options that I have seen work in the past.

1) Delete the rule file (if there is one) and change everything back to "write" through the front end (not directly in the cube). This has been hit or miss for me in the past.

2) Take Alan's suggestion and move it through the back end while the server is down. This is probably the easiest and cleanest way to do it.

I believe you can't delete _any_ object starting with } . Martin may remember creating such an object at a client, just to hold some structural stuff, and finding he couldn't get rid of it. I agree with Alan - rename/remove the object on the disc and restart.

If you want to eliminate a }CellSecurity_ or }ElementSecurity cube the best (and only) way to do it is to take the server down, delete the .cub file and restart.

David Usherwood wrote:I believe you can't delete _any_ object starting with } . Martin may remember creating such an object at a client, just to hold some structural stuff, and finding he couldn't get rid of it. I agree with Alan - rename/remove the object on the disc and restart.

Indeed I do remember that occurrence. I wanted to hide some TI parameters. The only way was, as Scott confirms, to shut the server down, delete it in the back end, and restart the server. Which took two hours at that particular client.

Martin

thanks everyone

2 hours

OUCH!