This Essbase discussion board is provided as a free service and dedicated to all the Essbase professionals out there!
 Return to Index  

No real solution, but here's what I did....

January 6 2017 at 9:22 AM
No score for this post
sdt 
from IP address 208.203.94.34


Response to Answers to this all over this message board

What I did is re-arrange the to disable connects and commands first then when I get to 'kill request' I run it three times with a 10 sec pause in between. Only thing I can think of is Essbase did not kill the process that was going on and export failed. Figured I would kill three times to reduce the chances of it happening again. Not sure if this is valid but going to give it a whirl.

Thanks for links to other posts!!!!

set timestamp on;
echo "First attempt to kill any processes on "$AppName"";
alter system kill request on application $AppName;
iferror 'DisableConnectionError';

echo "Pause 10 Seconds";
shell "@ping -n 10 localhost > nul";

echo "Second attempt to kill any processes on "$AppName"";
alter system kill request on application $AppName;
iferror 'DisableConnectionError';

echo "Pause another 10 Seconds";
shell "@ping -n 10 localhost > nul";

echo "Third attempt to kill any processes on "$AppName"";
alter system kill request on application $AppName;
iferror 'DisableConnectionError';
set timestamp off;



 
Scoring disabled. You must be logged in to score posts.Respond to this message   

RSS feed for this forum - http://www.network54.com/Forum/58296?xml=rss. Please email hypess (at) gmail.com, if you have any questions/feedback/issues.