Installation

Toad supports installation on Citrix servers. Toad must be installed on the Citrix server by the Citrix administrator. Users then connect to this instance through their Citrix logon. Citrix support is enabled with the appropriate installation option - Citrix/Terminal Server on the Select Installation Type dialog. Toad requires write access to the server registry during installation and read access during run-time to achieve Citrix support. Full procedures for installing Toad on a Citrix server are located in the Getting Started Guide.

First, join the Yahoo! ToadBeta list. Send an email to: toadbeta [dash] subscribe [at] yahoogroups [dot] com. Next, go to http://www.toadsoft.com/beta.html to read the beta usage agreement, then download the beta installer using the link at the bottom of the page. Run the MSI installer, but do not install to your current Toad commercial folder. Now download the latest beta update and unzip into the beta folder you created in the previous step. New beta builds are announced in the ToadBeta Yahoo! group, where any issues encountered in the beta should be addressed. Do not contact Quest Support with beta issues.

Toad for Oracle now uses the Quest Installer to handle installation and upgrades. This allows many Quest product installations to be managed from one location.

There are some differences from the old Toad installers, however. The following will give you some information that may make installing or upgrading Toad easier.

• The INSTALL LOCATION screen defines the BASE directory for all products to be installed: Quest Installer, Toad, Knowledge Xpert, SQL Optimizer and so on.

• The PRODUCT SELECTION screen places the current installation of Toad.exe. If you do not change it, Toad for Oracle will automatically be placed in a folder called Toad for Oracle beneath the BASE (install location) directory OR IF THERE IS ANOTHER INSTALLATION OF TOAD FOR ORACLE UNDER THAT ROOT DIRECTORY, THAT INSTANCE WILL BE UPGRADED. This can be an issue if you are also running the beta version of Toad for Oracle, as the Installer may find the beta install and upgrade that.

1. On the Product Selection screen, expand the Toad for Oracle section.
2. Near the end of this section, click on INSTALLATION DIRECTORY.
3. Set the installation directory for the location where you want to install Toad.

Download the installation executable from Quest's website. You will need to enter your license key there. If you have a network install, and you want to upgrade to the latest version of TOAD, you should run the TOAD installation script to overwrite the installation to the server, then run the TOAD installation script again to overwrite the installation to the client. Unfortunately, the client must be upgraded in many cases because there are new configuration files or a new version of Formatter Plus. Upgrading the server and not upgrading the client is a common error. If a new version of Formatter Plus is needed for the new version of TOAD, and the client has not been upgraded, then when you launch TOAD, you may get an error such as 'Installed Formatter does not support XML version 12.' and the procedure editor will not compile.

TOAD is indicating that it cannot find a SQL*Net or Net8 installation, which is required in order for TOAD to connect to a database. Make sure \bin folder is in PATH, and that some version of oraxy.dll, e.g., ora71.dll, ora72.dll, etc. exists in that folder or elsewhere in the PATH. For Oracle8, the OCI dll is named OraClient8.dll. For Oracle9, the OCI dll is named OraClient9.dll.

This is likely due to the fact that you do have a permanent key, and you may have used a trial key or two in the past. TOAD keeps a record of this, and thinks that you are attempting to use it as a trial for another 30 day period, and will not allow this. It will not accept the key, and result in the message that you are receiving. To obtain a new override trial license key that will eliminate the "invalid key" message, you will need to contact the nearest Quest Software Sales Office and ask for your Account Representative.

From the Toad email group, answer supplied by Michael Staszewski :

• Close Toad (all versions).
• Copy the file PLSQLSUB.TXT from 8.6 into your user files folder.
• Open Toad.ini and remove the line AutoReplace=
• Start Toad 9.0.1.

From the Toad email group, answer supplied by Henry :

1. On the older computer or installation, locate the connections.ini file. In Toad 8.5 and greater this file is located in the C:\Program Files\Quest Software\Toad for Oracle\User Files directory. In Toad 8.0 and below this file is located in the C:\Program Files\Quest Software\Toad directory.
2. On the new computer or installation, exit out of Toad.
3. Copy the connections.ini from the 8.5 location given in step 1 to the corresponding 9.1 directory. Replace the existing connections.ini if necessary.
4. Launch Toad 9.1 and the old connections and passwords will be displayed at the login prompt.

Note: If upgrading to version 9.0.1 and the passwords have not been transferred over, ensure that the SAVEPASSWORD entry in the connections.ini of the older version is issued to a value of one and not zero prior to copying.

From a question on the Toad email group, answer supplied by Matt Wilkins :

As the developer of the new Toad for Oracle installer MSI, I will explain.

One of the standard features of all MSIs is that each unique MSI installer has a higher level of self-awareness. Have you ever noticed the "maintenance" screen you'll get when you attempt to install a program over itself without first removing it? The choices are usually "Modify", "Repair" or "Remove". This is because the MSI looks immediately at the registry to check its install state. Our previous installers were done in WiseScript, and they did not care if there were concurrent installs; you could simply install it again and the registry would be overwritten. Microsoft wants their Windows installers to clean up after themselves more efficiently, hence concurrent installs become problematic.

