Toad InstallGuide

Toad for Data Analysts
Installation Guide
2.6
2010 Quest Software, Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchasers personal use without the written permission of Quest Software, Inc. The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com email: legal@quest.com Refer to our web site for regional and international office information. Trademarks Quest, Quest Software, the Quest Software logo, Benchmark Factory, LiteSpeed, Spotlight, SQL LiteSpeed, SQLab, Toad, T.O.A.D., Toad World, vOptimizer Pro, vSpotlight, and vToad are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
Toad for Data Analysts 2.6 Installation Guide February 2010
Table of Contents
Installation System Requirements Install Toad Read-Only Installation Install Toad Silently Install Toad on Citrix Systems Upgrade Toad Register Toad Uninstall Toad Configuration Configure Toad Layouts Configure Connections Troubleshoot Database Issues Configure Version Control Appendix: Contact Quest Contact Quest Support Contact Quest Software About Quest Software Index 1 1 6 7 8 15 16 18 18 19 19 22 48 64 74 74 74 74 75
1
Installation
System Requirements
Client Requirements
Ensure that the client computer meets the following minimum requirements: Component Platform Hard Disk Space Memory Requirement 1 GHz minimum 800 MB to install Toad 239 MB to run Toad 512 MB of RAM minimum, 1 GB recommended Note:The memory required may vary based on the following:
l l l l
Applications that are running on your system when using Toad Size and complexity of the database Amount of database activity Number of concurrent users accessing the database
Operating System
Windows Server 2003 Windows XP Professional (32-bit) Windows Vista (32-bit or 64-bit) Windows Server 2008 (32-bit or 64-bit) Windows 7 (32-bit) Important (SQLServer only):Toad uses the Microsoft Distributed Transaction Coordinator (DTC) when opening a SQL file to get FullText Search status, but DTC is disabled by default on Windows Vista and Windows Server 2008. If you are using either operating system, ensure that Network DTC access is enabled on the Toad client. See http://technet.microsoft.com/en-us/library/cc753510(WS.10).aspx for more information about enabling DTC access.
Toad for Data Analysts Installation Guide Installation
Component .NET Framework
Requirement Microsoft .NET Framework 3.5 (Service Pack 1) Note:The following conditions apply:
l l
The .NET Framework Client Profile is not supported. To run Toad, the .NET security policy must be set to unrestricted. See "User Requirements and Restrictions for Running Toad" (page 5) for more information.
Additional Requirements
Web Browser Microsoft Internet Explorer 6.0 or later Existing DB2 Client Support (DB2 native provider only) Toad installs a DB2 9.7 client as part of the installation process. The DB2 9.7 client can co-exist with an existing DB2 8 client; however, it is incompatible with a DB2 7 client. If a DB2 7 client is already installed on the system, the Toad installation stops and cannot complete. You must first upgrade to the DB2 8 client. Then restart the Toad installation to avoid losing functionality in some DB2 native tools. Oracle Client Toad can connect to Oracle using Direct Connect (no need for an Oracle Client) or can connect using an Oracle Client or Oracle Instant Client. However, if you want to use LDAP, you must install an Oracle Client. See "Configure Connections" (page 22) for more information.Toad supports 9i or later Oracle Clients and Oracle Instant Clients. See "Create Oracle Connections" (page 22) for more information about configuring an Oracle Instant Client to work with Toad.
Server Requirements
Ensure that the server meets the following minimum requirements: Component Operating System Requirement Oracle Native Database Provider
l l l l l l l
IBM AIX 5.1, 5.2, 5.3 HP-UX 11i 1.5, 2 (32-bit or 64-bit) Red Hat Enterprise Linux AS release 3 and 4 (32-bit or 64-bit) Solaris 7, 8, 9, 10 (32-bit or 64-bit) SuSE 7, 8, 9 Windows 2003 (32-bit or 64-bit) Windows XP
Component
Requirement SQL Server Native Database Provider

l l l l l l l l
Windows Server 2000 Service Pack 4 or later Windows 2000 Professional Edition Service Pack 4 or later Windows XP (32-bit with Service Pack 2 or later and 64-bit) Windows Server 2003 (32-bit or 64-bit) Service Pack 1 or later Windows Vista (32-bit or 64-bit) Windows Server 2008 (32-bit or 64-bit) Windows Server 2008 R2 (64-bit) Windows 7 (32-bit or 64-bit) z/OS (V1R6 Base Services [5694-A01] or later) IBM AIX 5.1, 5.2, 5.3, 6.1 HP-UX 11i 1.5, 2 (32-bit or 64-bit) Red Hat Enterprise Linux AS release 3 and 4 (32-bit or 64-bit) Solaris 7, 8, 9, 10 (32-bit or 64-bit) SuSE 7, 8, 9 Windows 2000, 2003,(including 64-bit), 2008, XP, Vista, Windows 7 Windows 2000 Service Pack 4 or later Windows 2003 Windows XP (32-bit or 64-bit) Windows Vista (32-bit or 64-bit)
DB2 for z/OS Native Database Provider

l
DB2 for LUW Native Database Provider

l l l l l l
MySQL Native Database Provider

l l l l
Component Native Database Support
Requirement Toad supports the following databases:

l l
Oracle 9i, 10g, 11g R2 SQL Server 2000 (Service Pack 3 or later), 2005 (Service Pack 2 or later), 2008 Note:SQL Server Compact Edition is not supported. IBM DB2 for LUW 8.1.5 or later, 9.1 or later IBM DB2 for z/OS 8 and 9 Notes:
l
l l
To run RUNSTATS and the native REORG utility on tablespaces and indexes in DB2 for LUW, Toad supports DB2 for LUW 8.2.2 or later. At this time, Toad SQL Analysis for DB2 LUW does not support DB2 for LUW 9.7. Toad supports DB2 8 for z/OS running in Full Function mode, but does not support DB2 8 for z/OS running in Compatibility mode.
MySQL 5.1 Note: Toad can manage Amazon RDS and any other cloud or service offering compatible with MySQL.
l l l
Sybase ASE 12.5, 15.0.2, 15.0.3 (limited testing) Access 2003, 2007 Excel 2003, 2007
ODBC Database Support
Toad for Data Analysts supports almost all databases that you can connect to using an ODBC 3.0 or later driver. For a list of databases that are not supported, see Known Issues in the release notes. Toad for Data Analysts Quality Assurance has tested the following databases using an ODBC 3.0 or later driver:
l l l
DB2 for i5/OS V5R4 and IBM i 6.1 (limited testing) Informix Dynamic 10.00, 11.0 (limited testing) Ingres Community Edition 2006 R2 on Windows 32-bit (limited testing) Netezza Data Warehouse Appliance 4.6.6 PostgreSQL 8.3.4 Teradata V2R6.1 (limited testing)
l l l
Citrix Requirements
Limited testing has been performed for Citrix support on Windows Server 2003 Enterprise Server (Service Pack 2) using the MetaFrame Presentation Server 5.0 and Citrix Presentation Server Clients 10.2. See "Install Toad on Citrix Systems" (page 15) for more information.
User Requirements
User Requirements to Install Toad Only Windows Administrators and Power Users can install Toad. Note:The following exceptions exist for Power Users:
l
A Power User cannot install Toad on a computer running Windows Vista Enterprise. This is a Windows limitation because Vista does not support Power User mode. (DB2 only) A Power User cannot install Toad if a DB2 for LUW version earlier than 8.1.7 already exists on the computer. Only an Administrator can install Toad under this condition. However, if the computer has an existing DB2 for LUW 8.1.7 or later installation, a Power User can install Toad as long as this user belongs to the DB2ADMNS or DBUSERS group.
If an Administrator installs Toad, the Administrator can share the Toad shortcut icon on the desktop and menu items with any user--a Power User, Restricted User, Vista standard user--on the computer. If a Power User installs Toad, a Restricted User cannot do the following:
l l
Associate file extensions. View the Toad shortcut icon on the desktop or the Toad menu options in the Windows Start menu. As a workaround, Restricted Users can create a shortcut to Toad from the install directory and place the shortcut on their desktop.
User Requirements and Restrictions for Running Toad The following describes the requirements and restrictions for users who launch and run Toad:
l
(DB2 only) A Windows Power User or Restricted User must belong to the DB2ADMNS or DB2USERS group. To add the user to one of these groups, select Start | Control Panel | Administrative Tools | Computer Management | System Tools | Local Users and Groups | Groups | DB2ADMNS or DB2USERS. (DB2 only) A Windows Vista user must be either an administrator or a standard user that belongs to an Vista Administrators group. Additionally, to enable full functionality in Toad when Vistas User Access Control security feature is turned on, the standard user must run Toad as an administrator. (Right-click the Toad icon on the Vista desktop and select Run as administrator.) See the Toad for DB2 Release Notes for a description of the restrictions that are in place when the standard user does not run Toad as an administrator.
(DB2 only) A Windows Power User or Restricted User does not have the authority to add or remove DB2 catalog entries using the Toad Client Configuration wizard. However, these users can use the Import Profile function in the Toad Client Configuration wizard to import catalog entries to Toad. (DB2 only) As a minimum requirement to manage a DB2 for z/OS subsystem in Toad, the user ID defined in the Toad connection profile for the subsystem must either have SYSADM privileges or SELECT privileges on the DB2 catalog tables. To run Toad, the .NET security policy must be set to Unrestricted. To modify the security policy: 1. Select Control Panel from the Windows Start menu. 2. Double-click Administrative Tools. 3. Double-click Microsoft .NET Framework version Configuration. 4. Select My Computer, and then select the Runtime Security Policy node. 5. Select Evaluate Assembly from the list of tasks in the right panel, and locate and select Toad.exe in the File field. 6. Click Next and set the permission to Unrestricted. To create or modify the QuestSoftware.ToadSecurity table to enable Toad Security, the user who maintains this table must have privileges to create, insert, update, and delete it. All other users need only the ability to read the QuestSoftware.ToadSecurity table to use Toad Security features.
Install Toad
Note:If you received Toad for Data Analysts with your purchase of Toad for Oracle, note that by installing Toad for Data Analysts, you agree to use the software solely on the seat for which Toad for Oracle was purchased. To install Toad 1. Run the ToadInstaller.exe from the CD or downloaded file. 2. Complete the wizard. Note: On the Read-Only Installation page, select whether to install Toad as a typical install with all features enabled, or whether you want to install as read-only. In readonly mode, you cannot create, alter, or drop database objects.
Read-Only Installation
During installation, you can select an option to install Toad as a read-only application. This lets you query data and view objects using Toad, but all actions that can impact the database (Create, Alter, Drop, Insert, Update, etc.,) are disabled or hidden. This ensures that you can use Toad without worrying about committing a change to a sensitive production instance. The following image shows an example of differences between a typical and read-only installation:
To change an existing installation to read-only Reinstall Toad and select Read-only Install on the Install Type page.
Install Toad Silently

Silent installation provides a convenient method for deploying Toad to multiple machines. With some customization, you can also deploy the license key and settings at the same time
Determine Which Installer to Use

Before performing a silent installation, review the following to determine which installer to use: Installer Executable file (.exe) See "Install Toad Silently" (page 8) for more information. Advantages Silent installation using an exe file has the following advantages:
l
Disadvantages Silent installation using an exe file has the following disadvantages:
l
Verifies whether the prerequisite software is installed, and if not, redirects you to the download location. Verifies whether a version of Toad already exists on the target computer. If so, the executable uninstalls the previous version and then installs the current version.
Cannot deploy custom Toad settings files or license keys. Installer automatically exits if the prerequisite software is not installed.
Microsoft Installer file (.msi) See "Install Toad Silently" (page 8) for more information.
Supports deployment of Toad settings files and license keys.
Silent installation using an msi file has the following disadvantages:

l
Requires manual verification and download of any prerequisite software. Requires a manual uninstall of the previous version of Toad using Add/Remove Programs.
Silent Installation Prerequisites

Before you perform a silent installation, the following software must be installed on every computer on which you are installing Toad:
l l
Microsoft .NET Framework 3.5 (Service Pack 1) (DB2 native provider only) Toad installs a DB2 9.7 client as part of the installation process. The DB2 9.7 client can co-exist with an existing DB2 8 client; however, it is incompatible with a DB2 7 client. If a DB2 7 client is already installed on the system, the Toad installation stops and cannot complete. You must first upgrade to the DB2 8 client. Then restart the Toad installation to avoid losing functionality in some DB2 native tools.
Silent Installation Using the Executable

Use the executable file to perform a silent install to the default directory (or to a different directory) and to specify options such as logging installation messages. To perform a silent install using the executable file 1. At a Windows command prompt, switch to the drive or directory where the executable for Toad is located. (This file can be downloaded from the Quest web site or can be found on the Toad installation CD-ROM.) 2. For a standard installation with all features enabled, enter the following command:
ToadInstaller.exe /S
For a read-only installation with create, alter, and drop functionality disabled, enter the following command:
ToadInstaller.exe /S READONLY=TRUE
You can customize MSIEXEC command-line options and overrides for your installation similar to the following command:
ToadInstaller.exe /S /Lx C:\temp\installLog.txt INSTALLDIR=Drive:\your_install_path USERNAME=some_user COMPANYNAME=your_company ApplicationUsers=AllUsers
Use the following descriptions to customize the command-line options and overrides for your installation.
10
Command-Line Options The following MSIEXEC command-line options are used in this example: Option /L C:\temp\ installLog.txt Description (Optional) Write installation messages to the specified log. You can append other options, such as x for debug (used in the previous example) or v for a verbose log. See the log section at http://msdn2.microsoft.com/enus/library/aa367988.aspx for more information about additional logging options. Also, substitute C:\temp\installLog.txt in the example with the fully qualified name of the log file. Enclose this value in double quotations. The installation process creates this file if it does not exist. Otherwise, the existing file is overwritten Toad Default Installation Option Overrides You can specify the following values to override Toads default installation options. Enclose each value in double quotations: Option INSTALLDIR Description (Optional) Specify the absolute path for the directory in which you want to install Toad. If you do not include this path, the installation program defaults to: C:\Program Files\Quest Software\Toad for Data Analysts 2.5. (Optional) Specify the user that intends to use Toad on the target computer. Consider the following:
l
USERNAME
If OnlyCurrentUser is defined for the ApplicationUsers value (see description that follows), only the user specified here (and the user that installed Toad) can see the Toad shortcut on the desktop after the installation completes. If OnlyCurrentUser is defined but USERNAME is not included in the installation, only the user that installed Toad sees the Toad shortcut on the desktop. If AllUsers is defined for ApplicationUsers, the USERNAME value is ignored during installation.
COMPANYNAME
(Optional) Specify the name of the company that owns this installation.
11
Option ApplicationUsers
Description (Optional) Specify one of the following values:

l
AllUsers allows any user to see the Toad shortcut on the desktop after installation completes. OnlyCurrentUser allows only the user specified for USERNAME and the user that installed Toad to see the Toad shortcut on the target desktop. If USERNAME is not included in the installation, only the user that installed Toad sees the shortcut.
Note:If you do not specify a value, the installation program defaults to AllUsers. Note:All default installation option overrides are case-sensitive.
Silent Installation Using the Microsoft Installer

You can create a Microsoft transform (.mst) file that deploys the license key, custom settings, and connections for users when performing a silent install using the .msi file. You can also use the .msi file to perform a basic silent install using the default directory or can install to a different directory and specify command-line options and default installation overrides. See "Perform Silent Installation Using MSI" (page 13) for more information if you are not creating a transform file. Note:Review the following information about the msi installer:
l
The .msi file is located on the Toad installation CD or is available as a download from SupportLink at https://support.quest.com/SUPPORT/index?page=home. The installer does not verify that system requirements have been met before installing. If you do not want to manually verify system requirements, you should use the .exe file for the silent install.
Create Transform Files The following procedure uses the Wise Installer to create the transform file. To create a transform file that includes custom Toad settings 1. Save and install the ToadInstaller.msi file on a computer where the Wise for Windows Installer is installed. After customizing Toad settings, you will use the Wise Installer to create the transform file.
12
2. Open Notepad, and do the following: a. Enter the license key in the first line. b. Enter the site message in the second line. The file should look similar to the following: AAABBBBCCCCCCEDXDWLMV0WJ9-123-45678-B2 Quest Software c. Save the file with license.key as the file name in the Toad install directory. Make sure the file extension is .key not .txt. 3. Launch Toad. The application should open without prompting you to enter a license key. 4. Select Tools | Configuration Wizard from the Toad menu and complete the Configuration wizard. This wizard creates an initial settings file (Settings.xml). 5. Select Tools | Options from the menu in Toad to open the Options window. 6. Select each page in the window and set any options you want to deploy. These options create a module settings folder and files. 7. Select View | Connection Manager from the menu in Toad to open the Connection Manager. 8. Create any connections you want to deploy. 9. Exit Toad. Upon exiting, a Connections file is created. 10. Use the Wise for Windows Installer to create the Microsoft Transform file: a. Select File |New. b. Select Custom Templates under Categories, and then select the Transform template in the New Installation File window. c. Select the ToadInstaller.msi file in the Select the .MSI file to base this transform on window. d. Save the project. e. Select Files from the Feature Details view. f. Locate the following files and click Add to add them to the project: File to Add Settings.xml Location This file is located in the following directory: C:\Documents and Settings\username\Application Data\Quest Software\ Toad for Data Analysts 2.5.
13
File to Add ModuleSettings folder and files
Location This folder and related files are located in the following directory: C:\Documents and Settings\username\Application Data\Quest Software\ Toad for Data Analysts 2.5\ModuleSettings. This file is located in the following directory: C:\Documents and Settings\username\Application Data\Quest Software\Toad for Data Analysts 2.5.
Connections.xml
g. Save the project and compile it to create the transform (MST)file. 11. Perform a silent install. See "Perform Silent Installation Using MSI" (page 13) for more information. Perform Silent Installation Using MSI To perform a silent install using msi 1. At a Windows command prompt, switch to the drive or directory where the msi installer for Toad is located. This file is located on the Toad installation CD or is available as a download from SupportLink at https://support.quest.com/SUPPORT/index?page=home. 2. For a standard installation with all features enabled, enter the following command:
msiexec /i ToadInstaller.msi /q
For a read-only installation with create, alter, and drop functionality disabled, enter the following command:
msiexec /i ToadInstaller.msi /q READONLY=TRUE
You can customize command-line options and overrides for your installation similar to the following:
msiexec /i ToadInstaller.msi INSTALLDIR= Drive:\your_install_ path /q USERNAME=someone COMPANYNAME=your_company ApplicationUsers=AllUsers
14
Command-Line Options The following MSIEXEC command-line options are used in this example: Option /i /q Description Run the installation. Specify the user interface (UI) that displays during installation. You can append other options, such as n to hide the UI or b to hide the Cancel button during the installation.
Note:All command-line options are case-insensitive. See http://msdn2.microsoft.com/en-us/library/aa367988.aspxfor a complete list of command-line options. Toad Default Installation Option Overrides You can specify the following values to override Toads default installation options. Enclose each value in double quotations: Option INSTALLDIR Description (Optional) Specify the absolute path for the directory in which you want to install Toad. If you do not include this path, the installation program defaults to: C:\Program Files\Quest Software\Toad for Data Analysts 2.5. (Optional) Specify the user that intends to use Toad on the target computer. Consider the following:
l
USERNAME
If OnlyCurrentUser is defined for the ApplicationUsers value (see description that follows), only the user specified here (and the user that installed Toad) can see the Toad shortcut on the desktop after the installation completes. If OnlyCurrentUser is defined but USERNAME is not included in the installation, only the user that installed Toad sees the Toad shortcut on the desktop. If AllUsers is defined for ApplicationUsers, the USERNAME value is ignored during installation.
COMPANYNAME
(Optional) Specify the name of the company that owns this installation.
15
Option ApplicationUsers
Description (Optional) Specify one of the following values:

l
AllUsers allows any user to see the Toad shortcut on the desktop after installation completes. OnlyCurrentUser allows only the user specified for USERNAME and the user that installed Toad to see the Toad shortcut on the target desktop. If USERNAME is not included in the installation, only the user that installed Toad sees the shortcut.
Note:If you do not specify a value, the installation program defaults to AllUsers. Note:All default installation option overrides are case-sensitive.
Install Toad on Citrix Systems

To install Toad on a Citrix system 1. Connect to the Citrix Environment as an administrator. 2. Copy Toad to the Citrix server, if needed. 3. Install Toad. 4. During installation, select the Anyone who uses this computer checkbox when prompted. 5. Repeat steps 2 through 4 for each server in the Citrix farm. Note: Although you must install Toad on every server in the Citrix farm, you only need to publish Toad once. 6. Review the following considerations regarding licensing:
l
A license supplied by an administrator always overrides a user-supplied license in a Citrix environment. If you need to provide the same Toad functionality to all users, you can enter the default license key for all users.
16
Upgrade Toad
To upgrade Toad 1. Run the ToadInstaller.exe installation program from the CD or downloaded file. 2. Select Uninstall Toad and continue with install. 3. Complete the wizard. If you are upgrading from a previous version of Toad, you are prompted to migrate your settings the first time you start Toad. The settings files include database connections, layout customizations, shortcut keys, and options customized in the Options pages.
Files Migrated During Upgrades

When upgrading versions of Toad, the following files can be migrated from the previous version's Application Data Directory (Help |About to select a link to navigate to the location). File Action.log Description Tracks your usage within Toad. If you agree to share this data, the file is automatically sent to Quest on a periodic basis. Contains all connections stored in the Navigation Manager or the New Connection window. Contains the SQL Output connection trace log file if you select Tools | SQL Trace from the menu. Contains a log of all exceptions encountered while running Toad. Contains a log of exceptions encountered when attempting to connect to FTPservers. Contains connections to FTP servers stored in the FTP Connections window. Contains many of the global configuration settings. Used to generate SQL Server execution plans. Contains the last support bundle you generated. Description
Connections.xml ConnectionTrace.log ExceptionTrace.log FTPConnection.log FTPConnections.xml Settings.xml SqlServerPlanPrefs.xml ToadSupportBundle.zip Folder
17
Automation (temporary folder) Cache
Used by automation when executing automation scripts. Used to spool cache database metadata to disk if enabled. The data is in binary format and can always be recreated by fetching it from the database. Used by Compare plug-ins, script generation for Alter object windows, and the Script tab in the Object Explorer. Contains settings that depend on the context within Toad including the following:
l l
CNSScripter (temporary folder) Context
AdapterCustom data editing statements. FilterUnnamed filters defined in the Object Explorer or Database Explorer. Named FilterNamed filters defined in the Object Explorer or Database Explorer. TYPETabs that display on the right when you select an object in the Object Explorer or Database Explorer.
Keyboard Layouts
Contains custom keyboard shortcut layouts. Contains layouts for some areas in Toad, such as tool windows that automatically display in the Editor and column layouts for the Messages tab. Contains general settings for various components in Toad, such as whether the data grid defaults to read-only, displays not null indicators, etc. Used by Toad plugin components. Contains desktop configurations, including toolbar customizations and tool window locations. Contains pre-set and user created templates for formatting SQL, and the SQLstatement used to preview formatting changes in the Formatting Options page. Contains the SQL statements saved by SQL Recall. Contains the following templates:
l
ModuleSettings
Plugins Session SQLFormatter
SQLRecall Templates
Code TemplatesTemplates used to define default values when creating new objects in the Object Explorer or Database Browser. ScriptsStartup scripts to run when connecting. SnippetsCode Snippet entries.
l l
18
Register Toad
You should register Toadto ensure that all the features you purchased are available. Note:Consider the following:
l
If you have an existing Toad for Oracle license key, you can enter it in this window to enable Toad for Data Analysts. If you received Toad for Data Analysts with your purchase of Toad for Oracle, note that by installing Toad for Data Analysts you agree to use the software solely on the seat for which Toad for Oracle was purchased.
To register Toad 1. Select Help | Licensing from the menu. 2. Use the information provided by sales or support to complete the fields.
Uninstall Toad
If you uninstall Toad, it may not uninstall completely. When you use Toad, you create new files such as SQL scripts, data output, or temp files. The following types of files are not removed when you uninstall:
l l
Any new files you create Any copies of files you make for backup purposes
To uninstall Toad 1. Run the ToadInstaller.exe installation program from the CD or downloaded file. 2. Select Uninstall Toad only. 3. Complete the wizard.
2
Configuration
Configure Toad Layouts
Use the Configuration wizard to customize the look and feel of Toad to match Toad for Oracle, SQL Navigator, or your native database tools. In addition, you can specify the windows that display on startup or group functionality. Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions. To configure Toad layouts 1. Click the arrow beside (ALT+T+F). in the Standard toolbar and select Configuration Wizard
2. Review the following for additional information: Use this page... Layout and Settings To.... Set one of the following:
l
Toad for Data AnalystsApplies shortcut keys used by Toad for Data Analysts, opens default windows, and adds a Document Grouping and Wizard toolbar. Toad for OracleApplies shortcut keys used by Toad for Oracle and automatically opens the Project Manager, Editor, SQL Recall, and Output windows. MS Query AnalyzerApplies shortcut keys used by Query Analyzer and automatically opens the Object Explorer, Code Snippets, and Editor windows. MS Management StudioApplies shortcut keys used by Management Studio and automatically opens the Connection Manager and Editor windows. SQL NavigatorApplies shortcut keys used by SQL Navigator and automatically opens the Navigation Manager, Object Explorer, Editor, and Code Snippets windows. Toad for SQL Server, DB2, MySQLApplies shortcut keys used by Toad for SQL Server, DB2, and MySQL; and automatically opens the Connection Manager, Object
Toad for Data Analysts Installation Guide Configuration
20
Use this page...
To.... Explorer, Editor, and Code Snippets windows.

