I do not believe that this is a PLSD problem because we have similar issues in other products, but I was hoping that somebody might be able to tell me where to have the DBAs look.
If we wait for the 'down arrow' with the first set of results and then click on the export icon, often the database will disconnect you if you do not click it instantly. Sometimes, it disconnects before you even get the down-arrow lit. Even if you start the query using the auto-download and have a result set of more than 50,000-100,000 rows, sometimes it will also get disconnected. Sometimes the text importer gets disconnected similarly. Nothing seems to happen very consistently, like it was handled with a timer that I can trace.
This never happened in PLSD versions 9 or 10 or in regular Oracle 10 or 11. It happened rarely with Ver. 11 in Oracle 11, but much more often in Exadata 12c. I have it happen rarely to me, but my ID is set to time out less often, but we're talking the difference between 30 minutes for regular users vs. 4 hours for support users. (I could duplicate it if I had the DBAs set me to be a 'regular' user.) I can believe that the system will time out my object browser after 30 minutes, but I would hope that it wouldn't time me out if the query paused more than 30 minutes to get more results in the middle of an export. So far, I haven't been able to catch one of these instances with a person who I've had turn application logging on.
My guess is that the Exadata central CPU gets at least a partial result set, hands the export transfer off to another part of the system, and if the network is slow or something and the transfer doesn't come back for another batch of results quickly, it disconnects the session. That seems to fit the evidence, but I don't know how to find what that setting is.
Any ideas?
Thanks
Ron
If we wait for the 'down arrow' with the first set of results and then click on the export icon, often the database will disconnect you if you do not click it instantly. Sometimes, it disconnects before you even get the down-arrow lit. Even if you start the query using the auto-download and have a result set of more than 50,000-100,000 rows, sometimes it will also get disconnected. Sometimes the text importer gets disconnected similarly. Nothing seems to happen very consistently, like it was handled with a timer that I can trace.
This never happened in PLSD versions 9 or 10 or in regular Oracle 10 or 11. It happened rarely with Ver. 11 in Oracle 11, but much more often in Exadata 12c. I have it happen rarely to me, but my ID is set to time out less often, but we're talking the difference between 30 minutes for regular users vs. 4 hours for support users. (I could duplicate it if I had the DBAs set me to be a 'regular' user.) I can believe that the system will time out my object browser after 30 minutes, but I would hope that it wouldn't time me out if the query paused more than 30 minutes to get more results in the middle of an export. So far, I haven't been able to catch one of these instances with a person who I've had turn application logging on.
My guess is that the Exadata central CPU gets at least a partial result set, hands the export transfer off to another part of the system, and if the network is slow or something and the transfer doesn't come back for another batch of results quickly, it disconnects the session. That seems to fit the evidence, but I don't know how to find what that setting is.
Any ideas?
Thanks
Ron
