Technically speaking this is not a bug but a feature of Jedox software. Jedox has the possibility to lock a specific area of the cube in order to disable additional data entering. The majority of the time users click on this functionality by accident and then owners of the application break the head what went wrong. When the cube is locked, elements cannot be added or deleted. Etls cannot run import as well.

The error usually displays the following message “M_EL1 – dimension is locked: dimension is used in a locked cube”

Locked Cube Dimension
Locked Cube Dimension

One reason for the error could be the Hold functionality is triggered by the user as follows:

A similar thing is with Enable Undo functionality as well. Both of this information could be found in modeler under Cube properties.

Once both of the actions are released, an error will not appear anymore. After that users could continue adding the data or working on the architecture of the database.

In case you try to add or delete an element and an error shows that Dimension is in the lock mode, you will need to check all cubes where the dimension exists and see if something is locked. [attribute cubes as well].

If the problem still persists after all the above actions, a restart of OLAP would be the ultimate solution. In that case, the reason could be that somewhere inside the macros of your reports you use PALO.EADD where the connection is not properly closed. 

Please check if palo_disconnect($conn); is properly set.

Bug often appears when there is a frond-end widget for adding, deleting, or moving elements by macro PHP code.

The model presented can be found here.

How to use HOLD funcionality?

How to use Enable Undo funcionality?

 

 

1 Comment

  • Alexander Beth

    Very helpful. Thank you very much for this post. We had this error when we wanted to change entries in a dimension. We were able to fix it with your instructions.

Comments are closed.