l
CustomApplies shortcut keys used by Toad for Data Analysts, and lets you specify layout settings on the remaining pages.
Note: You can set or modify individual keyboard shortcuts in Keyboard Options in the Toad help. Look and Feel Set one of the following:
l
SkinApplies the skin style you select to document windows, tool windows, and modal dialogs. Grid styleApplies the grid style you select to the data grid only.
When selecting an option, the current wizard page, including the sample data grid provides a preview of the change. Database Explorer Style Quick Guide Specify how objects display in the Object Explorer window.
Display a Quick Start Guide that lets you quickly launch frequently used features and tutorials until you are more familiar with the application. Tips:
l
To view this window at anytime, select View | Quick Guide from the menu. To hide this window when starting Toad, select the Do not show on start up checkbox at the bottom of the Quick Guide window.
Group Documents
Specify the following options:

l
Use document groupsDisplays a Grouping toolbar that categorizes features into logical workgroups. Hide windows per groupDisplays only those windows that are associated with the selected group. For example, if the Query group is selected and a Query Builder window is open, it will be hidden when you select the Report group. Note: Unless the Hide windows per connection checkbox is selected, any connections that have a window open for this group display.
21
Use this page...
To.... Hide windows per connectionDisplays only those windows for the current connection that are associated with the selected group.
Tip: To hide the Grouping toolbar, select Tools | Customize from the menu, and then clear the Grouping checkbox in the Toolbar tab of the Customize window. Group Document Defaults Select a default window to open for each connection when a selecting a group from the Grouping toolbar: Understand
l
ER DiagramEasily identify relationships between tables via foreign keys. Database ExplorerDrill-down to details for each object. Query BuilderQuickly create complex queries and subqueries using a graphical interface. SQL EditorPowerful editor for writing SQL queries and scripts.
Query
l
Report
l
ExcelAutomatically export query results and open them in Excel. Toad ReportSend query results to the Toad Data Report wizard.
Wizard Bar Additional Settings
Display a list of frequently used actions for the current group window in a toolbar at the bottom of the window. Specify whether to automatically add files to the Project Manager when saving, executing, or sending the files to a report. This option can help you locate and manage your work.
22
Configure Connections
Configure Oracle LDAP Support
You can create Oracle Lightweight Directory Access Protocol (LDAP) connections when your Oracle client is configured for LDAP. Once the client is configured, Toad retrieves names from your LDAP server and displays them in the Database Name list in the Create New Connection window. Notes:
l l
To connect using LDAP, you must install an Oracle client on the computer. Toad supports a 9i, 10g, and 11 client and the Oracle Instant client. If you want to use the instant client, you must configure it to work with Toad. See "Configure the Oracle Instant Client" (page 23) for more information.
To configure the Oracle client for LDAP 1. Obtain the LDAP.ORA file from your database administrator. 2. Copy the LDAP.ORA file to the folder where the SQLNET.ORA file for your Oracle client is located. The default folder is: ORACLE_HOME\network\admin 3. Open the SQLNET.ORA file and enter "(LDAP)" as the value for the NAMES.DIRECTORY_PATH as follows: NAMES.DIRECTORY_PATH= (LDAP) Note: If you are using multiple naming methods, add the (LDAP) value to existing parameter values. For example, if you are using both the TNSNAMES and LDAP naming methods, add LDAP to TNSNAMES as follows: NAMES.DIRECTORY_PATH= (TNSNAMES, LDAP) 4. Save the SQLNET.ORA file. 5. Launch Toad and select File | New | Connection. 6. Create an LDAP connection following the procedure in Create Oracle Connections (page 22). In step 3, select a database on the LDAP server from the Database Name list.
Create Oracle Connections

You can create a new connection, or connect to an existing connection from the Create New Connection window. See "Troubleshoot Oracle Issues" (page 60) for more information about troubleshooting connection issues. You can connect to your database using a native Oracle database provider in Toad using one of the following methods:
23
Connection Method
Advantages
Disadvantages
Client connection (Client tab)Uses an installed Oracle Client or Oracle Instant Client to establish a connection to the database from Toad.
Supports LDAP (See "Configure Connections" (page 22) for more information about configuring the Oracle client to use LDAP.) Does not require an Oracle Client to be installed Recommended for connecting to Oracle 8i databases
Requires an Oracle client Note:Toad supports Oracle clients and Oracle Instant clients using version 9i or later.
Direct connection (Direct Connect tab)Uses TCP/IP to connect directly to the database.
Only supports common data types. Some advanced Oracle object types cannot be retrieved when connecting using this method. Does not support LDAP (To connect using LDAP, use the Client Connection method instead.)
Note:Quest recommends using one of the methods described in this table to connect to Oracle rather than an ODBC driver. Because ODBC connectivity is generic, it is not fullfeatured and may not be as robust as the fully exploited native database provider. Configure the Oracle Instant Client The Oracle Instant client installs only those files needed to connect to your database using OCI. Because this client does not write to the registry (no ORACLE_HOMES) or add to the environmental path, you must manually set environment variables so the client can be used with Toad. To configure the Oracle Instant Client to work with Toad 1. Save the Oracle Instant Client files in any location on the computer where Toad is installed. 2. On your Windows desktop, right-click My Computer and select Properties. 3. Select the Advanced tab and click Environment Variables. 4. Click New under System Variables and complete the following:
24
Variable name PATH
Variable Value < Path where Instant Client is installed>;%PATH% For Example:C:\Program Files\OracleInstantClient;%PATH%
TNS_ ADMIN
< Path where tnsnames.ora file is installed>
Create an Oracle Connection To create an Oracle connection 1. Click on the toolbar (ALT+F+N).
2. Select Oracle from the Group list box. 3. Review the following for additional information: Login Tab Database name Description Select the alias to use when connecting. This list displays aliases from LDAP as well as any local tnsnames.ora file. Note: If you do not select a database, Toad uses the ORACLE_ SID for the selected home. If an ORACLE_SID value does not exist and you do not specify a database, you cannot connect. Password Enter the password to use when connecting. Tip: After connecting, you can set a master password to further secure your connection in Tools |Options|Environment | Password. Connect as Select whether to connect as either SYSDBA or SYSOPER if you have the appropriate permissions. Otherwise, use the default. Select a schema if you frequently work in a different schema than the one associated with your user name. (Optional) Specify the location of an existing explain plan table to use instead of Toad automatically creating one for you when you execute a statement. This is useful if you do not have necessary permissions to create explain plan tables or want to use an existing table.
Schema Explain plan table
25
Category
Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.). Select this checkbox if you plan to use Automation to generate reports. Description Modify the Oracle home to use, if needed. Click this button to edit your local TNSNames file. Tip:You can press CTRL+F to open the Find/Replace window to locate entries in the TNSNames Editor. Pressing F3 locates the next entry that matches your criteria. Click this button to edit SQLNET.ORA parameters. Before editing this file, you should create a backup copy. See SQLNET.ORA Profile Parameters in the Oracle documentation for more information. Description Enter the ORACLE_SID value for the database. This value is specified in the registry under each installed home. Edit the nickname you want to display in the Connection toolbar, status bar, and document windows, if needed. If this field is blank, the name defaults to: database (username), schema
Save password Oracle Client Tab Current home TNSNames Editor
SQLNET Editor
Direct Tab SID Name
Advanced Tab ODBC driver
Description Select an ODBC driver to use when creating heterogeneous queries in the Query Builder for this connection. Toaduses the Microsoft Access ODBC driver for heterogeneous queries by default. Tip:You can specify the ODBC driver to use for all connections for this database provider in Tools |Options | Database | Oracle.
26
4. Click Connect to save the connection and immediately connect to the database. or Click Save to save the connection without connecting to the database. Tip:Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About.
Configure DB2 LDAP Support

You can create DB2 Lightweight Directory Access Protocol (LDAP) connections when the DB2 client installed with Toad is configured for LDAP. Configuring the client consists of enabling LDAP support and specifying the host name and port number of the LDAP server. Once the client is configured, Toad retrieves names from your LDAP server and displays them in the Database Alias list in the Connections window. Notes:
l
You must configure LDAP support for the DB2 client installed with Toad regardless of whether an existing DB2 client on the computer is already configured to support LDAP. Currently, Toad for DB2 supports only the access of DB2 LDAP catalog entries. Toad does not support the management of these entries.
To configure the DB2 client for LDAP 1. Open the Command Window for the DB2 client installed with Toad by selecting Start | All Programs | IBM DB2 | <ToadCom, ToadEval, or ToadFree> | Command Line Tools | Command Window. 2. Enter the following command to enable LDAP support:
db2set DB2_ENABLE_LDAP=YES
3. Enter the following command to specify the TCP/IP host name and port number of the LDAP server:
db2set DB2LDAPHOST=<hostname[:port]>
The port number defaults to 389 (default LDAP port) if you leave the port number blank. 4. Exit the Command window. 5. Launch Toad and open the Connections window. Databases on the LDAP server should be available from the Database alias dropdown list in the Connections window. To complete the Toad connection setup, you
27
must create a Toad connection profile for each database. See "Create Toad Connection Profiles for DB2" (page 36) for more information.
Configure DB2 Client Connections

Toad requires two phases to set up connections to the DB2 for LUW databases and DB2 for z/OS subsystems that you want Toad to manage. The first phase is to catalog each of these databases or subsystems on the DB2 client installed with Toad. Toad provides three methods for cataloging the systems:
l
Transfer an existing catalog from another DB2 client on your computer You can transfer the catalog of an existing DB2 client on your local computer to the new Toad DB2 client during initial setup or at any time later.
Transfer a Catalog During Initial Setup

