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

z/OS: Executing a procedure causes "Invalid SQL syntax" message when parameter listing has a new line character separating parameters. IBM has opened PMR 80539,756 to investigate this issue.

Workaround: Remove the new line character and separate the parameters by the spaces.