Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Toad for Oracle 17.0 - Installation Guide

Install Toad silently from the command line

A silent installation enables you to deploy Toad and other Edition products to multiple machines. To install silently, you obtain the individual product installers (.msi) for your Edition file and then execute command-line parameters to install one product at a time. You can change the parameters to fit your environment or standards, such as installing to a different directory.

These instructions are for performing a silent installation of Toad and, optionally, installing licenses on the target computers.

Note: Toad is installed per machine and will be available to all users on that machine.

Obtain product installers

Toad for Oracle with subscription licensing

Run the silent installation

From the Windows command prompt, run the Toad for Oracle EXE file. The basic command to perform a silent installation is:

ToadforOracle_Subscription_##.##.##.####_x64_En.exe /install /qn

To perform a silent installation of a particular product execute:

ToadforOracle_Subscription_##.##.##.####_x64_En.exe /install /qn /p:101

For help on product IDs and additional command line options, including MSI extraction, execute:

ToadforOracle_Subscription_##.##.##.####_x64_En.exe /?

Toad for Oracle with offline licensing

  1. Go to https://support.quest.com/download-product-select.

  2. Search for Toad for Oracle.

  3. Under MSI Installers (Special Installations Only), download the Toad Editions zip file.

  4. Unzip the download file.

Run the silent installation

From the Windows command prompt, run the Toad for Oracle MSI file. The basic command to perform a silent installation is:

msiexec /i "full path to MSI file"

Example

msiexec /i " C:\Users\jdoe\Downloads\ToadForOracle_12.10.0.111_x86_En.msi"

See Command-line options for additional options.

To perform a silent installation of other products that are provided with your Toad Edition, see the installation guide for that product on https://support.quest.com/technical-documentation.

Note: Toad is installed per machine and will be available to all users on that machine.

Install licenses

Applies to legacy Toad for Oracle with offline license keys.

To install licenses on the target computers, you do the following:

  • Create a Questkey.reg text file to specify each license key.
  • Send the file to the target PC and import it to the Registry there.

To create the Questkey.reg file

Create the Questkey.reg file in a text editor. The following is a template:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\{08439167-4CA5-48E9-A810-A3A7C0B80B06}]

[HKEY_CURRENT_USER\Software\{08439167-4CA5-48E9-A810-A3A7C0B80B06}\Local]

[HKEY_CURRENT_USER\Software\{08439167-4CA5-48E9-A810-A3A7C0B80B06}\Local\REPLACE_WITH_KEY]
"SiteMessage"="REPLACE_WITH_SITEMESSAGE"
"ProductName"="REPLACE_WITH_PRODUCTNAME"
"ProductVersion"="REPLACE_WITH_PRODUCTVERSION"

Follow these steps to configure the file:

  1. Do not change the first two HKEY_CURRENT_USER lines. They are the key entries.
  2. Replace the "REPLACE_WITH_(KEY | SITEMESSAGE | PRODUCTNAME | PRODUCTVERSION)" text with the relevant information supplied with your license.

  3. Add any additional licenses as required in the same file by replicating the last four lines and then applying the correct information.

  4. Save the file.

To apply the file on the target computer

  1. Transfer the Questkey.reg file to the target PC.
  2. Import the file to the Registry on the target PC with the following command in the Windows command prompt:

    C:\> reg import Questkey.reg

When the user runs Toad and any product installed with Toad, the software validates the license and removes the entries from the Registry.

Toad (and any other product) is ready for use when the license is validated.

Command-line options

You can use the following command-line parameters when you silently install Toad:

Option Parameter Description
/l Package|ProductCode Installs or configures the product.
/f

[p|o|e|d|c|a|u|m|s|v]

Package|ProductCode

Repairs the product. This option ignores any property values entered in the command-line. The default argument list for this option is 'omus.' The following options are available:

  • p—Reinstalls only if a file is missing.
  • o—Reinstalls if a file is missing or an older version is installed.
  • e—Reinstalls if a file is missing or an equal or older version is installed.
  • d—Reinstalls if a file is missing or a different version is installed.
  • c—Reinstalls if a file is missing or the stored checksum does not match the calculated value. This option only repairs files that have msidbFileAttributesChecksum in the Attributes column of the File table.
  • a—Forces all files to be reinstalled.
  • u—Rewrites all required, user-specific registry entries.
  • m—Rewrites all required, computer-specific registry entries.
  • s—Overwrites all existing shortcuts.
  • v—Runs from source and re-caches the local package. Do not use this option for the initial installation of the product or feature.

/a

Package

Installs the product on the network.

/x

Package/ProductCode

Uninstalls the product.

/l

[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*]

Logfile

Writes logging information to a logfile in the specified path. The path to the logfile location must already exist. The installer does not create the directory structure for the logfile. Flags indicate which information to log. If no flags are set, the default is 'iwearmo.' The following options are available:

  • i—Status messages.
  • w—Nonfatal warnings.
  • e—All error messages.
  • a—Start up of actions.
  • r—Action-specific records.
  • u—User requests.
  • c—Initial UI parameters.
  • m—Out-of-memory or fatal exit information.
  • o—Out-of-disk-space messages.
  • p—Terminal properties.
  • v—Verbose output.
  • x—Extra debugging information. Only available on Windows Server 2003.
  • +—Append to existing file.
  • !—Flush each line to the log.
  • "*"—Log all information except for the v and x options. To include the v and x options, enter "/l*vx".

/q

n|b|r|f

Sets the user interface level. Review the following options:

  • q, qn—No UI
  • qb—Basic UI. Use qb! to hide the Cancel button.
  • qr—Reduced UI with no modal dialog box displayed at the end of the installation.
  • qf—Full UI and any authored FatalError, UserExit, or Exit modal dialog boxes at the end.
  • qn+—No UI except for a modal dialog box displayed at the end.
  • qb+—Basic UI with a modal dialog box displayed at the end. The modal box does not display if you cancel the installation. Use qb+! or qb!+ to hide the Cancel button.
  • qb- —Basic UI with no modal dialog boxes. Note that /qb+- is not a supported UI level. Use qb-! or qb!- to hide the Cancel button.

Note: The ! option is available with Windows Installer 2.0 and works only with basic UI. It is not valid with the full UI.

RESTRICTIONS

p Prevents users from saving their connection password by disabling the Save password field in the Database Login window. For example: RESTRICTIONS=p

i

Prevents users from accessing the Internet via Toad by disabling all Internet access in Toad. This can be combined with the 'p' parameter; for example: RESTRICTIONS=p,i

Install Toad as Read-only

A Read-only version of Toad prevents the user from making any changes to the database, regardless of their Oracle privileges. In order to get a Toad installation to be Read Only, you can do so by using a parameter when installing the "normal" msi installer. This will make Toad read-only for all users on that machine for that version. You must have the appropriate license for a read-only version of Toad.

Note: 

  • Starting in v13.2, there is no longer a separate installer for the Read Only version.

  • Toad is installed per machine, and will be available to all users on that machine.

To install Toad for Oracle Read-Only

  1. Obtain the license key and site message text for your installation.
  2. Go to https://support.quest.com/download-product-select.
  3. Search for Toad for Oracle.
  4. Download the appropriate Toad Edition installer.
  5. Toad can be installed in Read-Only mode by using either of the following two methods:

    1. If launching the installer via the msiexec.exe command, include "READONLY=1" in the command line. For example: msiexec /i ToadforOracle_GA_14.0.75.662_x64_En.msi READONLY=1

    2. Adding a "Read-Only" DWORD entry with a value of 1 to the following Registry location: HKEY_LOCAL_MACHINE\Software\Quest Software\Toad for Oracle\<version> (where in this case, <version> = "14.0")

  6. Review the license terms, select I accept these terms, then click Next.
  7. If your license key is not shown, click Add to enter your license key and site message, then click Next.
  8. Click Install.

Post-installation tasks

Apply license keys to bundled products

Applies to legacy Toad for Oracle with offline license keys.

All products within a Toad Edition share a licensing key. For best results, when you have completed installation of your products, run Toad for Oracle first and enter the license key when prompted. This ensures that all installed products reflect the appropriate license key.

If you have previously licensed versions of Toad for Oracle or the other products in this Edition, your old license keys will continue to work. If you are upgrading to a different Edition and have been issued a new key, use the following procedure to apply it.

To add or upgrade an existing license

  1. Launch Toad for Oracle.
  2. Select Help | Licensing, then enter your new license key. Any new features are enabled automatically, and any additional Toad products are licensed using this key.

Cumulative licensing

You can add multiple licenses, including those for add-on packages like Sensitive Data Protection, to Toad. Toad will use the licenses providing the highest degree of features.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation