Specifying Disk Volumes

Use disk volumes to specify where you want to store Essbase index files (essn.ind) and data files (essn.pag).

Files are written to the disk volume in the following directory structure:

.../app/app_name/db_name

If you do not use the disk volumes setting, Essbase stores data only on the volume where the ARBORPATH directory resides. If the ARBORPATH variable is not set, Essbase stores data only on the volume where the server was started.

For new files, changes to the disk volumes setting take effect when you next start the database. Existing files and volumes are not affected.

Note:

For information about how to check the size of the index and data files, see Checking Index and Data File Sizes.

You can specify disk volumes using Administration Services, MaxL, or ESSCMD. When you use disk volumes, Essbase provides the following options for each disk volume:

Essbase creates data files and index files in these situations:

Essbase names files consecutively, starting with ess00001.xxx, where xxx is ind for an index file and pag for a data file, and continuing up to ess65535.xxx. This naming convention applies to each volume, so in the above example, volumes E, F, and G each have files named ess00001.pag and ess00001.ind.

Keep in mind the following guidelines when specifying disk volumes:

On Windows, you can use Universal/Uniform Naming Convention (UNC) to specify a disk volume as the location of a network resource, such as a shared directory. Syntax:

\\ComputerName\SharedFolder\Resource