立即与支持人员聊天
与支持团队交流

Toad Data Point 5.6 - Installation Guide

Troubleshoot DB2 LUW Issues

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

Installation Issues

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.

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

 

Related Topics

Create DB2 Connections

Manage Connections

Connection/Navigation Manager 

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.

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.

Missing Functionality or Object Information

Issue Cause/Solution

Unable to browse databases in DB2 for z/OS 8 or later.

The DB2 installation job DSNTISG defines a set of DB2 procedures that the ODBC driver uses. The installation assigns these procedures (namely, those beginning with SYSIBM.SQL*) to a specific Work Load Manager (WLM) environment, which currently might not exist or be defined properly.

Solution:

Be sure that you have correctly set up and enabled the WLM environment to which the procedure definitions point.

Cannot edit data in compatibility mode.

In compatibility mode, the ODBC driver does not return enough information for the CommandBuilder to correctly generate update or insert statements.

Solution:

No solution exists. However, when you connect to a subsystem running in compatibility mode, Toad now provides a message, informing you of this condition and warning you 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 Topics

Create DB2 Connections

Manage Connections

Connection/Navigation Manager 

Troubleshoot Informix Issues

Review the following solutions to help troubleshoot Informix issues in Toad.

Issue Cause/Solution

Unable to view all available databases.

The InformixODBC driver does not return information about every available database.

 

Related Topics

Create ODBC Connections

Troubleshoot MySQL Issues

Connection Issues

Issue Cause/Solution

"InvalidCastException" error when connecting to MYSQL 4.1.14-nt database

This is a known issue in MySQL.

Solution:

Review the known issue and download a patch from: http://bugs.mysql.com/bug.php?id=12771

"System.IO.DirectoryNot
FoundException"error occurs each time you attempt to connect after installing Toad into a directory other than the default directory.

Solution:

  1. Exit Toad.

  2. Locate the MySQL.xml file in the C:\Documents and Settings\username\Local Settings\ Application Data\Quest Software\ Toad for MySQLversion\ ModuleSettings

  3. Rename or delete the MySQL.xml file.

  4. Restart Toad.

Missing Functionality or Object Information

Issue Cause/Solution

Views tab in Object Explorer is unavailable when connecting to MySQL using the ODBC driver

You are attempting to connect using the 3.51 ODBC driver. This driver is hard-coded to reply that the database does not support views because it needs to connect to MySQL databases prior to version 5.

Solution:

Use the native MySQL provider included in Toad.

Using a MySQL ODBC connection in a cross-connection query results in an error

Attempting to execute a cross-connection query using a MySQL ODBC connection (not a native connection) results in the following error: "The table <table name> can not be mapped."

Solution:

To use a MySQL ODBC connection in a cross-connection query, you must specify a database for the connection.

To specify a database for an existing MySQL ODBC connection

  1. In the Connection/Navigation Manager, right-click the existing MySQL ODBC connection and select Properties.
  2. Click beside the Data source name drop-down list. The ODBC Data Source Administrator dialog opens.
  3. On the User DSN tab, select (highlight) the connection's MySQL ODBC driver and then click Configure. The MySQL ODBC Configuration dialog displays.
  4. Select a database from the Database list.

Notes:

  • Specifying a database using the Connection Properties Database field does not result in a solution. You must follow the procedure above.
  • You can repeat this procedure at any time to specify a different database.

 

Related Topics

Create MySQL Connections

Manage Connections

Connection/Navigation Manager 

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级