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: Configure DB2 Client Connections 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. |
© ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center