I am wondering if anyone has experienced the following error in SmartView 220.127.116.11.002 / APS 18.104.22.168.002.
When I am performing a retrieval on an Essbase application/database (BSO/ASO), I am getting the following error message:
Concurrent requests on the same session are not alllowed. Wait till the previous request completes processing.
I have noticed that I get this error after processing the request goes longer than 5mins. When I look at the Essbase session in EAS I can see the request still being performed by Essbase but the APS has disconnected me and I have to login again.
I have adjust the registry settings on the client perform the retrieval to increase timeout settings, I have turned compression off and on.
However no luck. I can replicate this error on a stand alone server which puts doubt that it is a network issue. I have also increase the maxstrucktread in the APS weblogic server from 600 to 1200 but with no success.
I am pretty sure I have been able to run a 40min retrieval using the same version of Smart View and APS at another client.
Has anyone seen this error or being able to run a SmartView retrieval with data for over 5mins?
Any help would be great. Issue has been logged with Oracle Support to verify if they can replicate the issue.
In the same readme provided look under #9404387, they state that is is resolved or am I mis-reading it?
Also do you know what they mean by a XMLA stateless session? I am pretty sure I am just running a SmartView session as I can see the session under the Essbase Provider Server and its states it is a SmartView session.
Did you apply the settings to the APS server too? This is the information Oracle sent to me for an unrelated but similar issue.
If on Windows, please check the following reg key values:
Another possible culprit I can think of is heap size.
With regards to where to set Java Heap, please refer to the following doc:
Did you apply the reg settings to both client, as well as APS server?
Please also apply the following:
Reg Settings: Local Machine\System\CurrentControlSet\Services\TCPIP\Parameters
Add/amend NETDELAY 1000 and NETRETRYCOUNT 1500 - in essbase.cfg and stop/start Essbase/APS
I haven't fully applied the settings (it's for a client I won't get the chance until next week) so can't say if it works or not, but your certainly sounds like a timeout error.
Hope it helps.
We have applied Patch 11823281 and since then we are getting that error. However rolling back to the original 22.214.171.124 version of APS we got a similar problem but a different error.
We were getting Invalid Pointer decompression error. This is after we have disabled compression in the APS server. However after more investigation we were getting this error after SmartView runs for 5mins as well.
Currently I just don't seem to be able to execute a SmartView query over 5mins with 126.96.36.199. The query is still running in Essbase, however we get the error from the client end. This is happening both to an ASO and BSO cube.
I thought at a previous client I was able to execute a 40min query via SmartView. The only thing that is difference is that they were on Excel 2003 as oppose to Excel 2007.
I have also updated the java heap size via the Windows Registry and updated a number of settings in the registry both at the client and server. However I will review the registry setting that you have recommended and see what results I get.
Thanks for the additional details. I tried changing those settings and re-starting APS and OHS service but I still got the same error at exactly 5 minutes. I have opened an SR with Oracle, I'll update this thread if I get more information.
If you have a distributed environment trying changing what I suggested on all the servers that contain Weblogic.
We had the case raised as a Sev 1 and after going through development, they told us it was just our setup and that something in the Weblogic file needed to be updated.