All security information is stored in the security file (essbase.sec) in the ARBORPATH/bin directory. Changing or deleting the following Essbase security entities can cause fragmentation in the security file: filters, users, groups, applications, databases, substitution variables, disk volumes, passwords, and other Essbase objects. Too much fragmentation in the security file can slow down security-related performance.
Essbase compacts (defragments) the security file automatically each time Essbase Server is stopped. You can check the defragmentation status of the security file and, if desired, you can compact it without stopping Essbase Server.
Note: | Compacting the security file while Essbase Server is running slows down Agent activity until the operation is completed, which could take a few minutes. |
To manually compact the security file:
From Enterprise View or a custom view, select the Security node under the appropriate Essbase Server.
Right-click and select Compact security file.
“Managing the Essbase Security File (essbase.sec)” in the Oracle Essbase Database Administrator's Guide
display system security file fragmentation_percent (MaxL) in the Oracle Essbase Technical Reference
alter system security file fragmentation_percent (MaxL) in the Oracle Essbase Technical Reference
compact (Essbase Agent) in the Oracle Essbase Technical Reference
SECURITYFILECOMPACTIONPERCENT (essbase.cfg setting) in the Oracle Essbase Technical Reference