First off, Id strongly recommend NOT using BI Analyses as the data source for the BIP report. The performance is terrible and the feature was put in to meet a requirement for very small and fast running reports. When the BIP report is run, it calls OBIEE to run the analysis. The query i the analysis is executed and the results returned to the the presentation services when then render the data as XML output and that is passed back to the BIP data model engine. Its slow and fraught with issues. Im not sure of the linkage btw BIP and the presentation services (PS) in terms of whether, BIP checks with PS to see if the report is complete or if PS nudges BIP when it is complete. I think is the former.
Either way, you are getting a disconnect between the two and the report is failing to render, I would recommend just grabbing the query out of the Analysis and pasting it into the BIP data model and use the BI Server connection. You get the security of the BIEE rpd model without the overhead of the report having to be formatted and rendered to XML and passed back to the BIP data model.
If you want to pursue the issue. Id log an SR with support to get some help. Make sure you include a trace 32 log of the report run with the SR - https://docs.oracle.com/cd/E17904_01/bi.1111/e13880/T526682T542464.htm
Also you don't say anything about what version you're on or what the actual error is.
My version is 220.127.116.11.0
First error is
Message ID BEA-101017
User <WLS Kernel>
Thread ID [ACTIVE] ExecuteThread: '31' for queue: 'weblogic.kernel.Default (self-tuning)'
Message: [ServletContext@2138351132[app:analytics module:analytics-ws path:null spec-version:3.1]] Root cause of ServletException. java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.net.SocketInputStream.read(SocketInputStream.java:171)...
And then (the same time) Incident Error:
Message ID DFW-40104
User <WLS Kernel>
Thread ID [ACTIVE].ExecuteThread: '31' for queue: 'weblogic.kernel.Default (self-tuning)'
Message: incident 55 created with problem key "DFW-99998 [java.net.SocketTimeoutException][oracle.bi.security.filter.BISecurityFilter.handleAnonymousSubject][analytics]"
In Incident's readme file I found error BEA-101017 is the reason of incident.
Problem Key: DFW-99998 [java.net.SocketTimeoutException][oracle.bi.security.filter.BISecurityFilter.handleAnonymousSubject][analytics]
Application Name: analytics
Name: <WLS Kernel>
Error Message Id: DFW-99998
DFW_APP_NAME : analytic
DFW_USER_NAME : <WLS Kernel>
So additional to everything timdexter told you, there's this:
My version is 18.104.22.168.0
Ref MOS Doc ID 2070465.1: "Error Correction for 22.214.171.124 ended: June 2017"
a) rethink how that data model sources its data
b) rethink if the analysis makes sense to begin with (like pulling in millions of rows across hundreds of columns just to show 12 months with 2 measures)
(not necessarily in that order)
Tim, thank you for so detailed answer
It's really good advise about copying sql query from analisys and paste to dataset.
I've tried it befire. It works, but it's not convenient to make changes in future.
Logging SR will help me probably
Thank you for the advice, but I tried to upgrade twice. And after upgrade new admin tool changed the levels order in hierarchies in rep during saving, created warnings and even errors (I found this as registered bug with no decision). So I was forced to rollback first and second bundle putches.
I've never ever seen that. What bug is that?
Normally what I've seen is that most RPD issues where tied to invalid config in the source version. Not the destination version.
I can't find it now on oracle support.
And I told about patching not about upgrade. I learnt a lot about upgrading from your link. I need to think much about.
Ok not sure what you exactly mean with "And I told about patching not about upgrade" but if your question is answered then can you please close this thread?
My first question is not answered. I asked about setting timeout for solving the problem and recieved answer only about workaround and recomendations about upgrade
I still hope sombody knows about timeout I need to set (if it exists)