Our Toad installer for network client and server demands that the installer be run twice– once for the server and once again for the client. This was never a problem in the past, but with MSI, the installer detects a previous install and thus launches the maint screen. The way around this was to create separate MSIs that were called by a bootstrapping EXE developed in WiseScript. This is the reason for the increased executable size. The parent EXE calls one of four MSIs according to user input, extracts the MSI locally and then runs it. We also need a bootstrapper in order to avoid running nested MSIs, a Quest (and presumably Microsoft) no-no.

Note : The following has been slightly paraphrased by Norm.

This query was raised on the lists about problems running TOAD after installing on Vista :

I have installed Toad 9.5.0.31 on Windows Vista. When I double click and try to run Toad it gives me an error and aborts due to some unknown reason. However when I run Toad by right click [in Explorer] and selecting "Run as administrator", it runs fine without problems. I would like to know reason and solution of this problem.

Brad from Quest replied with the explanation and the workaround :

You need to turn off User Account Control (UAC), you know, those annoying messages that are like :

• Are you sure you want to do this?
• Are you really sure?
• Are you sure that you are sure?
• Have you got permission to be sure?
• And so on and on and on ....

Apparently there is more to UAC than just the annoying confirmations. We noticed that files that Toad writes out were being redirected to a local user profile. It is this "data redirection" as they call it that made Toad inoperable in this environment. Specifically, when you install Toad, it installs a file called lexlib.new and when Toad is run, it renames this file to lexlib.lxl. Since this UAC does not allow normal users write access to program files, Toad could not rename this file, and hence the errors.

Solution 1.

To run Toad as a normal user, turn off UAC.

Solution 2.

If you don't have permission to turn off UAC then you need to copy the 'redirected' files from your local profile back to where they should have been in the first place. For example, in the case of the lexlib.lxl error, you must copy this file from your local profile (where vista redirects your data) to your user files folder under the location you have installed Toad..

A question on the list from Pete Jones :

Hello Toadies, I'd appreciate some insight into the "CodeSite 3.0.1 Client Tools, Raize Software Developer Tools" which evidently comes with Toad 9.5. Our software security folks don't have it on their list of approved applications and either want it removed or want it approved. What is its purpose? Can it be removed without compromising TOAD? Thanks!

And the reply from Michael Turner at Quest went as follows :

Hi Pete,

By way of introduction, I am the development team lead responsible for "Quest Installer," the application used to bundle Toad and the other products in the Toad 9.5 & 9.6 releases.

Codesite is a third-party utility used to log the options, progress and any errors during the installation process. This information can then be used by Quest's support area to assist with any installation issues you may have.

You may remove Codesite through Control Panel|Add or Remove programs and selecting the Codesite entry.

Quest Installer will continue to run without CodeSite, but installation logging will be minimal. As Codesite is installed as part of the Quest Installer installation, Codesite will not be reinstalled unless you uninstall/reinstall or update Quest Installer itself.

Regards
Michael

One possible answer is an invalid attempt to upgrade - it's a common problem where people get read violations after upgrades when they do not follow standard upgrade procedure. For example unzipping a beta into a production directory to get a free upgrade will cause a read error. Likewise, trying to use a trial download install to upgrade results in a similar error. Please verify that you went to support.quest.com, logged into your technical support account, that you were current on your maintenance (i.e. paid for upgrades), and downloaded a commercial version of the software install.

Occasionally, uninstalling Toad for Oracle leaves remnant installation files or registry entries, and reinstalling becomes problematic. Often, the solution is to run a Windows Installer Cleanup Utility available for free from Microsoft. Please see this site for more info:

http://support.microsoft.com/kb/290301

On the Toad list, a poster asked what is the best way to save or import my previous settings into a new version of Toad.

Further information confirmed that the user was about to get a new PC and was to install Toad 10 and wished to import his settings from Toad 9.

Toad supports importing settings from previous versions only if the previous version is 2 or less releases ago.

John "it's full of stars!" Bowman replied:

If they have pre-installed Toad 10, but not run it yet, you will automatically be prompted to copy your user files from a previous version. Since it's a new machine install, you won't see any versions listed in the drop-down box, but you can click on the ellipsis button next to the drop-down to select a folder from which to copy your previous user files. If your current version of Toad is 9.7 or later, these files should be located in:

• Windows XP and earlier: c:\Documents and Settings\<username>\Application Data\Quest Software\Toad for Oracle\9.7

• Windows Vista and later: c:\Users\<username>\AppData\Roaming\QuestSoftware\Toad for Oracle\9.7

You can copy this folder to anywhere on the network, or on a USB thumb drive. Then when the Initial Setup Wizard pops up, use the ellipsis button to select this folder. If your network admins have already run and configured Toad for Oracle, simply rename the following folder:

• Windows XP and earlier: c:\Documents and Settings\<username>\Application Data\Quest Software\Toad for Oracle\<version>

• Windows Vista and later: c:\Users\<username>\AppData\Roaming\QuestSoftware\Toad for Oracle\<version>

and Toad will consider itself a new install, recreate the folder, and prompt you to copy over your previous user files.