Chat now with support
Chat with Support

Toad Data Point 6.1 - Installation Guide

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 

Troubleshoot Oracle Issues

Review the following solutions to help troubleshoot Oracle connection issues pertaining to database connections and missing functionality and object information in Toad.

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.

Missing Functionality and Object Information

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:

  • For 9i drivers, update to 9.2.0.7.0 or later.

  • For 10g drivers, update to 10.1.0.3.0 or later.

 

Related Topics

Create Oracle Connections

Manage Connections

Connection/Navigation Manager 

 

Troubleshoot SQL Server Issues

Connection Issues

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
C:\Program Files\Quest Software
\Toad Data Point\Template\Scripts\
InitialSqlServer.Sql
" error message when connecting

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

  1. Open the SQL Server options page under Tools | Options | Database | SQL Server.

  2. Specify the location for the new install's InitialSqlServer.Sql file in the Run Script on new connection field.

By default, this file is located in the following directory:

C:\Program Files\Quest Software\Toad Data Point version \Templates\Scripts

Note: Clicking may result in a "Path not found error". If you receive this error, manually enter the location in the field.  

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:

  1. Open the options page under Tools | Options | Database | General.
  2. Clear Poll service status in connection list checkbox.
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.

 

Related Topics

Create SQL Server Connections

Manage Connections

Connection/Navigation Manager 

Troubleshoot Sybase ASE Issues

Review the following solutions to help troubleshoot SAP issues pertaining to the following in Toad:

Connection Issues

Issue Cause/Solution

Unable to connect to the database. The following message displays: "The ODBCMDA procedures have not been installed on this database..."

Stored procedures that the ODBC driver requires currently do not exist on the server.

Solution:

Install the required procedures.

Missing Functionality or Object Information

Issue Cause/Solution

Unable to view or export data for objects with non-standard names.

The ASE ODBC driver has issues handling non-standard names for objects.

Solution:

When setting up an ASE connection in Toad, select Use quoted identifiers on the Connection tab in the Adaptive Server Enterprise window to enable the use of quotations in identifiers.

Unable to view linked tables.

Linked tables store DSN connection information.

Solution:

Set up the DSN connection information exactly the same on all machines that access the database.

Other Issues

Issue Cause/Solution

DBMS name showing as SQL Server.

Older versions of the ASE ODBC driver return SQL Server as the DBMS name.

Solution:

Upgrade to the latest version of the ODBC driver, which correctly returns Adaptive Server Enterprise as the DBMS name.

 

Related Topics

Create SAP Connections

Manage Connections

Connection/Navigation Manager 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating