Understanding the Precedence of Database Settings

Essbase provides default values for some database storage settings in the essbase.cfg file. You can leave the default settings or change their values in two places:

Changes made for an individual database permanently override essbase.cfg settings and Essbase defaults for the relevant database until they are changed or withdrawn.

If you use MaxL or Administration Services Console to change settings at the database level, the changes become effective at different times, as shown in Table 152:

Table 152. Database Setting Precedence

Setting

When setting becomes effective

  • Index cache

  • Data file cache

  • Data cache

  • Cache memory locking

  • Disk volume

After you stop and restart a database

Isolation level parameters, concurrency parameters

The first time after setting these values that there are no active transactions

All other settings

Immediately

If you manually change these database settings in essbase.cfg, you must stop and restart the relevant application to make them effective.

Note:

The size of index pages is fixed at 8 KB to reduce input-output overhead, as well as to simplify database migration.