Chat now with support
Chat with Support

Toad for DB2 6.5 - Installation Guide

Installation

System Requirements

Review the following client and database server requirements for Toad® for IBM® DB2®.

Client Requirements

Before installing Toad, ensure that your client system meets the following minimum hardware and software requirements:

Requirement Details

Platform

2 GHz processor (recommended minimum)

Memory

4 GB of RAM minimum, 16 GB recommended

Note: The memory required may vary based on the following:

  • 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

Hard Disk Space

162 MB to run Toad

Note: The disk space required may vary based on the edition of Toad selected for installation.

Operating System

Windows Vista® Service Pack 2 (32-bit or 64-bit)

Windows Server® 2008 Service Pack 2 (32-bit or 64-bit)

Windows Server® 2008 R2 Service Pack 1 (64-bit)

Windows Server® 2012

Windows Server® 2012 R2

Windows Server® 2016

Windows® 7 (32-bit or 64-bit)

Windows® 8 (32-bit or 64-bit)

Windows® 8.1 (32-bit or 64-bit)

Windows® 10

.NET Framework

Microsoft® .NET Framework 4.5.1

Database Client

When connecting to a DB2 database/subsystem, ensure that you have a DB2 Client or IBM Data Server Driver installed. Toad supports DB2 Client versions 9.7.6 through 11.1.

Toad has been tested with the following versions of the DB2 Client: 9.7.6, 9.7.9 , 10.1.0, 10.1.2, 10.1.3, 10.5.0, 10.5.2, 10.5.3, and 11.1.0.

Additional Requirements

Web Browser

Microsoft® Internet Explorer® 7.0 or later

Screen

Toad supports screen resolutions up to 3200 x 1800 and display DPI settings up to 150%

Server Requirements

Before installing Toad, ensure that your server meets the following minimum hardware and software requirements:

Requirement Details

Database Server

IBM DB2 for LUW 9.5, 9.7, 10.1, 10.5, 10.5.0.5, 11.1

IBM DB2 for z/OS 9, 10, 11, 12

Note: Toad may support IBM DB2 Express and SWE in addition to listed above servers, but note that no testing was performed on it.

Note: Windows 8, 10 and Windows Server 2012 require the following Fix Pack in order to ensure registration of DLLs in Global Assembly Cache:

IBM DB2 LUW 10.5 Fix Pack 4
IBM DB2 LUW 10.1 Fix Pack 4
IBM DB2 LUW 9.7 Fix Pack 10

Virtualization Support

Requirement Details
Application Virtualization

When deploying Toad Data Point in a virtualization environment, for best results ensure the system accurately reflects the applicable client hardware and software requirements listed in this document.

Toad Data Point has been developed using Microsoft guidelines (see Remote Desktop Services programming guidelines) and can be deployed and operated in virtualization environments such as Citrix XenApp, Microsoft App-V, and VirtualBox.

See Install Toad on Citrix® Systems 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:

  •  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.
  • 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:

  • 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:

  • 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.
  • 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 Vista’s 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.)

  • 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.
  • To take full advantage of Toad for DB2 LUW functionality, the user ID specified in the Toad connection profile for each DB2 for LUW database connection requires the authorizations listed in the following document:

    ToadDB2LUWAuthorizations.xls

  • 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. For a complete list of authorizations (and corresponding GRANT statements) a user requires to take full advantage of Toad for DB2 z/OS functionality, refer to the following document:

    ToadDB2zOSAuthorizations.doc

  • 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.
  • For information about defining a RACF, Unix, or Linux group as a Toad Security role, see the About Setting Up Toad Security topic in the Toad online help. This topic explains how to add the Toad Security icons to your toolbar and how to define Toad Security roles that apply to your current connection. (The ability to define RACF, Unix, and Linux groups as Toad Security roles works with DB2 for LUW 9 or later databases and DB2 for z/OS 8 or later subsystems.)

Requirements for Full Access to Toad for DB2 z/OS Functionality

Install the following components on each DB2 for z/OS subsystem:

  • Toad for IBM DB2 z/OS Components

    Notes:

    • Without the z/OS components installed, Toad for IBM DB2 provides limited support for managing DB2 for z/OS subsystems. With the z/OS component installed, you have access to a full range of Toad functionality needed to manage DB2 subsystems.

      See Install Other Toad Components for more information.

    • If no Toad for IBM DB2 z/OS components are installed on your subsystem, see the Toad for IBM DB2 z/OS Components Installation Guide for installation requirements and instructions.
  • IBM stored procedure SYSPROC.DSNUTILU, installed and operational.

    Notes:

    • Toad requires SYSPROC.DSNUTILU to run DB2 utilities. For more information about this stored procedure, see Appendix B of the IBM DB2 Universal Database for z/OS Utility Guide and Reference.
    • A 32K character-size limit exists for each utility statement executing through DSNUTILU.
  • Certain table alterations require that Toad perform advanced alters involving multiple UNLOADs and LOADs of table data. Before executing these types of alterations, ensure that the Mask value defined for the Toad dataset template that generates the Unload datasets includes the &SEQ variable. This variable creates a unique name for each Unload dataset. (The Unload dataset template is identified in Tools | Options | Database | DB2 | z/OS | Load/Unload.)
  • When Toad migrates data from one subsystem to another, Toad invokes the IBM DB2 for z/OS UNLOAD and LOAD utilities. Ensure that the Reorg Unload dataset template (identified in Tools | Options | Database | DB2 | z/OS | Reorg) generates a dataset that resides on a pack (VOLSER) accessible by both the source and target subsystem.

