Essbase uses a check-out facility for database objects (such as calculation scripts, report scripts, and rules files) to ensure that objects are modified by only one user at one time. By default, Essbase asks you to lock objects when you open them and deletes your locks when you exit the object editor. For some objects, you can change the default locking behavior. See Setting Essbase Default Options.
Note: | This topic does not discuss outline locking and unlocking behavior. See Locking and Unlocking Outlines. |
You can open, edit, execute, and copy locked objects. You cannot save, rename, or delete locked objects. To save changes to locked objects, you must select File and then Save as, and save the modified object to another location.
If you attempt non-permitted operations on locked objects or on applications or databases that contain locked objects, Essbase displays the Unlock Objects dialog box, which asks you to remove locks and continue with the operation. You can view and unlock objects, according to your security permissions. Users with Administrator permissions can unlock any object. Users without Administrator permissions can unlock only objects that they locked.
Note: | Object locks and user locks on data are different. For information on data locks, see Viewing Data Locks. |
To view and unlock multiple locked objects:
From Enterprise View or a custom view, select an Essbase Server.
Right-click, and select Edit, and then Locked objects.
In the Locked Objects window, perform an action:
To unlock specific objects, select the rows that contain the objects, and click Unlock.
To unlock all objects, click Unlock All.
To lock or unlock one object manually:
From Enterprise View or a custom view, select an unlocked or locked object, for example, a calculation script.
Right-click, and, depending upon whether you selected an unlocked or locked object, click Lock or Unlock.
alter object (MaxL) in the Oracle Essbase Technical Reference
unlockobject (ESSCMD) in the Oracle Essbase Technical Reference