We are moving from regular Oracle 11 to Exadata 12C in a multi-instance RAC environment, using PLSD ver.11.0.6.1776 (32 bit).
In regular Oracle, starting with ver. 11, the 'main' session which controls the object browser, etc. seemed to disconnect after about 10 minutes, even though we could find no database or PLS setting to cause that. (Prior PLS versions didn't seem to disconnect that quickly.) It normally wasn't as much of a problem because we could use the SESSION tab at the top and log back in and continue editing, as long as we didn't actually have a program running. Running programs seemed to return data like normal even when the main session had apparently disconnected.
With Exadata, when a program runs longer than about 10 minutes, at the top of the screen, instead of the "User ID@database name" heading, it shows "Not logged on", and trying to click on anything on the left side gives the same message. After that happens, a running query will run until it gets the first 10 or 15 rows and display them, but, when the user clicks on the down arrow to show more, it gives a 'logged off' message and stops running. We can't find any database setting which controls this (both time-out values have been set to more than an hour), and the DBAs claim that they can't find a SQLNET setting causing it either. We have been able to get around it by clicking the icon to automatically save the results to a PC file, bypassing the UI, so the program is not the problem.
Has anybody run into anything like this with Exadata? Are there any settings or things that we need to watch out for with the RAC setup?
Thanks,
Ron E.
In regular Oracle, starting with ver. 11, the 'main' session which controls the object browser, etc. seemed to disconnect after about 10 minutes, even though we could find no database or PLS setting to cause that. (Prior PLS versions didn't seem to disconnect that quickly.) It normally wasn't as much of a problem because we could use the SESSION tab at the top and log back in and continue editing, as long as we didn't actually have a program running. Running programs seemed to return data like normal even when the main session had apparently disconnected.
With Exadata, when a program runs longer than about 10 minutes, at the top of the screen, instead of the "User ID@database name" heading, it shows "Not logged on", and trying to click on anything on the left side gives the same message. After that happens, a running query will run until it gets the first 10 or 15 rows and display them, but, when the user clicks on the down arrow to show more, it gives a 'logged off' message and stops running. We can't find any database setting which controls this (both time-out values have been set to more than an hour), and the DBAs claim that they can't find a SQLNET setting causing it either. We have been able to get around it by clicking the icon to automatically save the results to a PC file, bypassing the UI, so the program is not the problem.
Has anybody run into anything like this with Exadata? Are there any settings or things that we need to watch out for with the RAC setup?
Thanks,
Ron E.
