Toad^® for IBM DB2

Version 4.6 (Click here for previous versions)

Release Notes

February 2010

Contents

Welcome to Toad for DB2

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.

Back to Top

New in This Release

Click to review updates and new features in the following areas:

• Support for DB2 for LUW 9.7 Features
• Prerequisites and Installation
• General Toad Environment
• Connections
• Automation
• Database Administration
• Space Management
• Data Management
• Query Development
• Project Management

Back to Top

Support for DB2 for LUW 9.7 Features

Toad provides the following support for DB2 for 9.7 features:

• View registry values for the current database by accessing the Registry Variables tab on the right side of the Database node in the Database or Object Explorer. For a DB2 for LUW 9.7 connection, you can see the details of the new DB2_COMPATIBILITY_VECTOR registry variable.

• In the Database or Object Explorer for a DB2 for LUW 9.7 database, a new node lets you browse cataloged global temporary tables.

• The Create or Alter window supports the new Compress property for DB2 for LUW 9.7 indexes.

• Toad supports the data-type attributes introduced in DB2 for LUW 9.7. These attributes include the precision for Timestamp types and the inline length for LOB and XML types.

• The enhanced Toad Debugger provides support for new DB2 for LUW 9.7 features. These features include Oracle-like data types, such as NUMBER, VARCHAR2, and BOOLEAN, and logic control statements, such as LOOP, CASE, and IF/THEN.

Back to Start of Section

Back to Top

Prerequisites and Installation

Toad ships and installs IBM DB2 for LUW Client 9.7 as the DB2 client. The new default location for the DB2 client is C:\Program Files\Toad for DB2 4.6\SQLLIB.

Back to Start of Section

Back to Top

General Toad Environment

You can increase screen real-estate in Toad by pressing SHIFT+ALT+ENTER or selecting View | Full Screen from the menu to hide the default toolbars and display Toad in full screen mode.

In full screen mode, you can switch back to your previous screen size and displayed toolbars by clicking Full Screen beside the menu.

Back to Start of Section

Back to Top

Connections

You can now assign a category such as Development or Production to connections. This adds an indicator beside the connection in the Connection Manager and also color codes document tabs, such as Database Explorer, Editor, and Query Builder tabs, opened on the connection. To assign a category to a connection, select an existing category or create a new category from the Create New Connection or Connection Properties window.

The following shows four document tabs from different connections. The first tab has a Production category assigned to it; the second and fourth tabs have a Development category assigned; and the third tab has no category assigned. Note that the category also displays when you hover over the tab.

Additionally, you can select the Show category in explorer and object editors checkbox in Tools | Options | Database | General to apply the color coding to the Object Explorer window and the navigation pane in Object Editor (Create, Alter, Drop, etc.) windows.

Back to Start of Section

Back to Top

Automation

• The Zip File activity now supports AES 128-bit and 256-bit encryption.

Note: If you encrypt the zip file, you must have a zip utility that can support 128-bit or 256-bit unencryption.

• The Run Program activity now supports a Return Code variable. You can use this variable with an If..Condition activity.

  

Back to Start of Section

Back to Top

Database Administration

Click a category in the list to view the features and updates for this release:

• Object Explorer

• Object Management - General

• Object Management - DB2 for LUW

• Object Management - DB2 for z/OS

• Master Detail Browser

Object Explorer

• Toad now allows you to share object filters by exporting and importing them. To export named filters or unnamed filters defined for the current connection, select Export Filters from the schema filter menu.

Other Toad users who have the same database or subsystem connection defined can import and use the filters you exported. To import the filters in Toad, select File | Open File and select the appropriate TPF (Toad filter pack) file.

• The old Database Explorer and Web Browser toolbars have been combined into a single Explorer toolbar:

Object Management - General

• Within the Create View or Alter View window, you can launch a Query Builder session to help you build and maintain the view query.

When you have built or maintained the query, you can send it back to the Create or Alter View window.

• Toad introduces new privilege editors that make it easy to grant or revoke privileges on multiple database objects for users, groups, and DB2 for LUW roles.

Additionally, the Create Like option is now available to clone privileges.

• Utility and object editors now execute scripts on a background thread, allowing you to use other features in Toad while executing long-running scripts. The following shows what happens when you click Execute in a utility or object editor.

• When you open a previously saved Query Builder file in the ER Diagram feature, you can now right-click the Diagram pane and select Refresh to get the latest objects from the database, including added or removed columns and data-type updates.

  

Object Management - DB2 for LUW

• Toad provides support for important DB2 for LUW 9.7 features.  See Support for DB2 for LUW 9.7 Features.

• You can now send dynamic SQL statements captured for a given application to the Editor for tweaking or to Quest SQL Optimizer for DB2 LUW for tuning. From the Database node in the Database or Object Explorer, access the Applications tab. For a specific application, access its Dynamic SQL tab, select an SQL statement, and click the appropriate icon.

• The Parameters node has been removed from the Database or Object Explorer. Instead, database configuration parameter information now displays on the DB Parameters and DBM Parameters tabs on the right side of the Database node. As with the old design, you can edit online and deferred parameters.

You can now view database configuration parameters across all database partitions in a tabbed or side-by-side view.

The new side-by-side view allows you easily to see and edit parameters across all database partitions.

• Toad now has additional points from which to launch Spotlight on DB2 for LUW and Toad SQL Analysis for DB2 LUW on the current database.

From the Database node in the Database or Object Explorer, right-click the database object to launch Spotlight or SQL Analysis.

Additionally, you can launch Spotlight from the Monitor tab, located on the right side of the Database node.

• You can now activate, deactivate, quiesce, or unquiesce a DB2 for LUW database. Access these features from the Tools | LUW Database Tools menu.

Object Management - DB2 for z/OS

Toad now provides options to create copies of your data during a data load process to remove any COPY-PENDING statuses. These options apply to data loads that occur during Toad's DB2 utility processing or advanced alters.

If you select to perform image copies, Toad includes either COPYDDN parameters or a separate COPY statement in the LOAD script. (COPYDDN parameters are used for a LOAD REPLACE process only. Otherwise, Toad generates a separate COPY statement.)

Back to Start of Section

Back to Top

Space Management

• The Space Exceptions feature for DB2 for LUW databases has a new design. The filter panel at the top has been removed; exceptions are now organized on separate Table Reorg and Index Reorg reports. Additionally, the feature includes two new reports—Tablespace Freespace and Index Cardinality.

From any object listed on the reports, you can now right-click to perform actions.

• The Space Usage report for a DB2 for LUW database now includes a Details tab. This tab allows you to view container size information at summary and detailed levels.

Back to Start of Section

Back to Top

Data Management

Click a category in the list to view the features and updates for this release:

• Export Wizard

• Import Wizard

Export Wizard

• Support for exporting directly to Excel 2007 and Excel 2010.

• Toad now checks the directory you are exporting to and if a file with the same name already exists, the text of the Overwrite checkbox turns red as a warning so you can either overwrite or rename the file. The Next button is also disabled until you make a change.

• If you select a single table to export in the Export Wizard, you can specify a different name for the worksheet than the actual table name.

Import Wizard

The Import wizard now allows you to specify a discard file. Rows that fail to import are written to this file.

Error messages display on the Import Error window.

The Import Finished window provides a link to the discard file.

Back to Start of Section

Back to Top

Query Development

Click a category in the list to view the features and updates for this release:

• General

• Query Builder

• Editor

• Debugger

General

You can now toggle the Pivot & Chart tab to display the pivot grid and chart vertically (default) or horizontally from the right-click context menu.

The horizontal display looks as follows.

Query Builder

• When opening a previously saved Query Builder file, you can right-click the Diagram pane and select Refresh to get the latest objects from the database, including added or removed columns and data type updates.

An * in the title of the object indicates that the saved version differs from the database version.

• When using an IN or NOT IN operator on a date/time column in a WHERE condition, you can now select multiple entries or all entries.

Editor

• The Rename Tab is back by popular demand. In a previous release, this option was removed because of conflicts with version control, but it has been rewritten to avoid these conflicts. To use this feature, press F2 in an Editor or right-click an Editor tab and select Rename Tab.

  

  The temporary name is now stored as an alias.

  

• Files are now added to the Recent Files list when you drag them into the Editor.

  

• Line numbers now display by default in the left margin of the Editor window and on the SQL Script page in object editors. You can disable this functionality by clearing the Show line numbers checkbox in Tools | Options | Editor | General.

• You can now apply custom format templates to SQL directly from the Editor by selecting a template from the Format drop-down list on the toolbar. You can customize existing templates or create new templates in Tools | Options | Editor | Formatter.

  

• When you execute a script with host variables, the Bind Variables window now shows the type associated with the column or variable.

  

• The Editor now supports the generation of PL/I-formatted SQL.

  

• Group Execute includes the following enhancements:

  • When saving an Editor file where Group Execute is enabled, Toad defaults to saving the file as a Toad Editor File (.tef). If you save as this file type, the selected group and any filters are also saved in the file.

  • You can also see how many targets have been selected.

    

  • Toad now provides a new Merge result sets option for the Group Execute feature.

    

    

Debugger

• The enhanced Toad Debugger now supports the IBM DB2 Unified Debugger. See the Toad for DB2 Installation Guide for Debugger configuration requirements.

  Note: The Unified Debugger supports DB2 for LUW 9 and later databases and DB2 for z/OS 8 or 9 and later subsystems. You can no longer debug stored procedures on DB2 for LUW 8 databases.

• Toad Debugger provides support for new DB2 for LUW 9.7 features. These features include Oracle-like data types, such as NUMBER, VARCHAR2, and BOOLEAN, and logic control statements, such as LOOP, CASE, and IF/THEN.

  

Back to Start of Section

Back to Top

Project Management

You can now open a new project or save a project using buttons on the Project Manager toolbar.

Back to Start of Section

Back to Top

Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in the Toad for DB2 4.6:

Back to Start of Section

Back to Top

Known Issues

The following is a list of issues known to exist at the time of the Toad for DB2 release.

Back to Start of Section

Back to Top

Third-Party Known Issues

The following is a list of third party issues known to exist at the time of the Toad for DB2 release.

Back to Start of Section

Back to Top

Upgrade and Compatibility

Upgrade Toad for DB2

Review upgrade information in the Toad for DB2 Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.

Upgrade the Quest IBM DB2 z/OS Component

An upgrade to the Quest IBM DB2 z/OS component was available with the previous version, Toad for DB2 4.5.2. To ensure you have the latest z/OS component upgrade on a DB2 subsystem, do one of the following:

• If neither the Quest Central for DB2 mainframe component nor the Quest IBM DB2 z/OS component resides on the DB2 subsystem, perform a complete installation of the Toad IBM DB2 z/OS component available with this release of Toad for DB2. See the Toad IBM DB2 z/OS Installation Guide for more information.

• If the Quest Central for DB2 mainframe component or a pre-4.5 Quest IBM DB2 z/OS component resides on the DB2 subsystem, perform the following two-part upgrade:

  • Part 1: Update the LOADLIB

  • Part 2: Define the new functions

• If Quest IBM DB2 z/OS Component 4.5.0 resides on the DB2 subsystem, perform Part 1: Update the LOADLIB only.

• If Quest IBM DB2 z/OS Component 4.5.2 resides on the DB2 subsystem, the z/OS component is up to date.

Determine Current Quest IBM DB2 z/OS Component Version

To determine the Quest z/OS component version currently installed on a DB2 subsystem

1. Open a Toad Editor on the DB2 subsystem connection.
2. Execute the following query:

Notes:

• If the returned value is 5.1.0.14, the component version is 4.5.0.
• A value less than 5.1.0.14 indicates a pre-4.5.0 version.
• If the returned value is 5.1.0.2, the component version is 4.5.2.

Part 1: Update the LOADLIB

To update the LOADLIB

1. Allocate a sequential file on the mainframe using the following attributes:

RECFM=FB

LRECL=80

BLKSIZE=3120

2. Use FTP or an IND$FILE transfer to copy loadlib.xmi (in the Plugins\DB2\zOS folder, located where the Toad for DB2 4.6 client is installed) to the sequential file you set up in step 1. Transfer the file in binary mode.
3. At a TSO command prompt, type the following, where 'sequential.file.name' is the file you allocated in step 1:

TSO RECEIVE INDATASET (‘sequential.file.name’)

4. At message INMR906A, type the following:

DATASET(‘loadlib.name’)

The variable ’loadlib.name’ is either the name of the new PDS/E or the name of the old LOADLIB you are replacing, depending on whether you created a new PDS/E or are using the existing LOADLIB.

5. If you chose to receive the xmi dataset into a new PDS/E, do the following:

1. Update the WLM-started tasks and QPDSNAT procedures to reflect the new load library name.

2. APF-authorize the new LOADLIB.

Part 2: Define the New Functions

To define the new functions

1. Locate the U4045DDL member in the Plugins\DB2\zOS folder where the Toad for DB2 4.6 client is installed.

2. Open this file in the Toad Editor.

3. Change the %COLLID% and %MULTTCB% variables in the script to match those currently used in your system.

4. Execute the script to define the two new functions.

5. Grant these functions the same EXECUTE privileges granted to other QUEST functions.

Back to Start of Section

Back to Top

System Requirements

Verify that your system meets the requirements described in the following sections:

• Client Requirements

• Server Requirements

• User Requirements

• Citrix Requirements

• LDAP Requirements

• Compile and Debug Requirements for Stored Procedures

• Requirement for Capturing Container Information in DB2 for LUW Multi-Partition Databases

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

• Recommended Indexes to Improve Toad Performance in DB2 for z/OS

• Requirements for Object Migration

• SQL Analysis Configuration Requirements

Back to Top

Client Requirements

Toad for DB2 client installation requires the following.

Note: If a DB2 for LUW 7 client is installed on the machine where you are installing Toad, you must upgrade the DB2 client to version 8 before installing Toad for DB2 to avoid losing functionality in some DB2 native tools.

Back to Start of Section

Back to Top

Server Requirements

Toad supports any of these DB2 and operating system versions.

Back to Start of Section

Back to Top

User Privilege Requirements

The following are user requirements for installing and running Toad:

User Requirements to Install Toad

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

• Associate file extensions.
• View the Toad shortcut icon on the desktop or the Toad menu options on 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 a 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, this user 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:

  http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadDB2LUWAuthorizations.xls

• As a minimum to manage DB2 for z/OS subsystems in Toad, the user ID specified in the Toad connection profile for a specific subsystem must either have SYSADM privileges or be granted 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:

  http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadDB2zOSAuthorizations.doc

• 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.
6. In the File field, locate and select Toad.exe.
7. 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.
• 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.)

Back to Start of Section

Back to Top

Citrix Requirements

Toad has been tested for Citrix support on Windows Server 2003 Enterprise Server (Service Pack 2) using the Metaframe Access Suite 5.0 and Citrix Presentation Server Clients 10.2. See "Install Toad on Citrix Systems" in the Toad for DB2 Installation Guide.

Back to Start of Section

Back to Top

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: Keep the following mind:

• 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.
• Currently, Toad for DB2 supports only access to DB2 LDAP catalog entries. Toad does not support the management of these entries.

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 Connections window.

Databases on the LDAP server should now be available from the Database Alias drop-down list in the Connections window. To complete the Toad connection setup, you must create a Toad profile for each database. See Create Toad Connection Profiles for DB2 in the Toad for DB2 Installation Guide.

Back to Start of Section

Back to Top

Requirement for Capturing Container Information in DB2 for LUW Multi-Partition Databases

Certain Toad functions require that the DFT_MON_BUFPOOL database manager configuration parameter be set to ON to capture information on containers used in DB2 for LUW databases. Additionally, to capture container information across all partitions in a multi-partition database, the snapshot monitor requires that all database partitions be active. To activate all database partitions (and keep them active), execute the DB2 command ACTIVATE DATABASE real_database_name on the server before connecting Toad to the database. See your IBM DB2 for Linux, Unix, and Windows documentation for more information about this command.

Back to Start of Section

Back to Top

Compile and Debug Requirements for Stored SQL Procedures

See the Toad for DB2 Installation Guide for the list of requirements.

Back to Start of Section

Back to Top

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

To have access to the full range of Toad functionality for managing DB2 for z/OS subsystems, make sure that you have completed the following:

• Install the Quest IBM DB2 z/OS Component 4.5.2 on each DB2 for z/OS subsystem. The z/OS component allows you to perform the following functionality in Toad:

  • Bind and rebind DB2 for z/OS packages and plans

  • Invoke DB2 for z/OS utilities and commands within scripts that Toad for DB2 generates for advanced alters, migrations, and data and object synchronizations

  • Run stand-alone DB2 for z/OS utilities and commands available with UIs in Toad

  • Run DB2 for z/OS commands from the Editor

  • Execute remote DB2 for z/OS scripts

  • Create, alter, or drop dataset templates

  • Use Toad UIs to run DISPLAY, START, and STOP commands on DB2 for z/OS databases, tablespace, and indexes

  • Access accurate buffer-pool information for the DB2 subsystem

  • View volumes available for defining storage

  • View dataset information for tablespaces and indexes

  • Access information about current threads connected to the DB2 subsystem

  • Assign a RACF group to a Toad Security role to control the Toad features available to all users belonging to the RACF group

If you currently have the Quest Central for DB2 z/OS component or a pre-4.5.2 Quest IBM DB2 z/OS component installed on your DB2 subsystem, perform an upgrade. Use the instructions found in Upgrade and Compatibility.

If the neither the Quest Central for DB2 z/OS component nor a previous Quest IBM DB2 z/OS component currently exists on your DB2 subsystem, perform a new installation of Quest IBM DB2 z/OS Component available with this release of Toad for DB2. Use the instructions found in the Quest IBM DB2 z/OS Installation Guide (available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation).

• Make sure that the IBM stored procedure SYSPROC.DSNUTILU is installed and operational on each DB2 subsystem on which you are executing DB2 utilities. For additional information about SYSPROC.DSNUTILU, refer to Appendix B of the IBM DB2 Universal Database for z/OS Utility Guide and Reference.

Note: A 32K character-size limit exists for each utility statement executing through DSNUTIILU.

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

Back to Start of Section

Back to Top

Recommended Indexes to Improve Toad Performance in DB2 for z/OS

User-defined indexes on specific system catalog tables can improve performance when you are browsing DB2 for z/OS objects in Toad. The following link contains the DDL for indexes that can optimize Toad performance on your DB2 for z/OS subsystem. Keep in mind that the creation of these indexes is a recommendation only. The indexes can have different results in different environments, depending on the number of DB2 objects and the amount of data involved. To create these indexes, edit and run the DDL contained in the following file:

http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadDB2zOSIndexes.txt

Additionally, if the schema drop-down lists in the Object Migration wizard populate slowly, consider creating an index on the SCHEMA and CREATOR columns in the catalog table for each object type. Here is a list of some of the object-type tables:

