Every so often Toad will hang for several minutes with a little non descript screen. It ignores everything I try to do to cancel out of it. How can I stop this from happening.
Thanks
Every so often Toad will hang for several minutes with a little non descript screen. It ignores everything I try to do to cancel out of it. How can I stop this from happening.
Thanks
Are you experiencing this when running query or “without” any knowledgeable reason?
We'll need more info. Can you post a screenshot of the screen you see? What are you doing at the time the hang occurs?
On 09/26/2014 05:06 PM, orenolb wrote:
Thread created by orenolb
Every so often Toad will hang for several minutes with a little non descript screen. It ignores everything I try to do to cancel out of it. How can I stop this from happening.
Thanks
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
I have this happen also. Most of the time it is just trying to lookup for code assist or a connection has been dropped due to inactivity and Toad is looking for the connection.
I’m using version 12.0.0 and Toad hangs when trying to expand the tree on a package Spec. It doesn’t occur when expanding the Body. Has anyone else seen this particular issue? I have to kill my Toad session to get out.
It’s possible that your data dictionary stats are out of date and when toad is querying to see dependencies and such to graphically reflect status - that the missing / stale stats are the source fo the slow down. I’ve written numerous blogs on toad world about such issues and the way to fix it - so query toad world for toad slow and read - it might be this …
this blog: www.toadworld.com/…/help-toad-for-oracle-seems-slow.aspx
has links about half way down to all the stats blogs worth reading …
even if you think I’m way off or just crazy - the fix is simple (run two package calls which takes like 5 minutes) and it might just fix the problem - so little pain to maybe see big improvement
exec dbms_stats.gather_dictionary_stats;
exec dbms_stats.gather_fixed_objects_stats;
I forgot to mention that this is in the Schema Browser but maybe that isn’t necessary. Gathering the stats didn’t fix the issue.
thanks for trying the stats - eliminates some things … sorry it did not work …
We do execute a couple of queries when you expand the spec, but generally these are pretty fast queries. If you turn on Spool SQL (Main Menu -> Database -> Spool SQL), you can watch these queries execute and see how long they take. For good measure, you could try executing them in the Editor and see if they run quickly there. Another thing that happens when you expand a package is that we parse the source code to create the nodes under “spec”. So if it’s not a slow query, then another possibility is that parser is having problems with the package.