When you first launch Toad after installation, Toad provides an opportunity to transfer the catalog of an existing DB2 client on your local computer to your new Toad DB2 client. (In other words, Toad exports and imports the catalog for you.)
Toad makes this option available only when all of these conditions exist:
l
You are launching Toad for the first time since installation. This installation is a first-time Toad installation on your computer, or it is an upgrade from a previous Toad version already on your computer. Toad detects other DB2 clients installed on your computer. These can include the DB2 clients laid down with other installations.
If you choose not to transfer an existing catalog at this point, you can transfer a catalog later. See "Transfer a Catalog Any Time After Initial Setup" (page 28) for more information.
28
To migrate an existing DB2 catalog 1. Open Toad after installation is complete. 2. If Toad displays the Settings Migration Utility window, select whether to migrate from your previously installed Toad. (These settings include Toad connection profiles.)
l
If you migrate settings, the window showing the option to transfer a catalog displays once the migration completes. If you do not migrate settings, the window showing the option to transfer a catalog displays when you select to create the first connection. If the Settings Migration Utility window does not display, go to step 3.
3. On the window showing the option to transfer a catalog, locate the DB2 Client list, and select the name of the existing DB2 client whose catalog you want to transfer to your newly installed Toad . This list contains all current previously installed DB2 clients on your computer, including the default DB2 client instance and other Toad client installations. 4. Click OK to proceed with the catalog transfer. When the transfer completes, the Connections window displays. The Database alias drop-down list now includes all the DB2 databases and subsystems whose catalog entries you transferred. Note: During the transfer process, DB2 does not automatically export catalog entries for the local DB2 instance and its databases installed on your computer unless these entries already exist in the catalog you are transferring. To include local node entries in your Toad DB2 client catalog, you must manually catalog these databases. 5. Proceed to Create Toad Connection Profiles for DB2 (page 36) for the DB2 databases and subsystems whose connection profiles you did not migrate (in step 2). For those profiles you migrated, simply select the connection in the Connections window, and provide the login ID and password to start the connection.
Transfer a Catalog Any Time After Initial Setup

To transfer a catalog any time after initial setup 1. In the Connection Manager or on the Connections window, click the toolbar. in
2. From the DB2 Client list, select the name of the existing DB2 client whose
29
catalog you want to transfer to your newly installed Toad. This list contains all current previously installed DB2 clients on your computer, including the default DB2 client instance and other Toad client installations. 3. Click OK. 4. Create Toad Connection Profiles for DB2 (page 36) for any of the transferred catalog entries as needed.
l
Import a DB2 Catalog previously exported to a file Toad provides functionality to import an existing DB2 client catalog to your Toad DB2 client, saving you the effort of manually creating individual catalog entries on the Toad DB2 client. This feature executes the DB2 Connectivity Configuration Import Tool command db2cfimp, which imports an export profile containing the catalog exported the from a local or remote DB2 client or a local Toad DB2 client. Either of these functions export DB2 catalogs:
l
Export Profile feature in the Toad Configuration wizard (for exporting your current Toad DB2 client catalog only). See Export the Catalog for the Current DB2 Client. DB2 Connectivity Configuration Export Tool Command db2cfexp. For more information, see the following IBM documentation: http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/ com.ibm.db2.udb.doc/core/r0002442.htm.
Note: Do not attempt to manually import catalog entries from the IBM CLP window provided with Toad. If you have any DB2 ODBC entries, db2cfimp will override your existing ODBC system with DSN entries and can cause previously configured DB2 ODBC connections to stop working. To import an exported catalog profile 1. In the Connections (or Create New Connection) window, click beside the Database alias drop-down list to open the Client Configuration wizard. 2. On the Welcome page, select Import Profile. 3. Click Next. 4. Click in the Profile name field to browse for and select the exported profile you want to import. When you select the profile, its contents display in the text pane. 5. Complete the wizard.
30
Once you close the wizard, the Database alias drop-down list in the Connections window includes all the DB2 databases and subsystems whose catalog entries you imported. Note: DB2 does not automatically export catalog entries for the local DB2 instance and its databases on the computer from which the export is run (unless these entries already exist in the catalog). Therefore, the profile you are importing might not include these node entries. To add the missing entries to your Toad DB2 client catalog, you must manually catalog the databases. If these databases are local to your computer, catalog them as remote databases. See "Manually catalog DB2 for LUW databases" (page 30) for more information. 6. Proceed to catalog entries as needed. See "Create Toad Connection Profiles for DB2" (page 36) for more information.
l
Manually catalog DB2 for LUW databases To manually catalog a DB2 for LUW database 1. In the Connections (or Create New Connection) window, click beside the Database alias drop-down list to open the Client Configuration wizard. The Welcome page displays, showing the Toad DB2 client's existing catalog configuration in a tree view. 2. If the host and node names for the database you want to configure are listed in the tree, select them. These selections pre-fill certain fields required later in the wizard process. If these names are not listed, you must provide the necessary host and node information later in the wizard. 3. Click Add Catalog Entry. 4. Review the following for additional information: Add a Host Operating system Description Select the operating system for the server on which the DB2 for LUW instance containing the DB2 database you are cataloging resides. For a list of supported server platforms, see the release notes. Enter the TCP/IP address or the system name for the server on which the DB2 database resides. Enter the port number for the server on which the DB2 database resides.
Host name Port number
31
Enable SOCKS security Specify an Instance Node name
Select this checkbox to enable the SOCKS secure protocol to handle TCP traffic for this connection. SOCKS adds an authentication mechanism for additional security. Description Enter a user-defined name for the DB2 instance containing the database you are cataloging. If you selected the node name from the tree on the Welcome page, this information is pre-filled (but you can update it as needed).
Instance name Comment Add a Database Database name Database alias Authentication Target principal
Enter the real name of the DB2 instance. Enter a descriptive comment for the instance, if needed. Description Enter the real name of the DB2 database. Enter a unique nickname to identify the database on your system. Select the authentication method that is required to connect to the database. Enter the service account name for server's service where the database resides. Note: This option is available only when Kerberos is selected as the authentication method.
5. Complete the wizard. The Database alias drop-down list in the Connections window shows the alias for the newly cataloged database. To complete the Toad connection setup, you must create a Toad connection profile for the database. See "Create Toad Connection Profiles for DB2" (page 36) for more information.
l
Manually catalog DB2 for z/OS subsystems Note: If you connect directly to a DB2 for z/OS subsystem, you cannot take advantage of Sysplex. If you want to use Sysplex, catalog an entry to a DB2 Connect gateway instead. See "Manually catalog DB2 Connect gateways" (page 33) for more information.
32
To manually catalog a DB2 for z/OS subsystem 1. In the Connections (or Create New Connection) window, click beside the Database alias drop-down list to open the Client Configuration wizard. The Welcome page displays, showing the Toad DB2 client's existing catalog configuration in a tree view. 2. If the host name for the DB2 subsystem you want to configure is listed in the tree, select it. This selection pre-fills certain fields required later in the wizard process. If the host name is not listed, you must provide the necessary host information later in the wizard. 3. Click Add Catalog Entry. 4. Review the following for additional information: Add a Host Operating system Host name Port number Enable SOCKS security Add a DB2 Subsystem Location name Database alias Description Select z/OS for the server operating system. Enter the TCP/IP address or the system name for the server on which the DB2 subsystem resides. Enter the port number of the service for the DB2 subsystem. Select this checkbox to enable the SOCKS secure protocol to handle TCP traffic for this connection. SOCKS adds an authentication mechanism for additional security. Description Enter the location name of the DB2 subsystem as defined during the DB2 installation. Enter a unique, user-defined alias to identify the DB2 subsystem on your system. You can use the same name you used in the previous Location name field, as long as it does not already exist in the list aliases in the Toad DB2 client.
5. Complete the wizard. A message window informs you whether the entry was added successfully. The Database alias drop-down list in the Connections window shows the alias for the newly cataloged subsystem. To complete the Toad connection setup,
33
create a Toad connection profile for the database. See "Create Toad Connection Profiles for DB2" (page 36) for more information.
l
Manually catalog DB2 Connect gateways In order to connect to a DB2 for z/OS subsystem, you need to catalog two entries. First, you need to catalog the DB2 subsystem on the DB2 Connect gateway. During this process, you define an alias for the DB2 subsystem. Second, you need to catalog this DB2 subsystem alias in Toad. The procedure below describes both cataloging events. To manually catalog an entry to a DB2 Connect gateway 1. Catalog the DB2 subsystem on the DB2 Connect gateway. See the IBM DB2 for z/OS documentation for more information. 2. In the Connections (or Create New Connection) window in Toad, click beside the Database alias drop-down list to open the Client Configuration wizard. 3. Click Add Catalog Entry. 4. Review the following for additional information: Add a Host Operating system Host name Port number Enable SOCKS security Specify an Instance Node name Description Select the operating system for the server on which the DB2 Connect gateway resides. Enter the TCP/IP address or the system name for the server on which the DB2 Connect gateway resides. Enter the port number of the service for the DB2 Connect gateway. Select this checkbox to enable the SOCKS secure protocol to handle TCP traffic for this connection. SOCKS adds an authentication mechanism for additional security. Description Enter an alias for the user-defined node name you specify in the Instance name field.
34
Instance name
Enter a user-defined name for the gateway node or use the same value entered in the Node name. Note: This name does not point to an actual node on the gateway system, but is needed to continue the cataloging process.
Add a Database Database name
Description Enter the database alias name for the DB2 subsystem. Note: This alias name must match the alias cataloged on the DB2 Connect gateway.
Database alias
Enter a unique, user-defined alias for the DB2 Connect gateway. You can use the same alias you used in the previous Database name field, as long as it does not exist in the list of Toad for DB2 aliases. Select the authentication method that matches the method specified for the DB2 subsystem on the DB2 Connect gateway.
Authentication
5. Complete the wizard. The Database alias drop-down list in the Connections window shows the name for the newly cataloged DB2 subsystem. To complete the Toad connection setup, you must create a Toad connection profile for the subsystem. See "Create Toad Connection Profiles for DB2" (page 36) for more information. Note: Toad for DB2 supports LDAP connections. See "Configure DB2 LDAP Support" (page 26) for more information. Additionally, Toad provides functionality to perform the following maintenance on the catalog you set up for the current Toad DB2 client:
l
Edit DB2 Catalog Entries To edit a DB2 catalog entry 1. In the Connections (or Create New Connection) window, click beside the Database alias drop-down list to open the Client Configuration wizard. 2. In the catalog configuration tree for the Toad DB2 client, select the catalog entry for the DB2 database or subsystem that you want to edit. 3. Click Edit Catalog Entry. 4. On the Edit Catalog Entry page, update the catalog properties as needed. For a description of the catalog properties, see the following links:
35
Manually catalog DB2 for LUW databases (page 30) Manually catalog DB2 for z/OS subsystems (page 31) Manually catalog DB2 Connect gateways (page 33)
l l
5. Click Next to open the Catalog Script Review window. 6. Review and modify the script in the preview pane as needed. 7. Click Finish. A message window displays, informing you whether the updates to the catalog entry completed successfully.
l
Remove DB2 Catalog Entries To remove a DB2 catalog entry 1. In the Connections (or Create New Connection) window, click beside the Database alias drop-down list to open the Client Configuration wizard. 2. In the catalog configuration tree for the Toad DB2 client, expand one or more nodes, and select the catalog entries that you want to remove. (Press CTRL+click to select multiple entries.) Note: You can remove a node by selecting all database entries for that node. 3. Click Remove Catalog Entry. 4. On the Catalog Script Review page, modify the script in the preview pane as needed. 5. Click Finish. A message window displays, informing you whether the removals completed successfully.
Export the Catalog for the Current DB2 Client Toad for DB2 provides functionality to export your current Toad DB2 client catalog to a file, called an export profile. You can then import this profile to set up the catalog for another Toad DB2 client. To create the export profile containing the current Toad DB2 client catalog, Toad executes the DB2 Connectivity Configuration Export Tool command db2cfexp. If you want to export the catalog of a remote or local DB2 client (other than your current Toad DB2 client), you must manually execute this command. For more information, see the following IBM documentation: http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/ com.ibm.db2.udb.doc/core/r0002442.htm. To export the Toad DB2 client catalog 1. In the Connections (or Create New Connection) window, click Database alias drop-down list. beside the
2. Click Export Profile in the Welcome window of the Client Configuration wizard.
36
(You might need to click 3. Click Next.
this button.)
4. Click in the Profile name field to browse for and select the path for the profile in which to export the current Toad DB2 client catalog. 5. Select the type of profile you want to create:
l
Template to create a profile used as a template for other DB2 clients (default for exporting a Toad DB2 catalog) Backup to create a profile used to back up a DB2 database instance Maintain to create a profile that contains only database or node information required for updating other instances For more information about these profile types, see the IBM documentation (as cited previously) describing the db2cfexp command.
6. Complete the wizard. A message window displays, informing you whether the export completed successfully. Note: DB2 does not automatically export catalog entries for the local DB2 instance and its databases installed on your computer unless these entries already exist in the catalog you are exporting. If you later import the export catalog to a Toad DB2 client, you must manually catalog the missing local-node databases as remote databases. See "Manually catalog DB2 for LUW databases" (page 30) for more information. After you have set up the catalog on the current Toad DB2 client, you can proceed to the second phase of the Toad connection setup. This phase involves creating Toad connection profiles for the cataloged DB2 databases or subsystems. See "Create Toad Connection Profiles for DB2" (page 36) for more information.
Create Toad Connection Profiles for DB2

