Chat now with support
Chat with Support

Toad Data Point 5.1 - User Guide

Troubleshoot DB2 LUW Issues

Review the following solutions to help troubleshoot DB2 LUW issues pertaining to Toad installation and database connections.

Installation Issues



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.


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=, 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.


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:

  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.

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.


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.


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

"SUCCESS - unable to allocate an environment handle."

A settings file might be corrupt.


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


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


Related Topics

Create DB2 Connections

Manage Connections

Connection/Navigation Manager 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating