When I compile a PL/SQL package body that has any syntax error, or invalid table name, etc, it takes about 14-20 seconds and you are disconnected from database. When you RECONNECT, then you are displayed with the error. In the meantime, I have lost all my session data in other tabs, my saved tabs of information, etc.
I am using the latest TOAD Beta 25.3.211.6831 against Oracle Version
| Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production |
| PL/SQL Release 12.1.0.2.0 - Production |
| CORE 12.1.0.2.0 Production |
| TNS for 64-bit Windows: Version 12.1.0.2.0 - Production |
| NLSRTL Version 12.1.0.2.0 - Production |
See the simplest package body with just a missing semi-colon after the null. Hit F9 to compile and it spins for 15-20 seconds and then you get the error displayed ORA-03113.
after you click reconnect you see error:
This also happens on a previous TOAD Version 17 version.
I am doing a DIRECT connect to attempt to take TNSNAMES out of the equation. With TNSNAMES.ora I also get the same error. This is occurring on multiple Oracle Version 12.1.0.2.0 database.
Any help you may be able to provide would be much appreciated. I am sure you can see how frustrating this is :).
Thanks.
Jeff G
Do you have the Execute queries in threads option checked? If so, uncheck it. Does that change anything?
Could it be your client version? What if you establish the connection without using the client. On the Login window, clear this checkbox.
ORA-03113 is a problem on the Oracle side of things. Oracle had some problem and disconnected you. I don't think Toad is doing anything wrong.
If you are using an Oracle client, Toad's no-client option may help as Mike suggested. A newer Oracle client may also help - but my suspicion is that the problem is on the database side of things.
Another thing you can try:
- Turn on spool SQL in Toad (main menu -> database -> Spool SQL -> Spool to screen
- Compile your package to make the error happen
- find the SQL which caused the error in the spool sql output
- Using the same Oracle client that Toad was using - connect with SQL Plus, and try the same SQL there.
- If you get the same ORA-03113, then you have a case that you can open with Oracle support and hopefully they can resolve it. Unfortunately, I have found that when Toad is involved they tend to just blame things on Toad.
I did NOT have “Execute Queries in Threads (create seperate session) checked”
I DID reconnect and I UNCHECKED that “Connect using Oracle Client” and that seems to have solved the issue (for now, and hopefully permanently). I will let you know if it shows up again.
Thanks very much. You can imagine how frustrating yesterday was that every time I compiled and had a syntax error, on invalid column name or anything, I got disconnected from database!
I have used TOAD for many, many years and new had this issue until yesterday.
Jeff G