About
Essbase uses a checkout facility for database Artifacts to ensure that only one user modifies an Artifacts at one time. This section describes how to lock and unlock artifacts, with the exception of Outline. See Locking And Unlocking Outlines.
Articles Related
Locking Artifacts
Locking artifacts is not the same as locking Data Block. The Essbase kernel handles locking for data blocks but not for Artifacts. See Data Locks.
By default, whenever you open a database artifact, Essbase prompts you to lock the artifact. You can change this default behavior for some artifacts; see “Setting Essbase Default Options” in Oracle Essbase Administration Services Online Help.
When an artifact is locked, Essbase does not allow other users to save over, rename, or delete the Artifacts. You can open a locked Artifacts and edit it, but you cannot save over the existing Artifacts. To save changes made to a locked artifact, save the modified artifact to a different location. You can execute and copy locked artifacts.
Unlocking Artifacts
You can unlock artifacts according to your permissions. In Essbase Administration Services, you can view all Artifacts locks for an Essbase - Servers, Application, or Database.
To unlock an artifact, use a tool:
| Tool | Topic | Documentation Location |
|---|---|---|
| Essbase Administration Services | Locking and Unlocking Objects | Oracle Essbase Administration Services Online Help |
| Maxl | alter object | Oracle Essbase Technical Reference |
| Esscmd | UNLOCKOBJECT | Oracle Essbase Technical Reference |