Analytic Services enables memory management by providing controls on the maximum amount of memory an application can use. Analytic Services also writes messages to an application log as soon as the application's memory use exceeds 90% of the limit that you set. After the limit is met 100%, Analytic Services stops the application.
To enable Analytic Services to manage application memory use:
When 90% of the value in the configuration file is reached, Analytic Services writes this warning message to the application log:
Application is using [n] bytes of memory. It is more than 90 percent of the limit set in the memory config file.
If the application uses 100% of the memory as limited by the Memory Configuration File, Analytic Services writes this error message to the application log and stops the application:
Application is using [n] bytes of memory, and is requesting a new memory block of [n] bytes. The memory has exceeded the limit.
When the 90% warning messages appear in the log, the database administrator may wish to take corrective action:
See the Database Administrator's Guide for more information about memory use. Refer to the sections on cache settings, performance, and estimating memory use.
To enable Analytic Services to write messages to the log when application memory use exceeds 90% of a value you determine, and to limit the memory used by a single application to 100% of the value in the file, create or edit a memory configuration file and add the MEMORY LIMIT configuration setting:
Name the file config.mem to control all applications on the Analytic Server, or name it config.mem.appName to control just one application. Because Analytic Services looks for the relevant application-specific memory configuration file before it looks for the server-wide file during application start-up, you can create one generic file (config.mem) to configure all the applications, and also create individual application memory configuration files (config.mem.appName) for applications that need different maximum memory settings.
Make sure the file is located in the ARBORPATH/bin directory.
Add the MEMORYLIMIT configuration setting to the configuration file.
©2004 Hyperion Solutions Corporation. All Rights Reserved. http://www.hyperion.com |