Toad for DB2 is a database development and administration solution that provides productivity features for rapidly creating and executing queries, automating database object management, developing SQL code, and instant access to DB2 expertise.

Developers and administrators have access to a community of users, peers, and experts to help solve development and administration issues and assist in developing applications and feedback for improving Quests products.

All of this comes with the backing of Quest Software, a healthy and growing corporate entity that can provide the necessary training, support, and superior customer service demanded by IT management.

Top

New in this Release

Log Reader for DB2 LUW

Log Reader for DB2 LUW is a SQL data-auditing and data-recovery tool. It analyzes the transaction log for a DB2 for LUW database to display information about the data and object-structure changes that have occurred in the database and to provide a means to redo or undo individual commands or transactions. You can access the Log Reader from the Tools menu in Toad.

Top

System Requirements

Verify that your system meets the following minimum requirements.

Hardware Requirements

Software Requirements

Database Requirements

User Privilege Requirements

The following user privileges are required for installing and running Toad:

• Only Power users and Administrators can install Toad.

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

• If a Power user installs Toad, a Restricted user can run the application but cannot see the Toad for DB2 icon on the desktop or the Toad for DB2 menu options in the Windows Start menu. As a workaround, Restricted users can create a shortcut to the application from the install directory and place the shortcut on their desktop .

• If an Administrator installs Toad, the Administrator can share the Toad for DB2 desktop icon and menu items with any user on the computer.

• Network and LAN installations are currently not supported.

• In order to use Toad with a DB2 mainframe, any user who does not have SYSADM privileges must be granted SELECT permissions on the DB2 catalog tables.

• In order to set or modify Toad Security settings, users must have privileges to create the QuestSoftware.ToadSecurity table if it does not exist. If the table does exist, users must have privileges to insert, update, and delete data in the QuestSoftware.ToadSecurity table.

Citrix Requirements

Toad has been tested for Citrix support using the Metaframe Access Suite 3.0 on Windows Server 2003 operating system. For information about installing Toad in a Citrix environment, refer to Install Toad for DB2 on a Citrix Machine in the Getting Started Guide.

LDAP Requirements

To connect to a Lightweight Directory Application Protocol (LDAP) server, you must enable LDAP support and specify the host name and port number of the LDAP server for the DB2 client installed with Toad.

Note: You must configure LDAP support for the DB2 client installed with Toad regardless of whether an existing DB2 client on the machine is already configured to support LDAP.

To configure Toad to use 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. Type the following command to enable LDAP support:
   
   db2set DB2_ENABLE_LDAP=YES

3. Type 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 New Connection window.
   
   Databases on the LDAP server should be available from the Database Alias drop-down list.

Note: At this point, Toad for DB2 supports only the access of DB2 LDAP catalog entries. Toad does not support the management of these entries (such as adding or removing them).

Log Reader for DB2 LUW Requirements

Note: The Log Reader is currently available for DB2 for LUW version 8.x databases only.

For each DB2 for LUW database on which you intend to use the Log Reader, the following requirements must be met:

Required Database Configuration Parameters

The Log Reader requires that either or both of these database configuration parameters be set as follows for the database:

• Set LOGRETAIN to RECOVERY. Additionally, if you want to specify an archive location other than the default directory for storing log files for the database, specify this location for the LOGARCHMETH1 database configuration parameter.

• Set USEREXIT to YES. Additionally, to use the user exit, you need to set the LOGARCHMETH1 database configuration parameter to USEREXIT and to set up the user-exit program appropriately.

If you update either parameter, you must back up the database after the update.

For information about updating these database configuration parameters, setting up a user-exit program, and backing up the database, refer to your IBM DB2 for Linux, Unix,and Windows documentation.

Optional Table Option

Enable the DATA CAPTURE CHANGES option for each database table for which you want the Log Reader to perform these functions:

• Reconstruct the SQL to undo or redo any UPDATE command performed on the table. (DATA CAPTURE CHANGES saves the affected data to the log before and after the UPDATE takes place.)

• Provide information about the user that issued each UPDATE command on the table.

You can enable this option for an existing table using the ALTER TABLE command.

Required Authorities

The user must have the following authorities to load the log files for a Log Reader session:

• READ permissions on the log files belonging to the database and on the directory where these files are stored

• Database administrator privileges to read the database's log

Size Limitation for Log Files

The amount of log data that the Log Reader can parse depends on the memory available on the client machine. The recommendation is that the Log Reader loads one or more log files whose combined total size is not greater than 100 MB.

Top

Installation Notes

General Information

Please review installation and upgrade information in the Getting Started Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 2.5 | Documentation.

Silent Installation

Use the following procedure to install Toad for DB2 in silent mode on Windows machines. Silent installation provides a convenient method for pushing Toad for DB2 onto multiple machines that use the same Toad for DB2 installation options and macros or that require the same installation directory path.

Note: If a version of Toad for DB2 already exists on the target machine, the silent installation program uninstalls this previous installation and then proceeds to install the current version.

To install Toad for DB2 in silent mode

1. At a Windows command prompt, switch to the drive or directory where the self-extracting installation executable for Toad for DB2 is located. (This .EXE file can be downloaded from the Quest web site or is found on the Toad for DB2 installation CD-ROM.)

2. Enter the following command. Use the descriptions below to customize the command options and macros as necessary for your site:
   
   Toad_for_DB2_installation_filename.exe /S /Lx "c:\temp\installLog.txt" INSTALLDIR="C:\Program Files\Quest Software\Toad for DB2 2.5" USERNAME="user name" COMPANYNAME="company name" ApplicationUsers="AllUsers"
   
   Note: All command options and macro keywords are case-sensitive.

• Substitute Toad_for_DB2_installation_filename.exe in the example with the exact name of the Toad for DB2 self-extractable installation file.

• Include /S to indicate that the installation will run in silent mode.

• Include /L (an MSIEXEC option) to indicate that installation messages will be written to the specified log. You can append other MSIEXEC options, such as x for debug (used in the example above) or v for a verbose log.

• 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 will create this file if it does not exist. Otherwise, the file is overwritten.  

• Provide the following macros in the command line. If you do not include the required macros, the installation program uses the default values indicated. Enclose each macro value in double quotations.

INSTALLDIR--Specify the absolute path for the directory in which you want to install Toad for DB2. If you do not include this macro, the installation program defaults to the "C:\Program Files\Quest Software\Toad for DB2 2.5" value.

USERNAME--(Optional) Provide the user ID that intends to use the Toad for DB2 on the target machine. If "OnlyCurrentUser" is defined for the ApplicationUsers macro (described below), only the user ID specified here (and the ID that installed Toad) can see the Toad for DB2 shortcut on the target machine desktop after the installation is completed. If "OnlyCurrentUser" is defined but USERNAME is not included in the installation, only the user ID that installed Toad sees the Toad for DB2 shortcut on the target machine desktop. If "AllUsers" is defined for ApplicationUsers, the USERNAME macro is ignored during installation.

COMPANYNAME--(Optional) Provide the name of the company that owns this installation.

ApplicationUsers--Specify either value. If you do not include this macro, the installation program defaults to AllUsers.

"AllUsers" allows any user ID to see the Toad for DB2 shortcut on the target machine desktop after installation is completed.

"OnlyCurrentUser" allows only the user ID specified for USERNAME and the user ID that installed Toad to see the Toad for DB2 shortcut on the target machine desktop. If USERNAME is not included in the installation, only user ID that installed Toad sees the shortcut.

Running Toad with DB2 for LUW Version 9 FixPak 1

If you upgraded IBM DB2 for LUW version 9 from FixPak 0 to FixPak 1, specifying the Work with Existing option, Toad for DB2 might issue an exception error when you try to establish a database connection. The error message is similar to the following: "The type initializer for 'IBM.Data.DB2.DB2Connection' threw an exception."

To resolve this issue, remove the 9.1.0 dependent Assembly section from the machine.config (a .Net file).

To remove the 9.1.0 dependent Assembly section from machine.config

At a Windows command prompt, run the following command:

db2nmpcfg -unregister -level 9.1.0

Top

Global Operation

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Far-East Asia, Japan.

This release has the following known capabilities or limitations:

• Toad Editions that contain Knowledge Xpert.
  The Knowledge Xpert feature is available with English language content only.

Top

Enhancements and Resolved Issues

Version 2.5

The following enhancements and resolved issues have been implemented in this release of Toad for DB2.
 

Version 2.0.1

The following enhancements and resolved issues have been implemented in this release of Toad for DB2.