Write access denied for admin

[Catherine]

Hello,

I have a problem entering data in a cube. I did enter some data in that cube until a few days ago. I'm logged as an admin, there are no calculation rules. I'm trying to enter data at a leaf level.
I'm working with version 10.1.

If I build another cube with exactly the same dimensions, I'm able to enter data.

Could there be a lock somewhere? Any ideas?

Thank you

[jim wood]

Are you using work flow? Check the cube security to se if somebody has reserved it or check dimension / element security for the same,

Jim.

[Catherine]

Yes, I'm using workflow.

If I right clik the cube and go to security, I can reserve it or lock it so it means it isn't yet. Is there another place to check it?

Regarding dimensions, it could not be the case because if I create another cube with the same dimensions, I can enter data.

Thanks for your help.

[jim wood]

There are a series of control cubes associated with the workflow hierarchy. I'm not 100% certain where (when a submission has been approved) the lock is stored.

[Catherine]

There are a series of control cubes associated with the workflow hierarchy. I'm not 100% certain where (when a submission has been approved) the lock is stored.

Does anybody know more about it ?
The thing is I'm on a development environment and nobody has connected to it except me. So I am wondering why I was able to enter data a few days ago, and not today !

[Catherine]

Hello,

I have still not solved my problem.
One workaround is to delete and recreate the cube and that is what I did last time.

But the problem appears again today. I was able to enter data alla day long on Tuesday. And today (nobody connected yesterday) I am not able any more. One thing even more strange, I restored Tuesday mid of the day backup (I am sure I was able to enter data all day long) and I can not enter data !

Thank you in advance for your help

[Catherine]

I have a partial answer to my problem.

Considering that if I recreate the cube, I do not have the problem anymore, it is not linked to any security problem on the dimensions. So I had a look at control objects concerning cubes.
I found a cube called }SecurityOverlayGlobal_CubeName which has two dimensions, first is the Workflow dimension and other one is again a control object, dimension named "}SecurityOverlay". This dimension has one element "OverlayData".
This cube contains 1 on my entities (workflow dimension).

If I suppress the 1 regarding one entity, I can enter data again.

But my question remains:
What is the purpose of this cube?
When are the data inside updated?
Why does it prevent even admin to enter data?

I couldn't find anything in IBM documentation.

Thanks for your help

[qml]

But my question remains:
What is the purpose of this cube?
When are the data inside updated?
Why does it prevent even admin to enter data?

You will find some of the answers to your questions (or hints thereof) in this thread. The behaviour you are seeing is caused by a contribution application and someone submitting nodes in it. If you want it to go away then do not create the application for that cube or use a different type of application.

[Catherine]

OK I see. If I unterstand well, the content of this cube is not taken into account right now when I re-build the cube, but only next time I restart the instance.

It only remains me one question (so far ):
I do not have any more applications (I used the process }tp_admin_delete_all), but those }SecurityOverlayGlobal_CubeName cubes remain in my TM1 instance, preventing admin to enter data. Why?
Can I suppress those cubes or should I only clear the content (knowing that I will recreate the application in a few days) ?