Review the following solutions to help troubleshoot Access issues pertaining to missing functionality and object information and other problems in Toad.
See Create Access Connections for more information about Access connections.
Issue | Cause/Solution |
---|---|
Some queries display in the View tab of the Object Explorer, but do not display in the Query tab. |
The Access ODBC driver handles saved queries in the following manner:
|
Primary key information is unavailable. |
The Microsoft Access ODBC driver does not return primary key information for databases. However, in some cases, Toad can obtain this information through additional methods. |
Issue | Cause/Solution |
---|---|
A delay occurs between writing a value to a database via one connection and seeing the updated value via another connection. |
This delay is the default when you are writing and reading data between two different Jet connections. The delay occurs even if the two connections reside in the same client process. Solution: Use a single connection when updating data. |
Review the following solutions to help troubleshoot DB2 LUW issues pertaining to Toad installation and database connections.
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
|
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." "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
Notes:
|
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. |
Review the following solutions to help troubleshoot DB2 z/OS issues in Toad.
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
|
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:
|
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. |
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: 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:
|
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. |
© ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center