You might encounter issues with initializing Unified Debugger sessions if the version of the DB2 for LUW server on which you are debugging is earlier than 10.1 fix pack 2.

Workaround: If the DB2 server version is earlier than DB2 for LUW 10.1 fix pack 2, copy DB2DBGM.JAR from the Toad client installation to the following location on the server:

• DB2 instance home path/SQLLIB/JAR (Unix or AIX computer)
• DB2 instance home path\SQLLIB\JAR (Windows computer)

Notes:

If the DB2 server version is DB2 for 10.1 fix pack 2, use the JAR file supplied with your DB2 version. If replacing the JAR file as described in the workaround, make sure you back up the original JAR file on the server before replacing it with the one from the Toad client installation.

Toad uses hardcoded values instead of some variables such as %USERNAME% in several path names and therefore App-V environment is not supported.

For installation adhere to Windows Installer Best Practices, see here.

If running Toad for IBM DB2 6.0 or earlier in a pureScale environment and the QUEST.SH_SNAPSHOT procedure had been installed, the procedure will have to be redefined. Please, follow these steps:

1. Drop procedure QUEST.SH_SNAPSHOT
2. Right click a tablespace
3. Select Space Management | View Space History
4. Click Yes when prompted to run the install script for the procedure
5. Execute the script

After installing DB2 LUW v10.1.3, the script tab for LUW procedures is empty. This is due to an issue introduced by IBM in fixpack 3 regarding the NULLIF SQL function.

IBM APAR IC96725 addresses this issue.

When the IBM DB2 Analytics Accelerator is used in conjunction with DB2 z/OS, along with an IBM DB2 .Net Data Provider v10.1.3, timestamp values returned from queries are invalid. Since Toad DB2 v5.6 uses the IBM DB2 v10.1.3 .Net Data provider, invalid timestamp values can be returned within Toad 5.6. IBM PMR 8862756 has been opened on this topic.

Please consult that PMR for a work-around.

When the user is running DB2 Server 10.1.3 with a database that has been migrated from a previous release, the debugger will fail with a reference to SYSDEBUGPRIVATE. This occurs from an IBM bug in the db2updv10 update utility.

IBM APAR IC96837 addresses this issue. This has been resolved in IBM DB2 10.1 FixPack 4.

The Debugger may not advance to the next line under certain circumstances. Those circumstances include DECLARE statements with multiple variables defined on a single line and IF statements with multiple conditions defined on a single line.

Workaround:

In procedures that are to be debugged: The procedure text should be modified to separate DECLARE variables onto different lines and IF statements separated to have conditions on separate lines.

LUW: The following error message is displayed when you attempt to modify a watch value during a Debug session on a DB2 for LUW 9 database: "ERROR [57011] [IBM][DB2/NT] SQL0954C Not enough storage is available in the application heap to process the statement. SQLSTATE=57011" The call to modify the watch value fails on DB2, and the server runs out of heap memory.

Workaround: To avoid the heap memory issue, increase the application heap size on the server.

To export to an Office 2003 or 2007 Excel instance, the Office Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from one of the following locations:

• 2003 PIAs: http://www.microsoft.com/en-us/download/details.aspx?id=20923
• 2007 PIAs: http://www.microsoft.com/en-us/download/details.aspx?id=18346

Date formatting issues occur when exporting table data to an Excel file or instance. These issues seem to occur especially when exporting dates previous to 1900.

Workaround: For better results, try exporting the data to a CSV file.