Chat now with support
Chat with Support

Toad for DB2 6.3 - Installation Guide

Create DB2 Connections

Setting up connections to the DB2 for LUW databases and DB2 for z/OS subsystems that Toad will manage requires two steps.

Step 1. Configure DB2 client connections - If you use a DB2 client each of the databases or subsystems must be cataloged on the client. See Configure DB2 Client Connections to learn how to catalog databases/subsystems.

Step 2. Create connection profiles - Step 2 involves creating Toad connection profiles for DB2 databases or subsystems that were either cataloged in the DB2 client or imported from your Data Server Driver configuration file. 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. If you use IBM DSD environment you can import your connection profile from a Data Server Driver configuration file.

Note: The default location of your Data Server Driver configuration file is in ...Program Data\IBM\DB2\IBMDBCL1\cfg. The default config filename is db2dsdriver.cfg.

Note: When you connect using IBM Data Server Driver the Database button and the toolbar option in Tools | LUW Database Options will not be available.

Connection Using a Custom Connection String

You can also connect to your DB2 database/subsystem using a custom connection string.

  • Select Connect Using | Connection String in Connection Properties
  • Enter Database alias, Host name, Login, and Password and the connection string will be automatically updated according to what you enter
  • You can save a connection created using a custom connection string in your Connection Manager

Create Connection Profiles

Use one of the following methods to create Toad connection profiles:

Manage Connections

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:

  • Connect to and manage a DB2 database or subsystem through Toad

  • Troubleshoot connection issues

Note: Click to open the Client Configuration Wizard. See Configure DB2 Client Connections for more information.

Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help | About.

Create Intelligence Central Connections

Toad allows you to create a connection to a Toad Intelligence Central server.

About Toad Intelligence Central Connections

To create a new TIC connection, you must provide the TIC server name and then register with TIC by creating a new user account for yourself. The new user name and password will be used by TIC to identify you from among the group of TIC users and to manage the objects you create and are granted access to on the TIC server.

A TIC connection displays in the format: username@server. The username is the name of the new user you create when you create a new TIC connection.

To create an Intelligence Central connection

  1. Click in the Toad Intelligence Central Object Explorer (View | Toad Intelligence Central).
  2. Select the Register New User tab.
  3. Register New User. Use this tab to register with Intelligence Central by creating your own account (user name and password). Review the following for additional information:

    Note: If you are creating a connection to a Intelligence Central instance for which you already have a user account, do not fill in this tab again. Skip ahead to the next step (Login tab).

    Register New User  
    Use Windows Authentication

    Select to create a new user account using your Windows credentials. Toad automatically populates the fields with your account information.

    Host

    Enter the name of the Intelligence Central host server. Click to display a list of Intelligence Central servers currently active on the network.

    User Name

    Create a new user name for this connection.

    This is the name you will be logged in with. The objects you create will be linked to this user name. All your TIC rights (like sharing) will be linked to this user name. This user name will display in the format:

    username@server

    Note: User names must be lower case only. When you enter a user name, all upper-case characters are automatically converted to lower-case.

    Password

    Create a password.

    Verify Password

    Re-enter the password to confirm.

    Full Name

    Enter your full name.

    This name, along with your user name, displays on the Sharing tab of the Publishing dialog and in the Alter Visibility dialog. Your full name will help users identify you when they select users with which to share an object.

    Email Address

    Enter your email address.

    Port

    Enter the port number for the App Server.
  4. Login as Existing User tab. Use this tab to create a new connection to a TIC server for which you already have a user account. (When you open an existing connection, this tab displays your user account information.)

    Login as Existing User  

    Host

    Enter the name of the Intelligence Central host server. Click to display a list of Intelligence Central servers currently active on the network.

    User

    Enter an existing server user name.

    Password

    Enter the existing password for the user name.

    Data Source

    (Optional) Enter the name of a default data source to open upon connection.

    Port

    Enter the port number for the App Server.

    Category

    (Optional) Select an existing category or create a new one.
  5. (Optional) Select Save Password to save your password with this connection.
  6. Click Connect to connect immediately and save the connection information. Optionally, click Save to save the connection without connecting.