Toad requires two phases to set up connections to the DB2 for LUW databases and DB2 for z/OS subsystems that you want Toad to manage. Tip:Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About. The first phase is to catalog each of these databases or subsystems on the DB2 client installed with Toad. See "Configure DB2 Client Connections" (page 27) for more information. The second phase involves creating Toad connection profiles for the cataloged DB2 databases or subsystems. Each profile contains the information that Toad needs to connect to the system, such as the user ID and password, DB2 registry settings, and the default schema. This topic describes the three methods for setting up the profiles:
l
Migrate existing connection profiles from another Toadinstallation on your computer (available during initial Toad setup only)
37
When you first launch Toad after installation, Toad provides an opportunity to migrate the settings of an existing Toad installation on your local computer to your new Toad installation. These settings include, among other configuration parameters, the Toad connection profiles defined on the earlier installation. (Toad exports and imports these connection profiles for you.) Toad makes this option available only when both of these conditions exist:
l
You are launching Toad for the first time since installation. Toad detects earlier versions of Toad on your computer.
If you choose not to migrate the connection profiles at this point, you can perform the migration later using the Connection Managers' Import Connections and Export Connections features. To migrate Toad connection profiles 1. Open Toad after installation is complete. Toad displays the Settings Migration Utility window if the conditions described previously exist. 2. Select the Toad installation whose connection profiles you want to migrate to your new Toad installation, and click Migrate. After the migration completes, Toad provides the option to transfer a local DB2 catalog to your new Toad DB2 client. 3. Select to transfer a DB2 catalog or to manually catalog entries later. See "Configure DB2 Client Connections" (page 27) for more information. Note: The connection profiles you migrated are not usable unless you also transfer the DB2 catalog containing the corresponding entries for these profiles (or until you manually create these catalog entries later). After the catalog transfer is complete, your Toad connection setup is complete for all those connections that have both a catalog entry on the Toad DB2 client and a Toad connection profile. For any connection that does not have a corresponding DB2 catalog entry, create an entry. See "Configure DB2 Client Connections" (page 27) for more information.
l
Import Toad connection profiles previously exported to an XMLfile (See "Export Connection Profiles to an XML File" (page 39) for more informationabout exporting a profile that you can later import.) Note: The connection profiles are not usable unless you have also created entries in the DB2 catalog for the DB2 databases and subsystems to which these profiles correspond. See "Configure DB2 Client Connections" (page 27) for more information.
38
To import connection profiles 1. In the Connections (or Create New Connection) window, click toolbar, and select Connection file. on the
2. From the Import Connections window, browse for and select the XML file containing the connection profiles you want to import. 3. Click Open. 4. Select DB2 and click OK to complete the import. The connections whose profiles you imported are listed on the Connections window.
l
Manually define Toad connection profiles. To create a Toad connection profile for a DB2 database or subsystem 1. In the Connections (or Create New Connection) window, click toolbar (ALT+F+N). 2. Select DB2 from the Group list box. 3. Review the following for additional information: Database alias Select the alias for the DB2 database or subsystem. This alias was defined when you cataloged this DB2 database or subsystem on the Toad DB2 client. See "Configure DB2 Client Connections" (page 27) for more information if the alias does not display in the list. Enter the SET SCHEMA value (DB2 for LUW) or the SET SCHEMA or SET CURRENT SQLID value (DB2 for z/OS) for this connection. Edit the nickname you want to display for this connection throughout Toad (for example, in the Connections window, document windows, Connection toolbar, and status bar). If this field is blank, the name defaults to: database_alias (login) Category Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.). on the
Default schema/auth ID Name
39
4. Select the Advanced tab to define special register values that are then in effect each time Toad connects to the DB2 database or subsystem. 5. Click Connect to save the connection and immediately connect to the database. or Click Save to save the connection without connecting to the database. After you have completed both phases for configuring Toad connections to DB2 databases or subsystems, the Connections window lists all the configured connections, allowing you to perform the following:
l
Connect to and manage a DB2 database or subsystem through Toad Export Connection Profiles to an XML File Toad for DB2 provides functionality to export one or more of your current Toad connection profiles to an XML file. You can then import these exported connection profiles into another Toad installation. See "Import Toad connection profiles previously exported to an XMLfile " (page 37) for more information. To export connection profiles 1. In the Connections (or Create New Connection) window, select the connections whose profiles you want to export. 2. Click on the toolbar, and select Connection file.
3. On the Export Connections window, review the selected connections, and click OK. 4. Browse for and select the path for the file in which to export the selected profiles.
l
Import connection profiles from an XML file Import missing connections defined on the Toad client. You can import all connection entries currently defined in the Toad DB2 client catalog but missing from your current list of Toad connections.See "Create Toad Connection Profiles for DB2" (page 36) for more information. Note: The imported connection entries might be associated with incorrect or missing DB2 catalog or Toad connection profile information, making them currently invalid. To re-instate any of these connections, you might need to provide accurate DB2 catalog and Toad profile information. To import missing connections In the Connections or Connections Manager window, click .
40
Troubleshoot connection issues for DB2 for LUW databases or DB2 for z/OS subsystems
Create Access Connections

Although this connection uses the ODBC driver, it is easier and faster to connect using this method. See "Troubleshoot Database Issues" (page 48) for more information about troubleshooting connection issues. Notes:
l
The Toad Sample database already has a username and password defined. The connection information for this database is: Database file = C:\Program Files\Quest Software\ToadInstallDirectory\Plugins\Odbc\Sample Database\Quest_Stage.mdb User = QUEST Password = QUEST Additional sample files for this database are available in the Project Manager.
This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions.
To create an Access connection 1. Click on the toolbar (ALT+F+N).
2. Select Access from the Group list box. 3. Review the following for additional information: Database file MDW file Password Select the database to use when connecting. Select the MDW file that is linked to the database. Enter the password to use when connecting. Tip: After connecting, you can set a master password to further secure your connection in Tools |Options|Environment | Password. Name Category Edit the nickname you want to display in the Connection toolbar, status bar, and document windows, if needed. Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.).
41
Create Excel Connections

Although you can create a connection to an Excel file from the standard ODBC driver, this method uses the Microsoft Jet Database Engine, which makes connecting to Excel much easier and faster. See "Troubleshoot Excel" (page 49) for more information about troubleshooting connection issues. Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions. To create an Excel connection 1. Click on the toolbar (ALT+F+N).
2. Select Excel from the Group list box. 3. Review the following for additional information: File name Name Category Select the Excel file you want to connect to. Edit the nickname you want to display in the Connection toolbar, status bar, and document windows, if needed. Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.).
42
Create MySQL Connections

You can create a new connection, or connect to an existing connection from the Create New Connection window. See "Troubleshoot MySQL Issues" (page 59) for more information about troubleshooting connection issues. Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions. To create a MySQL connection 1. Click on the toolbar (ALT+F+N).
2. Select MySQL from the Group list box. 3. Review the following for additional information: Login Tab Connection type Host Password Description Select the protocol to use when connecting. Enter the name of the host computer where the database is installed. Enter the password to use when connecting. Tip: After connecting, you can set a master password to further secure your connection in Tools |Options|Environment | Password. Connection timeout SSL Enter the number of seconds to wait when connecting before the application times out. The default is 15 seconds. If you selected SSL as the connection type, review the following for additional information:
l
Private keybrowse to the location of the SSL key file to use when connecting. CA certbrowse to the location of the trusted certificate authority to use when connecting. Certbrowse to the location of the SSL certificate file to use when connecting.
Compress Use MySQL libraries
Select this checkbox to compress the value of any strings and return binary values. Select this checkbox to use an embedded MySQL library instead of the MySQL .NET provider. Note: If you select this option, you must specify libMySQL.dll
43
in the path. Name Edit the nickname you want to display in the Connection toolbar, status bar, and document windows, if needed. If this field is blank, the name defaults to: username@hostname (database) Category Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.). Description Select an ODBC driver to use for heterogeneous queries for this connection. Tip:You can specify the ODBC driver to use for all connections for this database provider in Tools |Options | Database | MySQL. 4. Click Connect to save the connection and immediately connect to the database. or Click Save to save the connection without connecting to the database. Tip:Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About.
Advanced Tab ODBC driver
Create ODBC Connections

The purpose of the ODBC provider is to offer basic connection and querying capabilities to any database that supports an ODBC 3.0 or later driver. For a list of databases tested with the ODBC provider, see the Release Notes. This form of connectivity allows connections to databases such as Teradata, Netezza, IBM iSeries, and Ingres. Because this form of connectivity is generic, it is not full-featured and may not be as robust as the fully exploited providers for databases that use a native provider.
Scenario
You need to create an ODBC connection to an Oracle 11g database. To create an ODBC connection 1. Click on the toolbar (ALT+F+N+O).
2. Select ODBC from the Group list box.
44
3. Click 4. Click Add.
in the Data Source Name field.
5. Select an ODBC driver from the list, and click Finish. Scenario: Select the ODBC driver provided by Oracle. The Microsoft ODBC for Oracle driver has less functionality than the driver provided by Oracle. 6. Specify the configuration properties required for the database. Scenario: If you have an Oracle database with Unicode data, make sure to select Force SQL_WCHAR Support on the Workarounds tab. If you do not, you will not be able to see the data. 7. Review the following fields on the Create New Connection window: Data source name User Password Select the type of data source you want to connect to from the list. Enter the user name to use when connecting. Enter the password to use when connecting. Tip: After connecting, you can set a master password to further secure your connection in Tools |Options|Environment | Password. Database Specify the location of the database schema. Click to create a temporary connection and display available schemas in the dropdown list. Specify the following connection options. Displays they type of data source selected.
Information Data Source Name Driver Connection String Name Category
Displays the ODBC driver associated with the data source. Enter the connection string. Edit the nickname you want to display in the Connection toolbar, status bar, and document windows, if needed. Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.).
8. Click Connect to save the connection and immediately connect to the database.
45
or Click Save to save the connection without connecting to the database. Tip:Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About.
Create SQL Server Connections

You can create a new connection, or connect to an existing connection from the Create New Connection window. See "" (page 62) for more information about troubleshooting connection issues. To create a new connection 1. Click on the toolbar (ALT+F+N).
2. Select SQL Server from the Group list box. 3. Review the following for additional information: Login Tab Server name Description Enter the name of the server to use when connecting. Click to display any servers running SQL Server that are currently active on the network. Note: For named instances, enter the MachineName\InstanceName in this field. Password Enter the password to use when connecting. Tip: After connecting, you can set a master password to further secure your connection in Tools |Options|Environment | Password. Name Edit the nickname you want to display in the Connection toolbar, status bar, and document windows, if needed. If this field is blank, the name defaults to: servername (login) database Category Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.). Description
Advanced Tab
46
OBDC driver
Select an ODBC driver to use for heterogeneous queries for this connection. Tip:You can specify the ODBC driver to use for all connections for this database provider in Tools |Options | Database | SQLServer.
Create Sybase ASE Connections

You can create a new connection, or connect to an existing connection from the Create New Connection window. See "Troubleshoot Sybase ASE Issues" (page 63) for more information about troubleshooting connection issues. Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions. To create a Sybase ASE connection 1. Click on the toolbar (ALT+F+N).
2. Select Sybase ASE from the Group list box. 3. Review the following for additional information: Login Tab CharSet Description Enter the client character set such as UTF-8 in this field if it differs from the default character set. This helps you avoid connection issues. Note:This field is not case sensitive. Password Enter the password to use when connecting. Tip: After connecting, you can set a master password to further secure your connection in Tools |Options|Environment | Password. Name Category Edit the nickname you want to display in the Connection toolbar, status bar, and document windows, if needed. Select or create a category if you want to color code Editor tabs for a specific connection. This can help differentiate between
47
development and production databases. You can also set an option to color code the Object Explorer pane and object editor windows (Create, Alter, Drop, etc.). Advanced Tab ODBC driver Description Select an ODBC driver to use for heterogeneous queries for this connection. Tip:You can specify the ODBC driver to use for all connections for this database provider in Tools |Options | Database | Oracle. 4. Click Connect to save the connection and immediately connect to the database. or Click Save to save the connection without connecting to the database. Tip:Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help |About.
Understand Toad Connections

In Toad, a connection represents one or more actual connections to the database. Toad creates an initial database connection for general usage. It also creates a separate database connection for each Editor (the first time you execute a statement) and a separate database connection for each Data tab in the Database Explorer (the first time you select the tab and data is queried). The database connection for each Editor and Data tab remain open until you close the associated window; however, the connections remain in an inactive state if a statement is not currently executing. Tips:
l
To view the number of actual database connections that exist for a Toad connection and how many of those database connections are active, place the cursor over the connection in the Connection Manager or the Connection toolbar (illustrated in the following example).
48
You can view the progress of statements executing in the background in a progress bar located on the lower right side of the status bar. To cancel a script's execution, click the progress bar to display the Background Processes window.
Share Database Connections Editors and Data tabs can share the same database connection when the connection is inactive if you clear the Use specific connection for each open editor checkbox in Tools | Options |Editor |General. Any new executions or windows attempt to use this connection first. For example; if you share a database connection, you can execute a query in the Editor, execute another query in a new Editor, and then select the Data tab from the same connection. If the connection is in use and you attempt to execute it, one of the following occurs:
l
(DB2 and Oracle only) If your database supports executing multiple queries simultaneously on a shared connection, the query is placed in a queue and executes as soon as the current operation completes. If your database does not support executing multiple queries on a shared connection, a dialog prompts you to either permanently associate the window with a new database connection, cancel the previous operation, or add the query to a queue until the current operation completes, and the execute it. If you place multiple queries in the queue, each one executes in the order that it was added to the queue.
Note: Although you can share a database connection, any commits apply to the selected window only.
Troubleshoot Database Issues

Troubleshoot Access Issues
Review the following solutions to help troubleshoot Access issues pertaining to missing functionality and object information and other problems in Toad.
49
Missing Functionality and Object Information Issue Some queries display in the View tab of the Object Explorer, but do not display in the Query tab. Cause/Solution The Access ODBC driver handles saved queries in the following manner:
l
If the stored query does not contain parameters, it is treated as a view and displays in the View tab. If the stored query contains parameters, it is treated as a stored procedure and displays in the Query tab.
Primary key information is unavailable.
The Microsoft Access ODBC driver does not return primary key information for databases. However, in some cases, Toad can obtain this information through additional methods.
Other Issues Issue A delay occurs between writing a value to a database via one connection and seeing the updated value via another connection. Cause/Solution This delay is the default when you are writing and reading data between two different Jet connections. The delay occurs even if the two connections reside in the same client process. Solution: Use a single connection when updating data.
Troubleshoot Excel
Review the following solutions to help troubleshoot Excel:
l
Connections Web Browser integration
50
Connections Issue Tables are limited to 256 columns and 65536 rows. Column names longer than 64 characters are truncated and the remaining characters display as null. Tables do not display when connected. or The following error displays when connecting: "No user tables could be found in spreadsheet_ name.xls Cause/Solution This is a known limitation with Excel worksheets.
This is a known limitation with Excel worksheets.
This issue occurs because the worksheet does not include named regions. The Excel ODBC driver displays named regions as user tables and worksheets as system tables with a '$' appended to the end of the name. Solution 1: Show System Tables To view the worksheet, select the Show system objects checkbox in ODBC Options. Solution 2: Define Named Regions in the Worksheet 1. Disconnect your connection to the Excel spreadsheet in Toad. 2. Open the spreadsheet in Excel. 3. Select the columns and rows you want to define as a table. Make certain you include the column names. 4. Select Insert | Name | Define from the menu. 5. Enter a name for the named region. 6. Save your spreadsheet and exit Excel. 7. Reconnect to the Excel spreadsheet in Toad. A table displays with the name you specified for the named region.
Two worksheets with the same name are created when creating a new table.
The Excel ODBC driver automatically creates one worksheet with a named range and a new worksheet with the same name when you use the Create Table feature.
51
Issue Columns that include text values or special characters as part of a numeric value as well as entries with straight numeric values result in the one of the value sets displaying as null.
Cause/Solution When you connect to Excel, the driver automatically scans the first eight rows in a column and applies the data type used in a majority of those rows to all rows in the column. Any rows that do not meet the majority data type display as null values. Solution 1: Reformat Worksheet Column and Values as Text 1. Open the worksheet in Excel. 2. Format the column that contains mixed data types as Text. 3. Re-enter each value in the column. 4. You can now connect to this spreadsheet from Toad without any null values displayed. Solution 2: Force ODBC to Read All Rows as Text You can force the ODBC driver to read all rows as Text to avoid null values; however, this can result in issues if you attempt to insert data. Note: This option is not available if you use the Excel Microsoft Jet Database Engine to connect. 1. Open the Create New Connection window and select ODBC from the Group list box. 2. Complete the fields as described in Create ODBC Connections. 3. Enter "IMEX=1", in quotations, in the ExtraParameters field. 4. Click Connect.
Column names that contain an exclamation point (!) are not supported. Tables cannot be altered. The Primary Keys and Foreign Keys tabs are blank in the Database Explorer. Views do not display in the View tab in the Object Explorer, and attempting to create a
The exclamation point character has a special meaning in Excel. If a column name contains an exclamation point, it is internally converted to a dollar sign ($) character. The Excel ODBC driver does not support this functionality. Excel is a spreadsheet, and does not support primary and foreign keys so these tabs are always blank.
The Excel ODBC driver mistakenly indicates that views are
52
Issue view displays a message that the operation is not supported. The Procedures tab in the Object Explorer is blank. Indexes cannot be created or dropped. Unable to query Excel files without named regions.
Cause/Solution supported in Excel, when they are not. Although Toad displays the View tab in the Object Explorer based on the incorrect information, the tab remains blank and views cannot be created. Excel does not support procedures.
The Excel ODBC driver does not support this functionality. The worksheet you are querying does not have named regions defined. Solution: You can query the worksheet from the Editor by entering a dollar sign ($) followed by a cell range to limit the results similar to the following statement:
Select * from (MyWorksheet$A1:C10)
You can also query the entire worksheet by entering a dollar sign ($) after the worksheet name; however, this returns empty rows and columns in the worksheet. Unable to query data using an empty string or null value. The underlying data format cannot differentiate between an empty string and null data, so a query with a search condition that contains an empty string does not match any empty strings in the table. This occurs because the empty string is treated as a null value, and a null value never matches anything, not even another null value. The Excel ODBC driver does not support this functionality. While it is possible to update values, DELETE statements do not remove a row from a table. Basically, you can only insert data in a table. This error occurs if you have more than one named region in the same worksheet; and the named regions are not separated by a blank row. Solution: Add a blank row between named regions, or include only one named region in each worksheet.
Unable to update or delete rows in a table.
Attempting to insert data results in an error stating, "Cannot expand named range".
53
Web Browser Integration Issue Excel menus do not display when you open Excel files in the Web Browser. Cause/Solution The Web Browser cannot display Excel menus. Solution: Right-click the Excel toolbar and add the equivalent toolbar for the missing menu or functionality. The Web Browser supports one Excel instance at a time. Opening more than one Excel file disables the Excel toolbars for the additional files. Solution: Open only one Excel file at a time. Create Excel Connections (page 41)
When two or more instances of Excel are open in the Web Browser, toolbars are active for only one instance.
Troubleshoot DB2 LUW Issues

Review the following solutions to help troubleshoot DB2 LUW issues pertaining to Toad installation and database connections. Installation Issues The following table describes issues related to installing Toad for DB2. Issue System.IO.FileNotFoundException File or assembly name DB2AdminWrapper, or one of its dependencies was not found Cause/Solution You are not a member of the DB2ADMIN or DB2USERS group. To install Toad, you must be a member of either group. Solution: Ensure that you have been added to one of these groups. Cannot access IBM DB2 native tools after installing Toad for DB2 2.0 with previous install of DB2 client v7. Error: "SQL10007N Message "-1390" could not be retrieved. Reason code: "2"." Toad is bundled with the IBM DB2 v9 client. IBM does not support direct client migration from v7 to v9, so installing Toad on a system that has an existing v7 client may cause errors. Solution: Upgrade the IBM DB2 v7 client to the v8 client. If you upgrade the client after installing Toad, you do not have to uninstall or reinstall Toad.
54
Issue Error: "Could not load file or assembly 'IBM.Data.DB2.9.1.0, Version=9.1.0.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208' or one of its dependencies. The system cannot find the file specified."
Cause/Solution You installed a commercial version of Toad for DB2 after uninstalling the freeware version. Solution: You must remove run time information for the freeware version of Toad from the .NET system.config file. To remove run time information 1. Exit Toad. 2. Navigate to the following .NET framework directory: C:\WINDOWS\Microsoft.NET\ Framework\v2.0.50727\ CONFIG 3. Create a backup copy of the system.config file. 4. Open the system.config file in Notepad. 5. Locate the <runtime> tag delete everything between the runtime tags (including <runtime> and </runtime>). 6. Save the file. 7. Restart Toad.
55
Connection Issues Issue ERROR [08001] [IBM] SQL1336N The remote host was not found. SQLSTATE=08001 Cause/Solution You are attempting to connect to a database version that is not supported in Toad. Solution: Review the list of supported databases in the Release Notes or Installation Guide. ERROR [58031] [IBM] SQL1031N The database directory cannot be found on the indicated file system. SQLSTATE=58031 Catalog entries have not been imported or defined for the connection. Solution: See Configure DB2 Client Connections to determine the best method for cataloging a database. A settings file might be corrupt. Solution: Rename your local settings directory so a new one can be recreated. To rename your local setting directory 1. Exit Toad. 2. Navigate to the following settings directory: C:\Documents and Settings\ UserName\Local Settings\ApplicationData\Quest Software 3. Rename the Toad for DB2 version# folder to "Toad for DB2 OLD". 4. Restart Toad and try to connect. Note: Make sure you can view hidden folders in Windows Explorer.
"The type initializer for 'IBM.Data.DB2.DB2Connection' threw an exception." or "SUCCESS - unable to allocate an environment handle."
56
Troubleshoot DB2 z/OS Issues

Review the following solutions to help troubleshoot DB2 z/OS issues in Toad. Installation Issues Issue Error: "Could not load file or assembly 'IBM.Data.DB2.9.1.0, Version=9.1.0.2, Culture=neutral, PublicKeyToken=7c307b91aa13d208' or one of its dependencies. The system cannot find the file specified." Cause/Solution You installed a commercial version of Toad for DB2 after uninstalling the freeware version. Solution: You must remove run time information for the freeware version of Toad from the .NET system.config file. To remove run time information 1. Exit Toad. 2. Navigate to the following .NET framework directory: C:\WINDOWS\Microsoft.NET\ Framework\v2.0.50727\ CONFIG 3. Create a backup copy of the system.config file. 4. Open the system.config file in Notepad. 5. Locate the <runtime> tag delete everything between the runtime tags (including <runtime> and </runtime>). 6. Save the file. 7. Restart Toad.
57
Connection Issues Issue ERROR [08001] [IBM] SQL1336N The remote host was not found. SQLSTATE=08001 Cause/Solution You are attempting to connect to a database version that is not supported in Toad. Solution: Review the list of supported databases in the Release Notes or Installation Guide. ERROR [58031] [IBM] SQL1031N The database directory cannot be found on the indicated file system. SQLSTATE=58031 You do not have any catalog entries defined for the connection. Solution: See Configure DB2 Client Connections to determine the best method for cataloging a database. You do not have SYSADM privileges for the DB2 for z/OS subsystem. Solution: Ensure that you are granted SELECT permissions on the DB2 catalog tables. When using the Time-Sharing Option (TSO) to connect, the user ID, port number, or IP address entered may be incorrect. Solution: Ensure that you use the following for TSO connections:
l l
ERROR [42501] [IBM][DB2] SQL0551N "UserName" does not have the privilege to perform operation "SELECT" on object "SYSIBM.SYSSTMT". SQLSTATE=42501 ERROR [] [IBM] SQL1460N The environment variable "SOCKS_NS" required for SOCKS server name resolution is not defined or not valid.
DB2 user ID for the DB2 subsystem Port number that DB2 listens on, for remote connections, via the DB2 DDF address space IP address for the z/OS subsystem
58
Issue ERROR [56038] [IBM][DB2] SQL0969N There is no message text corresponding to SQL error "-4700" in the message file on this workstation.' when connecting to compatibility mode database. -orAfter connecting, some objects do not display properly or some functionality does not work as designed.
Cause/Solution In general, Toad does not support a z/OS subsystem running in Compatibility mode. Solution: If possible, switch the subsystem's operating mode to Full Function mode. If this is not possible, Toad now provides a message when you connect to subsystem, informing you of that the subsystem is running in compatibility mode and that some features might not be available.
Missing Functionality or Object Information Issue Unable to browse databases in DB2 for z/OS 8 or later. Cause/Solution The DB2 installation job DSNTISG defines a set of DB2 procedures that the ODBC driver uses. The installation assigns these procedures (namely, those beginning with SYSIBM.SQL*) to a specific Work Load Manager (WLM) environment, which currently might not exist or be defined properly. Solution: Be sure that you have correctly set up and enabled the WLM environment to which the procedure definitions point. Cannot edit data in compatibility mode. In compatibility mode, the ODBC driver does not return enough information for the CommandBuilder to correctly generate update or insert statements. Solution: No solution exists. However, when you connect to a subsystem running in compatibility mode, Toad now provides a message, informing you of this condition and warning you that some features might not be available.
59
Other Issues Issue [IBM][CLI Driver][DB2] SQL0104N An unexpected token "/*" was found following "". Expected tokens may include: "FROM INTO". SQLSTATE=42601 Cause/Solution The SQL script that you attempted to execute contains commented text delimited by characters that DB2 for z/OS 8 or earlier does not support. Solution: Set an option in Toad that removes comments automatically from a script before you execute it. To have Toad remove comments automatically from SQL before execution 1. Select Tools | Options | Database | DB2 | General. 2. Select Remove comments from SQL statements prior to execution.
Troubleshoot Informix Issues

Review the following solutions to help troubleshoot Informix issues in Toad. Issue Unable to view all available databases. Cause/Solution The InformixODBC driver does not return information about every available database.
Troubleshoot MySQL Issues

Review the following solutions to help troubleshoot MySQL connection issues pertaining to database connections and missing functionality or object information in Toad.
60
Connection Issues Issue "InvalidCastException" error when connecting to MYSQL 4.1.14-nt database Cause/Solution This is a known issue in MySQL. Solution: Review the known issue and download a patch from: http://bugs.mysql.com/bug.php?id=12771 Solution: 1. Exit Toad. 2. Locate the MySQL.xml file in the C:\Documents and Settings\username\Local Settings\ Application Data\Quest Software\ Toad for MySQLversion\ ModuleSettings 3. Rename or delete the MySQL.xml file. 4. Restart Toad. Missing Functionality or Object Information Issue Views tab is unavailable when connecting to MySQL using the ODBC driver Cause/Solution You are attempting to connect using the 3.51 ODBC driver. This driver is hard-coded to reply that the database does not support views because it needs to connect to MySQL databases prior to version 5. Solution: Use the native MySQL provider included in Toad Note: Although a beta version of the ODBC 5 driver resolves this issue, it is not recommended for use with production systems. If needed, you can download this driver from: http://dev.mysql.com/downloads/
"System.IO.DirectoryNot FoundException"error occurs each time you attempt to connect after installing Toad into a directory other than the default directory.
Troubleshoot Oracle Issues

Review the following solutions to help troubleshoot Oracle issues pertaining to database connections and missing functionality and object information in Toad.
61
Connection Issues Issue Attempting to connect when Oracle Instant Client is installed results in a System.NullReferenceException error Cause/Solution Solution: In order to connect using the Oracle Instant Client, the directory for the Instant Client must be included in the environmental path, or you must copy the client files for the instance to the root install directory of Toad for Data Analysts. You can also connect to the database without using an Oracle client or TNSNames file by selecting the Direct tab in the Create New Connection window. Unable to select a 64-bit Oracle client from the Current home field in the Oracle Client tab An error occurs when attempting to connect to Oracle Rdb using an ODBC driver. Toad runs as a 32-bit application, even when installed on a 64-bit O/S. Because it is a 32-bit application, Toad is not compatible with 64-bit Oracle clients. Toad does not support Oracle Rdb at this time.
Missing Functionality and Object Information Issue Some schemas are not available from the Schema drop-down list in the Object Explorer. Unable to view table data on the Data tab; SQLFetch generates an access violation. Cause/Solution The Oracle ODBC driver cannot display schemas that do not have any tables. The Oracle ODBC driver is accessing unallocated memory. Solution: Update the Oracle ODBC driver:
l l
For 9i drivers, update to 9.2.0.7.0 or later. For 10g drivers, update to 10.1.0.3.0 or later.
62
Troubleshoot SQL Server Issues

Review the following solutions to help troubleshoot SQL Server connection issues in Toad. Issue Cannot specify a port number when connecting Cause/Solution Currently, Toad does not have a separate field for specifying a port number. Solution: You can connect if you know the port number for the instance by entering the following in the Server name field on the New Connection window: ServerName,Port or IPAddress,Port For example: 10.1.29.129,1234 (where 1234 is the port number of the instance) Cannot connect to a remote instance in SQL Server 2005 Remote connections may not be enabled in SQL Server 2005. Also, named instances are configured to use dynamic ports and select an available port once the SQLServer Service starts. If you are connecting to a named instance through a firewall, configure the Database Engine to listen on a specific port, so that the appropriate port is opened in the firewall. Note: Remote connections are disabled by default in the Express and Developer editions of SQL Server 2005. Solution: To enable remote connections, see "How to configure SQL Server 2005 to allow remote connections" at: http://support.microsoft.com/kb/914277
63
Issue "Path is not of a legal form" error message when connecting or "Could not find a part of the path C:\Program Files\Quest Software \Toad for SQL Server\Template\Scripts\ InitialSqlServer.Sql" error message when connecting
Cause/Solution You attempted to migrate settings from a previous install of Toad to the current install, but the settings file (InitialSqlServer.Sql) for the previous install was either removed, moved, or corrupt. You may also receive this error if you installed Toad and migrated settings from a previous version, and later uninstalled the previous version. Solution: You must specify a valid location for the InitialSqlServer.Sql file in Toad. To specify a valid location 1. Open the SQL Server options page under Tools | Options | Database | SQL Server. 2. Specify the location for the new install's InitialSqlServer.Sql file in the Run Script on new connection field. By default, this file is located in the following directory: C:\Program Files\Quest Software\Toad for SQL Server version# \Templates\Scripts Note: Clicking may result in a "Path not found error". If you receive this error, manually enter the location in the field.
Troubleshoot Sybase ASE Issues

Review the following solutions to help troubleshoot SybaseASE issues pertaining to the following in Toad:
l
Database connections Missing functionality or object information Other issues
Connection Issues Issue Unable to connect to the database. The following message displays: "The ODBCMDA procedures have not been installed on this database..." Cause/Solution Stored procedures that the ODBC driver requires currently do not exist on the server. Solution: Install the required procedures.
64
Missing Functionality or Object Information Issue Unable to view or export data for objects with non-standard names. Cause/Solution Sybase ODBC driver has issues handling nonstandard names for objects. Solution: When setting up a Sybase connection in Toad, select Use quoted identifiers on the Connection tab in the Adaptive Server Enterprise window to enable the use of quotations in identifiers. Unable to view linked tables. Linked tables store DSN connection information. Solution: Set up the DSN connection information exactly the same on all machines that access the database. Other Issues Issue DBMS name showing as SQL Server. Cause/Solution Older versions of the Sybase ODBC driver return SQL Server as the DBMS name. Solution: Upgrade to the latest version of the Sybase ODBC driver, which correctly returns Adaptive Server Enterprise as the DBMS name.
Configure Version Control

About Version Control
Toad integrates with your existing version control system so you can maintain multiple revisions of files. Important: See "Troubleshoot Version Control" (page 72) for more information about issues when upgrading version control from a previous version. Prerequisites You must install a supported version control client on the computer where Toad is installed. The following table lists the supported version control providers and the versions tested with Toad.
65
Supported Provider Visual SourceSafe (VSS) Concurrent Versions System (CVS) Subversion
Server Version Tested VSS 6.0d
Client Version Tested VSS 6.0d See "Configure TFS or VSS" (page 66) for more information.
CVS 1.11.22 on Solaris CVSNT 2.5.03 on Windows Subversion 1.5.6 on Windows Note:Toad only supports Subversion 1.5.6 or later.
CVSNT 2.5.03 See "Configure CVS " (page 68) for more information. CollabNet Subversion Command-Line Client 1.5.6 Notes:
l
Toad only supports Subversion 1.5.6 or later. Any Subversion client must have svn.exe in its installation directory to use version control in Toad. Tortoise SVN is no longer supported in Toad because it no longer includes svn.exe in its installation directory.
See "Configure Subversion" (page 70) for more information. Team Foundation Server (TFS) TFS 2005, 2008 Visual Studio (2005 and 2008) Team Explorer Client See "Configure TFS or VSS" (page 66) for more information.
Note: Toad connects to your version control system based on login information included in the configuration. Your version control client does not need to run for Toad to connect.
66
Configure TFS or VSS

