Managing Essbase Security Backup Files

Each time you start Essbase Server, Essbase creates a temporary file, named tempessbase.sec, that is used to validate the Essbase security file (essbase.sec). When Essbase Server successfully starts using essbase.sec, tempessbase.sec is deleted and Essbase creates a security backup file, named essbase_timestamp.bak.

You can manage the number of security backup files that Essbase maintains; the interval at which the security backup files are created; and whether to switch to the latest, valid security backup file on startup if the essbase.sec file is invalid.

The content of essbase_timestamp.bak is encrypted.

  To update the essbase_timestamp.bak file, use a tool:

Tool

Topic

Location

Administration Services

Updating the Security Backup File

Oracle Essbase Administration Services Online Help

MaxL

alter system sync security backup

Oracle Essbase Technical Reference

essbase.cfg

NUMBEROFSECFILEBACKUPS

SECFILEBACKUPINTERVAL

ENABLESWITCHTOBACKUPFILE

 

Note:

Essbase automatically creates a backup of the security file before and after migration (essbase.bak_preUPM and essbase.bak_postUPM). See Migrating Essbase to EPM System Security.