Is anyone using PL/SQL Developer to use with a database on a VM in the Microsoft Azure cloud? We are trying this and encountering some issues that make it difficult to use. Once you get connected, it seems to work just fine, but getting a connection and maintaining the connection is the problem.
When starting PL/SQL Developer and entering the username/password/database information, we are more often than not running into one of two problems:
1) The login dialog box disappears, but the main window never appears. You have to go find the process in Task Manager and kill it.
2) The main window appears, but goes into a "Not Responding" state. If you press the close window icon (the X in the top-right hand corner of the window), Windows presents a dialog box with three choices: Attempt to restore the application, close the application or wait for the application. If you chose "restore", Windows is usually able to do something such that the PL/SQL Developer window comes alive and you can now work in it.
The second connection issue is that if you leave the PL/SQL Developer window idle for any long period of time, then window goes back into the "Not Responding" state, and you are back in the situation 2) above.
The third connection issue is that sometimes long-running queries/functions will lose the database connection. For example, doing the "Compile Invalid Objects" with more than 100 items to be compiled.
I have tried using both the v12 Oracle client (our usual configuration) and the v18 Oracle client (the database on the cloud is v18), and have the same problems with both.
Any suggestions?
When starting PL/SQL Developer and entering the username/password/database information, we are more often than not running into one of two problems:
1) The login dialog box disappears, but the main window never appears. You have to go find the process in Task Manager and kill it.
2) The main window appears, but goes into a "Not Responding" state. If you press the close window icon (the X in the top-right hand corner of the window), Windows presents a dialog box with three choices: Attempt to restore the application, close the application or wait for the application. If you chose "restore", Windows is usually able to do something such that the PL/SQL Developer window comes alive and you can now work in it.
The second connection issue is that if you leave the PL/SQL Developer window idle for any long period of time, then window goes back into the "Not Responding" state, and you are back in the situation 2) above.
The third connection issue is that sometimes long-running queries/functions will lose the database connection. For example, doing the "Compile Invalid Objects" with more than 100 items to be compiled.
I have tried using both the v12 Oracle client (our usual configuration) and the v18 Oracle client (the database on the cloud is v18), and have the same problems with both.
Any suggestions?