To change your Intelligence Central user password

You can change your password for your Intelligence Central user account at any time.

Note: You cannot use this procedure to change the password for a Intelligence Central account that uses Windows Authentication.

  1. In the Navigation Manager, right-click the Intelligence Central connection and select Change Password.
  2. Enter the old password and then enter the new password. Enter the new password a second time to confirm.

To switch your TIC user account to a Windows Authentication account

You can switch your current Intelligence Central account to a Windows Authentication account if both accounts have the same user name.

  1. In the Connection Manager, right-click your current TIC account connection and select Properties.
  2. In the Register New User tab, select Use Windows Authentication. Toad prompts you to switch your account.

Tip: Connections are stored in the connections.xml file and can be found by clicking the Application Data Directory link in Help | About.

 

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

Cause/Solution

System.IO.FileNotFoundException - File or assembly name DB2AdminWrapper, or one of its dependencies was not found

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.

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

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.

When installing Toad on Windows 7 64-bit, Program Compatibility Assistant may appear with “This program might not have installed correctly” message.

Solution:

Select This program installed correctly to continue installation. For more information, see http://windows.microsoft.com/en-PH/windows7/Program-Compatibility-Assistant-frequently-asked-questions

Connection Issues

Issue Cause/Solution

ERROR [08001] [IBM] SQL1336N The remote host was not found. SQLSTATE=08001  

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 for more information to determine the best method for cataloging a database.

"The type initializer for 'IBM.Data.DB2.DB2Connection' threw an exception."
or

"SUCCESS - unable to allocate an environment handle."

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:
    • Windows XP, Windows Server 2003—C:\Documents and Settings\username\Local Settings\Application Data\Quest Software
    • Windows Vista, Windows Server 2008, Windows 7—C:\Users\username\AppData\ Roaming\Quest Software\
  3. Rename the Toad for DB2 version# folder to "Toad for DB2 OLD".

  4. Restart Toad and try to connect.

Notes:

  • Make sure you can view hidden folders in Windows Explorer.
  • To navigate to this directory quickly, click the Application Data Directory link in the About dialog (Help | About).

Other Issues

Issue Cause/Solution

Unable to capture 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.

Troubleshoot DB2 z/OS Issues

Review the following solutions to help troubleshoot DB2 z/OS issues in Toad.

Installation Issues

Issue Cause/Solution

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

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.

When installing Toad on Windows 7 64-bit, Program Compatibility Assistant may appear with “This program might not have installed correctly” message.

Solution:

Select This program installed correctly to continue installation. For more information, see http://windows.microsoft.com/en-PH/windows7/Program-Compatibility-Assistant-frequently-asked-questions

Connection Issues

Issue Cause/Solution

ERROR [08001] [IBM] SQL1336N The remote host was not found. SQLSTATE=08001  

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 for more information to determine the best method for cataloging a database.

ERROR [42501] [IBM][DB2] SQL0551N "UserName" does not have the privilege to perform operation "SELECT" on object "SYSIBM.SYSSTMT". SQLSTATE=42501

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.

ERROR [] [IBM] SQL1460N The environment variable "SOCKS_NS" required for SOCKS server name resolution is not defined or not valid.

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:

  • 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

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.

-or-

After connecting, some objects do not display properly or some functionality does not work as designed.

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.

Other Issues

Issue Cause/Solution

Poor performance when browsing DB2 for z/OS objects in Toad. Indexes are populated slowly.

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:

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

Encountering the S378 Abend when running IBM DB2 z/10 subsystem in Conversion mode with older versions of Toad.

This issue appears because the Toad z/OS Component tries to reference the QUEST.QC200ZPARM function.

Solution:

DROP the QUEST.QC200ZPARM function from your DB2 z/OS 10 subsystem. This will eliminate the possibility of the function being called into the WLM environment procedure and causing the S378 abend.

We do not recommend that you to just STOP the QUEST.QC200ZPARM function on the mainframe side, without actually dropping it, because that may case Toad or the batch process (QCEXEC – remote job execution) to hang. Dropping the QUEST.QC200ZPARM function is recommended.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating