This content has been marked as final. Show 2 replies
If that is your code, I don't see where you are logging out after the QueryResult.rowset call.
Also, Are you 100% that your attempt to use an I/O operation with the WriteToFile() function that you are calling isn't causing your issue?
Try to comment out the WriteToFile() call and just write the QueryResult.rowset to the console/system output to see if the recordset XML is actually getting retrieved. Even long running queries should return some information.
In addition, test your query in OBI Presentation Services. If the query is taking 20 minutes to run in presentation services or it timesout there you may just want to update the query so that it returns less records, etc. Whatever affects you receive in presentation services in regards to timeouts, etc. are basically the same as those seen when calling the web services.
Thank you for the reply.
I do agree that i have omitted logging out command line and WriteToFile() definition. The below executesqlquery command is a syncronous call. I do not think it will be a problem with the next two or three lines. Below mentioned command line will not be released by the compiler until and unless it is completed. MOreover i am sure that the two mentioned command line does not have to do much on the issue becouse the error message is associated with below line and also works fine on simple query.
QueryResult = xmlviewservice.executeSQLQuery(qry, Obiee_Services.web_Reference.XMLQueryOutputFormat.SAWRowsetData, xmlQueryExecutionOption, sessionid)
I have tested other work around to resolve the current error i.e "Operation Time Out" error atleast(applying other configuration setup and increasing timeout properties). Having resolved sucessfully the next issue is on the below line. Blank rowset is returned each time. I can get an ID on QueryResult.QueryId and QueryResult.Finished=false.
Dim rstring As String = QueryResult.rowset
Finally, in OBI Presentation Services, the query runs fine in a specific time.