Compile and Debug Requirements for Stored SQL Procedures

Toad requires the following to compile and debug stored SQL procedures in DB2.

  • DB2 for LUW Requirements

The following is required to debug and compile stored SQL procedures on DB2 for LUW databases:

Component Requirements
Supported DB2 Versions DB2 for LUW 9 or later
Each DB2 Database IBM SYSPROC.DBG_% procedures, installed and operational
Privileges On each DB2 database, EXECUTE authority on all SYSPROC.DBG_% procedures
  • DB2 for z/OS Requirements

The following is required to debug and compile stored SQL procedures on DB2 for z/OS subsystems:

Component Requirements
Supported DB2 Versions DB2 for z/OS 9 to 11
Each DB2 Subsystem
  • IBM DB2 stored procedure SYSPROC.DSNTPSMP, installed and operational (needed to compile stored procedures in Toad)
  • IBM DB2 installation job DSNTIJSD, executed (needed to debug stored procedures)
  • IBM SYSPROC.DBG_% procedures, installed and operational
z/OS

IBM Unified Debugger Session Manager, installed and configured:

DB2 for z/OS

  1. Install and configure DB2UDSMD (the Debugger Session Manager).
  2. Start task DB2UDSMD, using default port number 4553.

Refer your systems administrator to the following link for instructions on installing and configuring DB2UDSMD:

http://www.ibm.com/developerworks/data/library/techarticle/dm-0903debugdatastudio/

Privileges
  • On each DB2 subsystem, EXECUTE authority on all SYSPROC.DBG_% procedures
  • DEBUGSESSION system privilege (for continued debugging of SQL procedures)

 

Install Toad

Toad for IBM DB2 is available in the following editions: Base, Professional and Xpert. DB Admin Module is an add-on module that provides extended admin functionality and can be added to any Toad edition.

Note: Your Toad for IBM DB2 license key determines the edition and will enable Toad for IBM DB2 functionality accordingly. In many cases, if functionality is disabled within Toad for IBM DB2, you may not have an appropriate license to use it. When Toad is running, you can see which components are licensed by selecting Help | About.

To install Toad

  1. Run the Installer.
  2. Accept the License Agreement.

  3. Select the products you want to install and click Install.

    Note: When installing Toad using Quest Software Installer on Windows 7 64-bit, Program Compatibility Assistant may appear with “This program might not have installed correctly” message. Select This program installed correctly to continue installation.

Note: Check Prohibit saving passwords during the installation to prohibit users from saving their passwords in Toad.

Specify App Data Directory Location

Toad for IBM DB2 6.5 stores settings files in the user's Application Data directory. The default location cannot be modified from within the application. Toad provides two methods to change the default location: by using a Registry setting or by using a command switch in a Toad shortcut.

Use the Registry setting method to change the application data directory from Roaming to Local. Use the command switch method to change the location to any new path.

To change Toad Application Data directory location from Roaming to Local

In the Registry under Toad for IBM DB2 (Computer\HKEY_CURRENT_USER\Software\Quest Software\Toad for IBM DB2\6.5), add LOCALSETTINGS with a value of 1.

See the following table for default (Roaming) and resulting (Local) directory path.

Caution: All current Toad settings will be lost after applying this Registry setting unless you manually copy the settings files from the default location (Roaming directory) to the new location (Local directory). Copy the settings files BEFORE you add the Registry setting and BEFORE opening Toad.

Operating System

Default Location New Location when
LOCALSETTINGS = 1

Windows Vista

Windows Server 2008

Windows 7

C:\Users\username\ AppData\Roaming\Quest Software\Toad for IBM DB2 6.5

C:\Users\username\ AppData\Local\Quest Software\ Toad for IBM DB2 6.5

To change Toad Application Data directory location using a command-line switch

You can override the default Application Data directory by running Toad with the command switch:

Toad.exe --datadir="YourNewDirPath"

To instruct Toad to always use the new directory path, add the command switch and the new directory path to a Toad desktop shortcut. Then use the desktop shortcut when opening Toad.

  1. To add the command switch, right-click the Toad shortcut and select Properties.
  2. Enter the command switch and add the directory path in quotes (replace "YourNewDirPath" with your directory path).
Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents