Hi

I´m having a slight problem with the cube locking up. Like now, I was
working on a cube on friday, left for home with the cube in edit mode.
Now, when I return on monday, the cube works fine but I cant edit
it... I get a message saying:

"Unable to open the cube Cube.

User xx/xxxxx on computer zzzzzzz has locked ’Cube’.
Description: Cube Editor has locked cube ’Cube’ for writing.
"

I don´t know whats going on... what is this lock and how can I take it
off?
And how is it put on?

thanks for any help

Arnar / Iceland

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/OLAP-Problem...ict211200.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=722321

to "unlock it", you can stop/restart the OLAP server service. (if you can't
find and stop the client application which lock your cube)

when a user open a cube using the administration console, a lock is made on
the cube to make sure that there is no other people editing or processing
it.

its why its allways important to close all the applications when the day is
off.
I have some developpers which sometimes omit to quit the analysis server
console, my solution is simple:
I kill the session

if they omit to save something, too bad.


"arnar" <UseLinkToEmail (AT) dbForumz (DOT) com> wrote