Oracle Toad For Mac
Colleen Bramham
Are you saying that you have multiple tnsnames.ora files? If you are using a TNS_ADMIN variable, then point it to a folder that is not part of your existing Oracle clients (maybe something like c:\Oracle\tnsadmin), and put your tnsnames.ora in that folder. The benefit of the TNS_ADMIN variable is so that you don't need a tnsnames.ora for every oracle client.
That said, I just tried pointing my tns_admin variable to the network\admin folder of one of my clients, and it worked fine for all of my installed clients, so I'm not sure why it isn't working for you.
Interesting that this has nothing with Toad. In mine 5 years extensive work with Toad (all Oracle versions except 12c) Toad have never true problem with TNS names.
So for any problem like this, first try with plain SQL*Plus connection. If works then it is really Toad problem.
:-()
@bricot_750
Your last answer (which you mark as verified) was:
I happened to point the TNS_ADMIN back to what I thought it was originally (second paragraph in my post) and it is working now.
I really do like to understand how that was related to Toad. Please spent some additional time to help us understand the problem.
Quest should really put some effort into a kill function so that processes that are stopped don't crash the entire system. I've lost track of how many times I've needed to kill a statement that then would not release and required shut-down through task manager. The document save helps, but it still loses work sometimes and when you have a lot of windows open you can lose your place when it all comes crashing down.
Which Toad version are you on? I fixed a bug like this in Toad version 15.0. Search for "cancel" on this page for details. There are 2 bugs on that page that may be relevant. If your case is different, please give me whatever details you can about how to reproduce it and I'll do what I can to fix it.
In the meantime, you might want to try using the threaded query option. That way your query executions aren't blocked by a popup cancel button. Instead you can just go to a different editor tab and keep working. To turn this on, go to Options -> Oracle -> Transaction. Check "Execute queries in threads".
Hi, I'm currently on 16.2. The issue for me is pretty much same. Some queries simply will not stop once started and Toad will not release focus from the error message forcing me to kill Toad altogether if it chooses to never release. Sometimes it will quit if I walk away and come back later, but other times it's hung.
Why not allow that to become a background process rather than lock everything up? It's not the only client I work with, but I believe it's the only one that takes this approach. The only resolve is that sometimes I use Script Runner, but I don't always want my output because the grid isn't the same as the Toad editor. Also when you're coding you're not always thinking and you make the mistake of executing something that you wish you hadn't and there's no turning back with Toad sometimes.
I have a dissimilar issue with executing pl/sql scripts. They run for hours only to find out that they stopped processing, but Toad is still showing a running status. I started putting timestamps on my records so I could measure the time between inserts to see if/when the process would stop. I thought perhaps it was a system policy, but if that was the case why wouldn't Toad respond in kind to an idle/terminated process?
Which Oracle client and server are you using? And can you tell me anything about the SQL that might help me reproduce it? I've tried to come up with SQL that just won't cancel w/o success. I've tried cartesian joins, "order by" on tables with millions of rows...everything I can think of. For me, it always cancels quickly.
I could make the dialog go away, but whatever is waiting would still be waiting. So I don't think you'd be able to run any other queries, and I think the "hang" would just happen at some other step in the shutdown. I can't just move the hanging part to a thread. But there's room for improvement here. I could probably get you to a point were you could at least save everything before having to kill Toad. That's why I suggested "execute queries in threads" though. That would let you save everything.
So, in this case, they are just long-running procedures or just very long scripts with a lot of insert statements, or what? And, do you think that the session becomes disconnected, or there is some oracle error, or what? (OK, I know I just ended two sentences that way. Just trying to toss out ideas and realizing they are probably wrong.)
I'm using Toad for Oracle to connect over a VPN to Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.11.0.0.0. The queries vary, but I can tell you the larger the tables and joins the more likely Toad will freeze if I need to kill it. I also use SQL Developer sometimes, but I haven't encountered issues with stopping queries that I can recall.
If I use Toad Script Runner it's not a problem because I can kill that. The window often freezes and I have to force it to close, but at least it runs as a separate process and doesn't tie up the main editor. That's generally how I avoid the problem, but sometimes I want to run something in the Toad editor.
The pl/sql runs long because they are often cursors processing over a large number of records and in some cases I'm hitting production tables so things can slow down. The tables can be in the hundreds of millions to billions at times. I have brought the matter up to our DBAs before, but haven't pursued further discussion about it. It would require monitoring the process so I would have to coordinate with them to see what's happening on the server. Toad however seems to think it's still running even when no records have been processed for over an hour or more. There's no error which is why the whole thing is a mystery.
I use to think maybe it was just taking a long time to complete, but when I monitor the transactions it looks dead so I usually have to kill and start it again. If you have any other suggestions I'm all ears. Thanks for the info.
Same problem here. I do not think VPN would be the issue. This started with recent versions of Toad. I am wondering if there is an option to download the previous versions of Toad which are more stable.
The latest Oracle client isn't necessarily the best. For example - with Oracle client version 19c and newer - client leaks memory when you select from a table with LOBs. You can see this with any version of Toad. Change to an 18c or 12cR2 client and there is no memory leak.
Yes, you are right. It was bad since we started moving to Client version 19 and above. but it was not this bad. now it is un-usable. Toad freezes when I double click, format or even run a script. and it stays frozen for like 2-5 mins every time. I feel SQL Developer does a better job. Personally, I just love the formatter tool in Toad and that keeps me on toad. I have other team members who are not very comfortable with SQL Developer and they keep asking for the help when this turns annoying
If we know something is going to take a long time, we usually do warn you, or give you the opportunity to cancel it. What you found is either a bug or some long running query. How can we warn you if you are about to experience a bug? No software does that.
Click "Try to restore the program". It actually works. Toad will realize that the connection is lost, it will come out of the "Not Responding" state, and Toad won't close. Then you can click Session -> Test/Reconnect to reconnect to the database.
Hi I am using Toad 13.1.0.78 and I have managed to put a break point on one of my triggers. I have activated the toggle compiling with debug and have placed a breakpoint right on the begin. My question is how do i initiate to step through this through a DML command like an update statement. It seems that when I open a new SQL editior and create the update statement, it does not hit the breakpoint at all even though I know the trigger is processing and i verified this by using dbms_output stmnts.
It sounds like you're 90% of the way there. You'll need to wrap your DML statement in a "dummy" procedure to allow it to be compiled with debug info. This'll allow you start stepping into the code. I have also setup a trigger that fires after I insert into my orders table.
Mike, thanks for the quick reply... I have done that already and I set a brekpoint on my UPDATE statement. Once I hit execute PL/SQL with debugger, it prompts me to the Set Parameters and execute, being I have no parameters, I hit execute and it never reaches or stops at the breakpoint. It does the update and toad just prompts a message indicating execution has terminated.
Can you confirm that the procedure is being compiled with debug correctly? You can quickly look in the Schema Browser on the left hand side to see what icon you've got. If the Schema Browser is already open I'd recommand refreshing the LHS as well just to grab the last state.
You'll want to make sure you have the following privileges to use the DBMS debugger. I suspect you're missing the DEBUG ANY PROCEDURE though.
DEBUG CONNECT SESSION
DEBUG ANY PROCEDURE
EXECUTE ON DBMS_DEBUG
I have asked the dba to grant this for me. In the meantime they have given me an account to use that has the debug with compile and it is now able to hit my initial breakpoint. Is there a play button so that it can continue to execute until the next breakpoint?
As suggested (more or less) Toad could be on the screen. Be sure it is the
active program. Hit Alt-Space, M meaningMove, use one of the cursor keys and
then the mouse and the screen will probably appear.
... information, when I click on connect, toad windows disappear. I see Toad
running in tast bar, but can not resize/maximize its windows so that it
comes up in front of me .. Any ideas?
Possibly!
Right click on the Toad button in the task bar - what options are
enabled? If you see Restore and Minimise, then Toad is currently
maximised - possibly as Phyllis mentions, off screen. Click Restore.