ITEM Verify which database are running and check access, security and startup information.

Check operating system environment variables as defined on installation and verify path information. Check machine and operating systems constraints impacting Essbase performance Determine whether lack of disk space or incompatible file systems are impacting Essbase performance. On NT systems, consider separating the physical drive on which the NT page file is utilized to minimize disk contention with the drives which essbase is using for paging. A combination of NT settings and ESSBASE.CFG settings can permit this. Check to see what applications and databases are loaded.

NOTES & IMPLICATIONS

This can be the cause of a major. Chance these are set correctly. Commonsense dillgence. Dont use SAN or NFS mounted drives unl have large memory caches.

Check database storage, database statistics, and lock contention.

Databases which are not being used still use memory. It could be useful to have a periodic script shutdown or quiet applications that are not being used. They do not automatically shutdown. Lock contention is all about writeback users and concurrent loads and calcs. Try to segregate that activity out.

Check database status and startup information, cache sizes, and data compression settings. Examine the configuration of the Currency conversion can be a currency database. major source of performance issues. If it is possible to be done outside of Essbase, you should try to do so. The exception would be a specific currency hedging applications for modeling. Check dimension information and characteristics of data blocks in the database (block density, percentage of maximum blocks existing, block size, compression

ratio). Check run time page for lock contention, insufficient cache size (buffer shortage), "hit" ratio on index searches, and number of read and write operations. Check to see where index files or page data files are stored, and whether they span multiple disks. Check record of database modifications for information On last successful data load, calculation, and outline Update operations. On exception, check exception error log report written in $ARBORPATH directory designation. Check Application Event Log File. Check Server Event Log File.

This can make a significant dent in performance. It helps a great deal to understand the virtual memory model of Essbase.

Actions to be taken will Include things such as raising the various caches to possibly Splitting a database into multiple cubes (rare).

Consider licensing a 3rd party tool to collect and analyze essbase log files. Or, consider using VB and Essbase to load log files into an essbase database for analysis.