Relational database tools - release notes


1.0 Known problems
   1.1 Rebuild before running preference for stored procedures and user-defined functions does not work properly
   1.2 Deploying certain table user-defined functions (UDFs) results in SQLSTATE -458 error
   1.3 User-defined function deploy or Run against local fails with certain returned LOB data types
   1.4 Cannot drop DB2 Java stored procedures that were deployed without source
   1.5 Class location is not discovered for Cloudscape database connections if WebSphere Application Server is installed separately from the workbench

1.0 Known problems

1.1 Rebuild before running preference for stored procedures and user-defined functions does not work properly

The Rebuild before running preference for stored procedures and user-defined functions does not work. This preference is set on the Process page of the Preferences window (Click Windows -> Preferences to open the Preferences window, then expand the Data and the DB2 Stored Procedure and UDF Builder nodes and click the Process node). To work around this problem, you must manually build stored procedures and user-defined functions before you run them if you have made changes since your last build.

1.2 Deploying certain table user-defined functions (UDFs) results in SQLSTATE -458 error

If you deploy certain table UDFs that were exported using the Include DROP statement option in the Export Routines wizard, you may see an error message with SQLSTATE -458. This is because of an error in the generated DROP FUNCTION statement. For example, if this is your UDF source:
CREATE FUNCTION USERID.BABELFISH ( TRANSLATIONMODE VARCHAR(100), SOURCEDATA VARCHAR(100) )
The DROP FUNCTION statement is generated like this:
DROP FUNCTION USERID.BABELFISH ()
To work around this problem, remove the parentheses from the end of the DROP FUNCTION statement.

1.3 User-defined function deploy or Run against local fails with certain returned LOB data types

User-defined functions with return parameters that are LOB data types might fail to deploy or run against a local database. This will occur if there is no length specified in your returned LOB parameter. For example:
CREATE FUNCTION USERID.COLCLOB () RETURNS clob
To fix this problem, you must specify a length for the returned LOB parameter. For example:
CREATE FUNCTION USERID.COLCLOB () RETURNS clob(5k)

1.4 Cannot drop DB2 Java stored procedures that were deployed without source

If you deploy a DB2 Java stored procedure to a database without deploying the source (Deploy using source check box is not checked on the Deploy Routines wizard Options page), you cannot then drop the stored procedure from the database using the workbench. To work around this problem, you can drop the stored procedure by issuing the DROP PROCEDURE command from the DB2 Command Line Processor (CLP), or by using the DB2 Control Center. You might also need to issue the CALL SQLJ.REMOVE_JAR command to remove the installed jar.

1.5 Class location is not discovered for Cloudscape database connections if WebSphere Application Server is installed separately from the workbench

In the following scenario, the Class location field in the Database Connection wizard or page is not automatically filled in:

  1. Install the workbench without installing WebSphere Application Server (WAS). Install WAS.
  2. Start the workbench.
  3. Create a connection to a Cloudscape database (Right-click -> New connection from the Database Explorer view of the Data perspective, or using the Database connection page of another wizard).

To work around this problem, fill the Class location field in manually, or restart the workbench and create the connection again. If you restart the workbench the Class location field is automatically filled in.

Return to the main readme file