When Toad is "hung", there are two possibilities: 1) The database is taking a long time to process a query 2) Toad is working really hard on something, like processing a bunch of data. In the first case, your PC's CPU usage in task manager will be near zero. And if you connect to the DB with another copy of Toad, and look in the Session Browser to find the session of the "stuck" Toad, you'll that it's session status is "ACTIVE". You can go to the "Current Statement" tab to see the query. Spool SQL shows the query that just completed, so that's not always the best technique to find a query that won't finish. In the 2nd case, your PCs CPU will be near 100% (or 50%, for dual core, 25% for quad core, etc). One of the processors will be at 100%. There is some work going on with not null constraints, but it shouldn't take long even with 11K constraints. I have a 10g database with 20K constraints (half PK and half not null) and I can extract all of them for comparison in just a few minutes. Of course there could be other factors that would make yours slow. Anyway, see if you can narrow down what is happening and let me know.
↧