Essbase uses a checkout facility for database artifacts to ensure that only one user modifies an artifact simultaneously. This section describes how to lock and unlock artifacts, with the exception of outlines. See Locking and Unlocking Outlines.
Locking artifacts is not the same as locking data blocks. 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 artifact. You can open a locked artifact and edit it, but you cannot save over the existing artifact. To save changes made to a locked artifact, save the modified artifact to a different location. You can execute and copy locked artifacts.