Killing a user session?

Question

Running Essbase 11.1.2 ASO cube...occassionally, when I attempt to kill a user session in EAS, I get the status of "terminating". I try to kill the session using Maxl commands to no avail. I know as a last resort to use task manager to end the ESSSVR.exe process -but I have been burned by this in the past as the database gets corrupted. Does anyone know of a safe method to kill these "terminating" sessions? and why are some easy to kill through EAS and others are not?

Answer 1

Hi ,
You may find the following entries in the application log which means there were hung sessions.
+[Mon Jan 24 13:23:46 2011]Local/ESSBASE0///Error(1013290)+
Failed to logout user []: timeout while waiting for requests to die
+[Mon Jan 24 13:23:46 2011]Local/ESSBASE0///Info(1056092)+
Sessions logged out [0]
However, it is difficult to say why these errors occur exactly. Usually Errors like this occur because there are still processes running in the memory when the next transaction is called.
A vast majority of errors can be avoided by integrating pauses and by unloading the application and then reloading it after each calculation or member/data load.
When you kill a session from the EAS Console for a particular user, you need to wait for some time before the process gets compeltely killed, which perform a restructure or data load or data aggregation. You need to wait untill the process gets killed completely before performing any operations on the application.
Never allow any other user to modify outline or update data whenever the Calculation is running. This can cause the application to go into a hang state and whenever you try to kill and if it fails, then you need to kill the ESSSVR process manually. For instance, follow the below guide lines when running Calc scripts:
1) Never allow any other user to indulge any activity on the application. It is preferred to schedule the batch script as a nightly process, if it is a large operation to avoid user interruption.
2) In case of hangups, use the UNLOCKOBJECT command (ESSCMD) to first unlock all the objects that are accessed by the script (Check the technical reference guide for the command ).
3) Next log off the user using the LOGOUTUSER command, but here if you have multiple sessions of the same user logged in the application, all the sessions will be logged off. In this case use the EAS console and kill all the requests of the user first and then kill the session of the user.
Suggestion:
Try to execute the following MaxL commands as batch script and check if the execution of Calculation script is successful:
spool on to 'D:\output\backup.log';
login admin mypassword on localhost;
alter application <app_name> load database <db_name>;
alter system logout session on database <db_name>;
Shell Sleep 30;
alter system kill request on database <db_name>;
Shell Sleep 30;
alter application <app_name> disable commands;
Shell Sleep 30;
Execute Calculation <app_name>.<db_name>.<calc_name>;
Shell Sleep 30;
alter application <app_name> enable commands;
Shell Sleep 30;
logout;
exit;
You can also refer the doc: How to Kill the Essbase Processes/Sessions in 'Terminating' Status (Doc ID 839411.1)
Hope it helps...
KosuruS