Toad 13.3 'Not Responding' When Running SQL

Toad for Oracle
1

Ever since upgrading to 13.3 when executing a SQL statement, it will randomly freeze up while the time count is on screen and show 'Not Responding'.

Once the SQL has completed and returns and unfreezes.

Is this a known bug in the latest version?

2

I have seen a short freeze near the end (I think this is during a big fetch) but that's all. Not enough to get the "not responding" state from windows.

how long do your freezes last? Checking this option should prevent that.

image
image1072×668 26 KB

3

The freezes last for as long as the SQL takes to return which can be anything from 30 seconds onward.

Sometimes it just freezes up permanently and you have to kill the program.

Thanks for the advice on the Transactions setting.

I'll see how that goes.

Is there a performance impact on using this setting or anything else I should know about it?

4

That setting will create a separate session in the database and run your SQL in a background thread.

So with that option checked, just be aware that insert/update/deletes made in the editor won't be available in other areas of Toad until you commit.

1 Like
5

I also have this problem. I have to shutdown Toad at least 5 times per day because the session becomes unusable. The memory usage grows and then the session gets into a non-responding state for a long while (even when trying to run the simplest of queries). My screen also flashes. I always use execute queries in threads.

6

It sounds like your sessions are timing out due to a network setting. After you are timed out (but don't realize it), and you do something in Toad which results in Toad trying to execute a query, the long wait is the Oracle client waiting on the Oracle server to respond (and Toad is waiting on Oracle client).

Two suggestions -

  1. go to Options -> Oracle -> Transactions. Set "On Test/Reconnect" to "Always disconnect and reconnect". Also set "when closing connections" to "Just disconnect". (Hover your mouse over that option to see how commits/rollbacks are handled).
  2. After you've been idle for a while (or Toad hasn't been running any queries in a given connection), before you do anything that might result in a query, go to main menu -> Session -> Test all connections.

Another thing you can do that might help keep connections active is open some window in Toad that runs periodic queries. The transactions window is a good one for that. It's on the main toolbar next to commit/rollback (has a database icon with a question mark over it). Check the "refresh" option in the window that appears. I think the default interval is 10 seconds, but you can increase to 60 or more if you want - just whatever is frequent enough in your environment to prevent disconnect.