You can configure version control to work with SQLscripts in the Editor. See "Troubleshoot Version Control" (page 72) for more information. To configure TFSor VSS to work with SQLscripts in the Editor 1. Ensure that a supported version control client is installed on the computer where Toad is installed. See "Configure Version Control" (page 64) for more information about tested version control clients and supported versions. 2. Open an Editor window. 3. Right-click anywhere in the toolbar area and select Version Control to display the Version Control toolbar. Tip:You can also access version control functionality from the File |Version Control menu when the Editor window has focus. 4. Click to open the Version Control wizard.
5. Review the following for additional information: Version Control System Page Type Description
Select either Team Foundation Server or Visual SourceSafe. Note: If you select TFS, you must specify the workspace name for the provider in the Team Foundation Server Properties window that displays.
Properties
(TFS only) Click this button (beside the Type field) and specify the workspace name for the provider in the Team Foundation Server Properties window. Select one of the following:
l
Server
For TFS, specify the server where your version control provider is installed and the port number (default is 8080) to use in the following format: http://MyServer:Port For VSS, select the folder where the Source Safe client is installed and the srcsafe.ini file (for example: C:\SourceSafe\VSS\srcsafe.ini).
67
User name/ Password
Enter login information for the version control provider and click Login. Note: For TFS only, if you leave the user name and password fields blank, Toad uses your default Windows credentials. Description
Version Control Settings Page Version control folder
Select the folder on the version control server where you want to check scripts in. If you already have scripts under version control, select the folder on the server where these scripts are located. Notes:
l
Version control automatically checks out scripts in this folder and any subfolders to the location you specify in the Working folder field.
Working folder
Select the folder to use as the default working folder. If you already have objects under version control, select the working folder for these objects.
6. Tips:
l
See "Add Scripts Using the Editor" in the Toad help for more information.
You can view revision history and revision comments for a scipt from the History tab; and can also right-click a revision to send it to the Diff Viewer to compare differences.
You can enable, disable, or delete a version control configuration under Tools | Options | Version Control |General. You can modify current settings, including whether to require comments when checking objects and scripts in or out, avoid checking scripts in automatically when executing a script in the Editor, disable or delete a version control configuration, etc., from Tools | Options | Version Control |<options page> .
68
Configure CVS
You can configure version control to work with SQLscripts in the Editor. See "Troubleshoot Version Control" (page 72) for more information. To configure CVS to work with SQLscripts in the Editor 1. Ensure that a supported version control client is installed on the computer where Toad is installed. See "Configure Version Control" (page 64) for more information about tested version control clients and supported versions. 2. Open an Editor window. 3. Right-click anywhere in the toolbar area and select Version Control to display the Version Control toolbar. Tip:You can also access version control functionality from the File |Version Control menu when the Editor window has focus. 4. Click to open the Version Control wizard.
5. Review the following for additional information: Version Control System Page Type Properties Description
Select CVS. Click this button (beside the Type field) and complete the following in the Command Based Version Control Properties window:
l
BinaryPathEnter the path where the CVS client is installed. For example, if you installed CVSNT, you would enter: C:\Program Files\CVSNT BranchRevisionLeave this field blank if you are working from the trunk in version control. If you are working from a branch, enter the branch number or name in this field. Caution: Specifying HEAD for the BranchRevision parameter can cause errors. Leave the parameter blank when working with the HEAD revision.
Server
Select the existing working folder for the version control repository or specify the server string. For example, if you are connecting using pserver, you should specify the server string as follows:
69
:pserver:MyServer:Port:/MyWorkingRepository User name/ password Default Version Control Settings Page Version control folder Enter your CVScommand-line user name and password and click Login. Note:The User name field is optional. Description
l
Working folder
Select the root repository folder on the client computer to use as the default working folder for checking SQLscripts out. If you already have SQLscripts under version control, select the existing working folder for these.
6. Tips:
l
See "Add Scripts Using the Editor" in the Toad help for more information.
You can enable, disable, or delete a version control configuration under Tools | Options | Version Control |General. You can modify current settings, including whether to require comments when checking objects and scripts in or out, avoid checking scripts in automatically when executing a script in the Editor, disable or delete a version control configuration, etc., from Tools | Options | Version Control |<options page> .
70
Configure Subversion
You can configure version control to work with SQLscripts in the Editor. See "Troubleshoot Version Control" (page 72) for more information. To configure Subversion to work with SQLscripts in the Editor 1. Ensure that a supported version control client is installed on the computer where Toad is installed. See "Configure Version Control" (page 64) for more information about tested version control clients and supported versions. 2. Open an Editor window. 3. Right-click anywhere in the toolbar area and select Version Control to display the Version Control toolbar. Tip:You can also access version control functionality from the File |Version Control menu when the Editor window has focus. 4. Click to open the Version Control wizard.
5. Review the following for additional information: Version Control System Page Type Properties Description
Select Subversion. Click this button (beside the Type field) and complete the following in the Command Based Version Control Properties window:
l
BinaryPathEnter the path where the Subversion client that contains svn.exe is installed. For example, if you installed the CollabNet Subversion Client, you would enter: C:\Program Files\CollabNet Subversion Client Note: Do not include svn.exe in the path.
BranchRevisionLeave this field blank if you are working from the trunk in version control. If you are working from a branch, enter the branch number or name in this field. Important: Specifying HEAD for the BranchRevision parameter can cause errors. Leave the parameter blank when working with the HEAD revision.
71
Server
Select the existing working folder for the version control repository or specify the server string (for example: svn://MyServer). Enter your Subversion command-line user name and password and click Login. Description
User name/ Password Default Version Control Settings Page Version control folder
l
Working folder
Select the root repository folder on the client computer to use as the default working folder for checking SQLscripts out. If you already have SQLscripts under version control, select the existing working folder for these.
6. See "Add Scripts Using the Editor" in the Toad help for more information. Tips:
l
You can enable, disable, or delete a version control configuration under Tools | Options | Version Control |General. You can modify current settings, including whether to require comments when checking objects and scripts in or out, avoid checking scripts in automatically when
72
executing a script in the Editor, disable or delete a version control configuration, etc., from Tools | Options | Version Control |<options page> .
Troubleshoot Version Control

Troubleshoot Upgrades For this release, the back-end of version control has been rewritten. If you previously used version control in Toad, the following may occur:
l
If you migrate settings when upgrading Toad, you may have to reconfigure the repository setting in version control if a "Failed to open the settings for module VersionControl reverting to defaults" error displays. To reconfigure the repository, select Tools |Options |Version Control |Defaults and select the previous repository in the Version control folder field. Your previous project settings are applied. In previous releases, the method Toad used to generate the script was different than the current method. After upgrading Toad, a message may display stating that files in version control are different than the local version. If your local version is current, you should check the files into version control.
73
Troubleshoot Other Issues Review the following to help troubleshoot issues with version control: VSSIssues Language support Description VSS 6.0 uses ANSI strings. Consequently, the English-encoded VSS server and client do not handle certain characters in other languages. This issue may also exist on previous or later VSS language installations. VSS is not case-sensitive. Using version control on objects whose names differ by case only can cause history and version-tracking issues. Description If a message stating that, The system cannot find the file specified displays, this usually means that the CVS executable cannot be found in the path you specified in the BinaryPath field of the Command Based Version Control Properties window. Verify that cvs.exe exists in the directory you specified in this field When executing CVS commands, user input is not allowed. This presents an issue when the user is using CVS with the SSH method and must enter a password to establish the Secure Shell. Workaround: Generate identity keys that automatically authenticate between the client and the server when connecting with SSH. Subversion Issues System cannot find file Description If a message stating that, The system cannot find the file specified displays, this usually means that the Subversion executable cannot be found in the path you specified in the BinaryPath field of the Command Based Version Control Properties window. Verify that svn.exe exists in the directory you specified in this field When executing Subversion commands, user input is not allowed. This presents an issue when the user is using Subversion with the SSH method and must enter a password to establish the Secure Shell. Workaround: Generate identity keys that automatically authenticate between the client and the server when connecting with SSH.
Case insensitive CVS Issues System cannot find file
Command execution
Command execution
Appendix: Contact Quest

Contact Quest Support
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to SupportLink, our self-service portal. Visit SupportLink at http://support.quest.com. From SupportLink, you can do the following: Retrieve thousands of solutions from our online Knowledgebase Download the latest releases and service packs Create, update and review Support cases View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures. The guide is available at: http://support.quest.com.
Contact Quest Software

Email info@quest.com Quest Software, Inc. World Headquarters Mail 5 Polaris Way Aliso Viejo, CA 92656 USA Web site www.quest.com
See our web site for regional and international office information.
About Quest Software

Now more than ever, organizations need to work smart and improve efficiency. Quest Software creates and supports smart systems management productshelping our customers solve everyday IT challenges easier and faster. Learn more at www.quest.com.
Oracle
60 63 53 56 62 47 74 8 19 68 D
Index
A Access create connections troubleshoot C Citrix installation requirements client requirements configure Toad connections configure DB2 client create Access Excels MySQL ODBC Oracle SQL Server Sybase ASE DB2 LDAP support Oracle LDAP support share for all session windows troubleshoot Access Informix 40 41 42 43 22 45 46 26 22 48 62 48 59 27 15 5 1 19 40 48
Sybase ASE troubleshoot DB2 LUW troubleshoot DB2 z/OS troubleshoot SQL Server understand contact support corporate deployment customize Toad CVS, configure
DB2 troubleshoot LUW issues troubleshoot z/OS issues E Excel create connections troubleshoot I Informix, troubleshoot installation Citrix client requirements server requirements silent user privilege requirements installation, read-only 59 6 5, 15 1 2 8 5 7 41 49 53 56
Toad for Data Analysts Installation Guide Index
76
L LDAP DB2 support Oracle support look and feel configuration M MySQL create connections troubleshoot O ODBC create connections Oracle create connections troubleshoot R read-only installation register Toad requirements Citrix client server user privilege S server requirements 2 5 1 2 5 7 18 22 60 43 42 59 26 22 19
shortcut keys configure to match other applications silent installation create transform file determine installer to use executable Microsoft installer (MSI) prerequisites SourceSafe, configure SQL Server troubleshoot SQLServer create connections Subversion, configure Sybase ASE create connections system requirements T Team Foundation Server, configure TFS, configure Toad customize transform file troubleshoot DB2 LUW connections DB2 z/OS connections Excel Informix issues 53 56 49 59 19 11 66 66 46 1 45 70 62 19 8 11 8 9 11 9 66
Toad for Data Analysts Installation Guide Index
77
MySQL Oracle connections SQL Server connections version control tutorials create ODBC connections U uninstall Toad user privilege requirements V Version Control configure CVS configure Subversion configure TFS configure VSS troubleshoot Visual SourceSafe, configure VSS, configure
59 60 62 72
43
18 5
64 68 70 66 66 72 66 66

Toad InstallGuide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Toad InstallGuide

Uploaded by

Copyright:

Available Formats

Toad for Data Analysts

Toad for Data Analysts 2.6 Installation Guide February 2010

Toad for Data Analysts Installation Guide Installation

Component .NET Framework

Toad for Data Analysts Installation Guide Installation

Requirement SQL Server Native Database Provider

DB2 for z/OS Native Database Provider

DB2 for LUW Native Database Provider

MySQL Native Database Provider

Toad for Data Analysts Installation Guide Installation

Component Native Database Support

Requirement Toad supports the following databases:

ODBC Database Support

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Install Toad Silently

Determine Which Installer to Use

Supports deployment of Toad settings files and license keys.

Silent installation using an msi file has the following disadvantages:

Toad for Data Analysts Installation Guide Installation

Silent Installation Prerequisites

Silent Installation Using the Executable

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Description (Optional) Specify one of the following values:

Silent Installation Using the Microsoft Installer

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

File to Add ModuleSettings folder and files

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Installation

Description (Optional) Specify one of the following values:

Install Toad on Citrix Systems

Toad for Data Analysts Installation Guide Installation

Files Migrated During Upgrades

Connections.xml ConnectionTrace.log ExceptionTrace.log FTPConnection.log FTPConnections.xml Settings.xml SqlServerPlanPrefs.xml ToadSupportBundle.zip Folder

Toad for Data Analysts Installation Guide Installation

Automation (temporary folder) Cache

CNSScripter (temporary folder) Context

Plugins Session SQLFormatter

Toad for Data Analysts Installation Guide Installation

Toad for Data Analysts Installation Guide Configuration

Use this page...

To.... Explorer, Editor, and Code Snippets windows.

Specify the following options:

Toad for Data Analysts Installation Guide Configuration

Use this page...

Wizard Bar Additional Settings

Toad for Data Analysts Installation Guide Configuration

Create Oracle Connections

Toad for Data Analysts Installation Guide Configuration

Toad for Data Analysts Installation Guide Configuration

Variable name PATH

< Path where tnsnames.ora file is installed>

Schema Explain plan table

Toad for Data Analysts Installation Guide Configuration

Save password Oracle Client Tab Current home TNSNames Editor

Direct Tab SID Name

Advanced Tab ODBC driver

Toad for Data Analysts Installation Guide Configuration

Configure DB2 LDAP Support