SYSIBM.SYSSYNONYMS
SYSIBM.SYSSEQUENCES
SYSIBM.SYSROUTINES
SYSIBM.SYSTABLES
SYSIBM.SYSDATATYPES
SYSIBM.SYSINDEXES
SYSIBM.SYSTRIGGERS
SYSIBM.INDEXES

Back to Start of Section

Back to Top

Requirements for Object Migration

The following are specifications for using Toad's Object Migration wizard to migrate DB2 objects and their dependencies:

• You cannot migrate objects between a DB2 for LUW and DB2 for z/OS platform and vice versa.
• Unexpected results can occur if you map two source schemas to the same target schema, and the two source schemas contain same-named objects (for example, if you map both source Schema A and source Schema B to target Schema C, and Schema A and Schema B both contain a table with the name Table1).

Back to Start of Section

Back to Top

Configuration Requirements for SQL Analysis

SQL Analysis requires the following configuration on the database servers on which you intend to run SQL collections:

• 36 4-kilobyte pages to run event monitors.
• The mon_heap_sz database manager configuration parameter set appropriately to support event monitors. See the IBM DB2 for Linux, UNIX, and Windows System Monitor Guide and Reference for more information about setting this parameter.

Back to Start of Section

Back to Top

Global Operations

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. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Far-East Asia, Japan.

However, this release has the following known capabilities or limitations:

• During the Toad for DB2 installation process, a user can override the default installation path, but cannot include Unicode characters in the new path specification. This limitation exists because Toad installs a DB2 for LUW client in the specified Toad installation path, and DB2 installations do not support Unicode characters.
• (Toad for DB2 for z/OS Xpert Edition and Toad for DB2 for LUW or z/OS DBA Edition only) The Toad SQL Tuning for DB2 z/OS, Toad SQL Analysis for DB2 LUW, and Toad Remote Script Execution (for DB2 LUW or z/OS) features support single-byte character sets only. These features do not support double-byte or multi-byte character sets. All DB2 client and server installations should be configured to use the same or compatible character encodings and the same locale and regional options.

Back to Top

Getting Started

Contents of the Release Package

The Toad for DB2 release package contains the following products:

• Toad for DB2 4.6
• Quest IBM DB2 z/OS Component 4.5
• Product documentation, including:
  • Toad for DB2 Installation Guide
  • Quest IBM DB2 z/OS Component Installation Guide
  • Toad for DB2 LUW Agent Installation Guide
  • On-line help
  • Other documentation based on the Toad for DB2 edition that you purchased

Installation Instructions

For important information about installing Toad for DB2, refer to the Toad for DB2 Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.

Installation Instructions for Additional Components

To install other Toad for DB2 components, refer to the following documentation:

Back to Start of Section

Back to Top

For More Information

Contacting Quest Software

Refer to our Web site for regional and international office information.

Contacting 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.

Back to Start of Section

Back to Top

© 2010 Quest Software, Inc.
ALL RIGHTS RESERVED.

This document contains proprietary information protected by copyright. The software described in this document 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 purchaser’s personal use without the written permission of Quest Software, Inc.

If you have any questions regarding your potential use of this material, contact:

Refer to our web site for regional and international office information.

Trademarks

Quest, Quest Software, the Quest Software logo, Aelita, Akonix, Akonix, AppAssure, Benchmark Factory, Big Brother, ChangeAuditor, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, GPOAdmin, I/Watch, Imceda, InLook, IntelliProfile, InTrust, Invertus, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, MessageStats, NBSpool, NetBase, Npulse, NetPro, PassGo, PerformaSure, Quest Central, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, vAnalyzer, vAutomator, vControl, vConverter, vEssentials, vFoglight, vMigrator, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vReplicator, vSpotlight, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vEssentials, Xaffire, and XRT 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.

Disclaimer

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.

Back to Top