Re: Toad For Oracle Download
Morris Betoch
I am on a windows 10 64 bit machine. I had to reboot my laptop because our VPN would not connect. After that was resolved, Toad won't open. I get no splash screen, nothing. I can see it in task manager, but that is all. It thinks that it is running, but nothing appears on my screen. No errors or anything else. I have rebooted my laptop, shut it down completely and restarted it. I have also uninstalled Toad and reinstalled it to no avail.
Kill Toad if it's still running and add DEBUG=1 to the [SETTINGS] section of Toad.ini. Search for DEBUG= first to be sure you do not include it twice. Its default location is %APPDATA%\Quest Software\Toad for Oracle\16.2\User Files\Toad.ini. Start Toad, give it 30 secs or so, and then kill it from Task Manager. See if a ToadDebug.log file was generated in %APPDATA%\Quest Software\Toad for Oracle\16.2\User Files\logs. If it was then please share it here.
I have done as you suggested, but it won't create a log file. There was no logs folder so I created one, but it just won't create a log file. I also tried it with 16.1 which also will not start and it too will not create a log file. I am considering uninstall ALL versions of toad that are on my laptop and removing all Quest Software data and folders and performing a clean install. What do you think?
Before uninstall/reinstall I'd try renaming %APPDATA%\Quest Software\Toad for Oracle\16.2 with Toad closed and trying again. If that doesn't work you can surely try uninstall/reinstall, but I don't have high hopes that it'll change anything. Were any Windows updates applied at your reboot? Does your company use any software that looks for malware that may have had its definitions updated?
There were no updates during the reboot or the cold startup, which I also did. As far as malware software, I will have to find out. I will do the rename of the 16.2 folder and let you know what happens.
I have checked and no definition updates for the malware. I did as you suggested and renamed the 16.2 folder while Toad was closed and even moved it to the TEMP folder. I then restarted TOAD to no avail. I assume that it was supposed to create a 16.2 folder again, but it did not and Toad remains in the background processes section of task manager and never comes to the Apps section like it normally does.
Hi John, that did not work for me. I think that I am going to totally uninstall all things Toad from my laptop, deleting everything that is related to Toad and reinstall the latest version to see what happens.
I have no other suggestions at this time. The existence of Toad.exe in Task Manage and the fact that Toad did not produce any log files means it is locking up extremely early in the startup logic. I'll put a breakpoint in and see if I can narrow down what's occurring between app start and the first log message that is produced.
We add a log comment on the first line of Toad's source. This would be what most would consider to the first line of the application although there is still some initialization code that gets executed before this. That initialization code is practically impossible to track down all of it and in what order it is executed. This code is usually quite small and used to initialize global objects or apply application wide settings that must be done immediately upon startup.
Given that Toad was working fine for you and then abruptly stopped after your reboot and that you have already uninstalled/reinstalled Toad once I don't think trying that again will change anything. This is feeling like an environment change on your PC, but I am unsure of what it is.
Well, I tried to do as you suggested, but Toad would not start from the command prompt at all. I started it directly from the file explorer by right clicking on Toad.exe and running as administrator. I then went to the windows event log, but nothing jumps out at me. Of course, like you, I am not sure what I am looking for either.
mstaszew, Well, here is what I did to resolve the situation. I uninstalled everything Quest/Toad related from my laptop and then removed any residual directories. I rebooted and then installed Toad version 14.2. When 14.2 came up, it prompted me to upgrade to 16.2. I chanced it and allowed it to upgrade and Toad 16.2 now works. Now I just have to put back all of my logins, but all is well. Thanks for your help today with this issue.
PL/SQL Developer from Presented between a choice between Toad and PL/SQL developer, about half the developers prefer PL/SQL developer. I have to admit the code completion in PL/SQL developer is much better, but I still prefer Toad for the DBMS management functionality.
I've used Squirrel-SQL (which is a Java/JDBC based program and will work with any OS or database that provides a driver) and the database development tools for Eclipse (Eclipse-DTP). Both are certainly sufficient for light database work. Both are free and open-source.
I'm surprised that nobody has mentioned DbVisualizer yet. Our company has been using it for a few years and everybody seems happy with it. It's powerful, runs on multiple platforms (Java-based) and supports different database systems (Oracle, DB2, MS Access etc). It has a free version; a commercial version is available if you need more features.
Simple answer:
Use Textpad or another text editor.
Explanation:
For me PL/SQL development is a process that has evolved over time. I've tried to apply continuous improvement to SQL development and it has worked out wonderfully for me. (for more on continuous improvement/Kaizen see link text)
I found PL/SQL IDE tools to be unstable.
I've had several crashes of Quest Software's TOAD as well as Quest Software's SQL Navigator (I've been using it since Version 3).
I lost work.
I tried other IDE PL/SQL tools.
These tools also crashed.
I lost work again.
I got frustrated.
I do not trust PL/SQL software development to any of the PL/SQL IDE tools out there.
Here are my PL/SQL coding core practices:
1. Export code using Quest Software TOAD
2. Use a Cygwin bash script to move files into the appropriate directories
3. Compare versions via BeyondCompare (if needed)
4. Check code out of WinCVS / CVSNT (if needed)
5. Edit using TextPad
6. Compare versions via BeyondCompare (if needed)
7. Check code in to WinCVS / CVSNT (if needed)
8. Use a Cygwin bash script to create a master changes file.
9. Import code back using Quest Software TOAD
An even more lengthy explanation:
I use Quest Software TOAD to export all PL/SQL and table DDL code to the filesystem.
In the Database menu -> Export -> Source Code
In the Database menu -> Export -> Table Scripts
This gets me individual files for each database object.
I move these files (Cygwin bash script) in directories
based on the file extensions.
*.prc files in /procedures
*.fnc files in /functions
*.pks and *.pkb files in /proceudres
*.trg files in /triggers
*.vw files in /views
*.sql files in /table_scripts
These files are initially checked into CVS.
(I use WinCVS/CVSNT server side)
I Beyond Compare each file version exported by TOAD
with the version already in CVS.
I ensure that the CVS sql repository is up to date.
In other words I need to have a good starting baseline.
I then use TextPad to edit the PL/SQL code.
link text
I pre-configure my Textpad with SQL syntax files
to make it easier on the eyes
link text
After editing, I Beyond Compare each edited
file version exported with the version
in WinCVS.
Luckily, WinCVS allows you to use an external
diff (Beyond Compare) which comes in very handy.
I load the new/changed code via TOAD to a test schema.
In the SQL Editor menu -> Load and Execute a Script File
I test the code out. (do some debug runs)
If the code tests out, I check the code into CVS.
At the end, I use Cygwin bash (and a bash script I've written) to create a master changes file. This master changes file contains all of the changes that need to be applied to bring the live schema up to date. This saves me a lot of time.
I then load the new/changed code via TOAD to a live schema. In the SQL Editor menu -> Load and Execute a Script File. That's about it. Software engineering is about process, versioning (CVS) and automating builds (bash script).
The biggest lesson out of all this (that have made me 10 times more productive) was switching from DB-based PL/SQL IDEs to simple ASCII text files. KIS in action.
If a copy your code resides in an ASCII file you avoid:
- mucking up the DB
- locking up DB objects
- iffy DB based revision control tools (if any)
- iffy DB diff tools (if any)
- losing code due to IDE crashes
- losing code due to DB crashes / shutdowns
- losing code due to concurrent editing (this can happen if two or more PL/SQL developers edit the same procedure)
Instead if you handle all PL/SQL code in filesystem ASCII files you have
- your choice of text editors (TextPad,notepad++,vi,etc)
- your choice of revision control systems (CVS,svn)
- your choice of text filtering/handling/scripting systems (I like Cygwin bash)
- your choice of diff tools (Beyond Compare,WinDiff,diff)
- your choice of DB tools (I can use TOAD, SQL Navigator) for importing and exporting the PL/SQL code to files.
I wanted a version history of all code changes.
I wanted to get everyone working together and prevent developers from stepping on each other's toes.
I wanted the freedom to choose my tools.
The side effect of this is that I handle all of the DB code in the filesystem during rapid development.
Just my 2 cents.
I would also recommend Oracle's SQL Developer, however I've found WinSQL to be quite good as well. SQL Developer is free and WinSQL has a community version that is quite robust, and works well against other platforms too (I also use it for working with Netezza).
59fb9ae87f