Toad Data Point 6.0.5 - Installation Guide

This is a known limitation with Excel worksheets.

This is a known limitation with Excel worksheets.

When you connect to Excel, the driver automatically scans the first eight rows in a column and applies the data type used in a majority of those rows to all rows in the column. Any rows that do not meet the majority data type display as null values.

Solution 1: Reformat worksheet column and values as text.

1. Open the worksheet in Excel.

2. Format the column that contains mixed data types as Text.

3. You can now connect to this spreadsheet from Toad without any null values displayed.

Solution 2: Create an ODBC connection.

You can force the ODBC driver to read all rows as Text to avoid null values; however, this can result in issues if you attempt to insert data.

1. Open the Create New Connection window and select ODBC from the Group list.

2. Complete the fields as described in Create ODBC Connections.

3. Enter "IMEX=1", in quotations, in the ExtraParameters field.

4. Click Connect.

The exclamation point character has a special meaning in Excel. If a column name contains an exclamation point, it is internally converted to a dollar sign ($) character.

Tables cannot be altered when the Excel connection is Read-Only.

Solution: Deselect Read-Only Connection in the Connection Properties dialog.

Excel is a spreadsheet, and does not support primary and foreign keys so these tabs are always blank.

The Excel ODBC driver does not support this functionality.

The worksheet you are querying does not have named ranges (regions) defined.

Solution:

You can query the worksheet from the Editor by entering a dollar sign ($) followed by a cell range to limit the results similar to the following statement: 

Select * from (MyWorksheet$A1:C10)

You can also query the entire worksheet by entering a dollar sign ($) after the worksheet name. However, this may also return the worksheet's empty rows and columns.

The Excel file does not have named ranges (regions) defined. If you click OK to close the message, the new connection is created, but no user tables display in Object Explorer. (System tables are displayed, if you selected to show these.)

Solution 1: In the Excel file, create named ranges.

Solution 2: Ask Toad to automatically create named ranges.

1. Disconnect from the file.
2. In Navigation Manager, right-click the file and select Properties | Advanced.

3. Select Automatically create ranges.

   The next time you connect, Toad automatically creates named ranges, which are then displayed as tables.

See Create Excel Connections for more information.

The underlying data format cannot differentiate between an empty string and null data, so a query with a search condition that contains an empty string does not match any empty strings in the table. This occurs because the empty string is treated as a null value, and a null value never matches anything, not even another null value.

The Excel ODBC driver does not support this functionality. While it is possible to update values, DELETE statements do not remove a row from a table. Basically, you can only insert data in a table.

This error occurs if you have more than one named range (region) in the same worksheet, and the named ranges are not separated by blank rows.

Solution 1: You must add blank rows between named ranges. Add as many blank rows as you have new records to insert.

Solution 2: Include only one named range in each worksheet.

When exporting to Excel, be aware that Excel worksheets have limits for maximum number of rows and columns supported.

See Microsoft Excel specifications and limits for more information.

The Toad document window cannot display all Excel menus.

Solution:

Right-click the Excel toolbar and add the equivalent toolbar for the missing menu or functionality.

Toad document windows support one Excel instance at a time. Opening more than one Excel file disables the Excel toolbars for the additional files.

Solution:

Open only one Excel file at a time.

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.

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.

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.

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.

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

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.

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.

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.

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.

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

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.

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.

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

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.

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