Automating your Essbase Cube - Oracle Essbase 9 Implementation Guide - page 298

Clear application log
A good practice for an Essbase administrator would be to clear the application log as
often as possible. If the application log file is allowed to get too large users, a marked
decrease in system performance is seen. The good news for the Essbase administrator
is that there is no need to log on to the Essbase server through EAS to clear the log
file. The system administrator can write a MaxL script and use it to clear the log file
on a weekly basis. Be sure to back up the log file for audit trails according to your
company's standards.
Syntax:
alter application <App-Name> clear logfile;
Enable/Disable start up/auto startup
In an application's properties you can set the application to start whenever the
Essbase server is started or you can start an application at the first user request
to log on. These properties can be set by the administrator with a MaxL command.
startup /* Allow user to start Application */
If startup is enabled, the users can start the application upon log on. If startup
is set to disabled, the users will not be able to log on, if the application is not
already started.
Syntax:
alter application <App-Name> enable startup;
alter application <App-Name> disbale startup;
autostartup /* Start Application when Essbase Analytical Server
starts */
If autostartup is enabled, the application will start as soon as the Essbase analytic
server is started. If autostartup is disabled, the application will not start when
the Essbase analytic server is started.
Syntax:
alter application <App-Name> enable autostartup;
alter application <App-Name> disable autostartup;