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. |
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 |
Solution:
|
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
Notes:
|
Review the following solutions to help troubleshoot Oracle connection issues
Issue | Cause/Solution |
---|---|
Attempting to connect when Oracle Instant Client is installed results in a System.NullReferenceException error |
Solution: In order to connect using the Oracle Instant Client, the directory for the Instant Client must be included in the environmental path, or you must copy the client files for the instance to the root install directory of Toad Data Point. You can also connect to the database without using an Oracle client or TNSNames file by selecting the Direct tab in the Create New Connection window. |
An error occurs when attempting to connect to Oracle Rdb using an ODBC driver | Toad does not support Oracle Rdb at this time. |
Attempting to connect to Oracle 18c results in the error ORA-28040: No matching authentication protocol | SQLNET.ALLOWED_LOGON_VERSION has been deprecated. Upgrade your Oracle client or set the parameter value to 12c. |
Issue | Cause/Solution |
---|---|
Some schemas are not available from the Schema drop-down list in the Object Explorer. |
The Oracle ODBC driver cannot display schemas that do not have any tables. |
Unable to view table data on the Data tab; SQLFetch generates an access violation. |
The Oracle ODBC driver is accessing unallocated memory. Solution: Update the Oracle ODBC driver:
|
Review the following solutions to help troubleshoot SQL Server connection issues in Toad.
Issue | Cause/Solution |
---|---|
Cannot specify a port number when connecting |
Currently, Toad does not have a separate field for specifying a port number. Solution: You can connect if you know the port number for the instance by entering the following in the Server name field on the New Connection window: ServerName,Port or IPAddress,Port For example: 10.1.29.129,1234 (where 1234 is the port number of the instance) |
Cannot connect to a remote instance in SQL Server 2005 |
Remote connections may not be enabled in SQL Server 2005. Also, named instances are configured to use dynamic ports and select an available port once the SQL Server Service starts. If you are connecting to a named instance through a firewall, configure the Database Engine to listen on a specific port, so that the appropriate port is opened in the firewall. Note: Remote connections are disabled by default in the Express and Developer editions of SQL Server 2005. Solution: To enable remote connections, see "How to configure SQL Server 2005 to allow remote connections" at: http://support.microsoft.com/kb/914277 |
"Path is not of a legal form" error message when connecting or "Could not find a part of the path |
You attempted to migrate settings from a previous install of Toad to the current install, but the settings file (InitialSqlServer.Sql) for the previous install was either removed, moved, or corrupt. You may also receive this error if you installed Toad and migrated settings from a previous version, and later uninstalled the previous version. Solution: You must specify a valid location for the InitialSqlServer.Sql file in Toad. To specify a valid location
By default, this file is located in the following directory: C:\Program Files\Quest Software\Toad Data Point version \Templates\Scripts Note: Clicking |
Cannot establish Named Pipes connection |
If you are trying to connect to the server using Named Pipes, "Poll service status in connection list" option should be cleared. Solution:
|
Cannot access some functionality when working with Azure connection. |
To utilize majority of Toad functionality VIEW DEFINITION grant is required for those databases you want to work with. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center