Hello
Version: Essbase 11.1.2.3.508 on Exalytics
We've been having this issue for around a month (I know this begs the question "what has changed since the last time it was working" but as far as we know, nothing)
When executing a calc script that takes around 10 hours with MaxL we are getting a timeout.
Basically I have a 'spool on' to a log file with an execute calculation command, and all I get in my log file is
MAXL> login $key 123456789 $key 123456789 on server.com:6423:secure;
OK/INFO - 1051034 - Logging in user [USER@AD].
OK/INFO - 1241001 - Logged in to Essbase.
MAXL> execute calculation app.cube.script;
Then nothing. The calc script actually completes successfully in Essbase, it's just that the MaxL triggering the calc is never getting a return from Essbase.
In the app log we find the following.
[Thu Mar 10 00:18:52 2016]Local/app/cube/USER@AD/140496033700160/Error(1042017)
Network error: Timed out before receiving all data
[Thu Mar 10 00:18:52 2016]Local/app/cube/USER@AD/140496033700160/Error(1013295)
Server Request Fails with error code [1042017]
I must say I was hoping for this message to appear after a specific amount of time like 720 minutes so I would just have to look for a setting with that value but nope. This message appears a few seconds after the calc script is actually completed, so I believe it is Essbase trying to send back a status to the MaxL that launched the calc but fails to do so.
I don't think the MaxL session itself is timing out, I was more thinking of a timeout on the OHS side, but I haven't done infrastructure setup and tuning in a while, and do not have access to the server (only a useless offshore team does) to actually search myself for the right setting to change if any.
I would appreciate any recommendation as to which setting could be altered.
Thanks
JM