Data tools Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM® Corp.

Release notes

1.0 Limitations
   1.1 SQL tooling is not available for routines in a data design project
2.0 Known problems and workarounds
   2.1 XML table falication in Table Data Editor
   2.2 Annotated XSD Mapping Editor
   2.3 XML
   2.4 SQL Tooling
   2.5 Routine Development
   2.6 SQL Procedure Profiling
   2.7 Stored Procedure Debugger
   2.8 Data Core Functionality
   2.9 Single column of XML data type in Table Data Editor

1.0 Limitations

1.1 SQL tooling is not available for routines in a data design project

There are two new types of data projects in the workbench:

Data design projects are used to create and store data models, for example, physical data models and logical data models. Data development projects are used to create and store data application development objects, such as stored procedures and user-defined functions (also known as routines). Routines can also be viewed from a data design project as part of a physical data model. However, development support for routines from a data design project is very limited, and there is no SQL tooling support for routines in a data design project. If you are developing routines, it is recommended that you use the designated data development project, that provides more complete support including wizards, routine editors, debugging support, and the integration of SQL tooling.

2.0 Known problems and workarounds

2.1 XML table falication in Table Data Editor

In the table data editor, if you perform an XML validation on a XML table that does not have a primary key, the XML validation will only work the first time, when you insert the XML value. In addition, an update of an existing XML column with XML validation will fail.

Workaround: Create a primary key for tables that contain XML columns.

2.2 Annotated XSD Mapping Editor

Working with multiple root elements in this editor can lead to errors when you save the annotated XSD file.

Workaround: Create a separate set of XML Schema document files for each root element.

2.3 XML

  • In order to use XML data types and work with XML schemas, you must connect to a UTF -8 database.
  • The amount of data returned from the database for XML documents is unlimited. Depending on the amount of data that you return, performance might be affected.
  • 2.4 SQL Tooling

    Workaround:  You can run the SQL from the SQL builder, if it is a DML statement.

    2.5 Routine Development

    Workaround: this issue, ensure that db2jcc.jar and the appropriate license files are in your system classpath.

    Workaround: You should specify the "-source 1.4" option in the Compile options field of the Deploy Routines wizard when you are  deploying Java stored procedures against servers that use a JDK level of 1.4. (for example, a DB2 Universal Database for Linux®, UNIX®, and Windows® V8.2 server). In general, use the appropriate compilation option "-source JDK level " to match the JDK level on the database server.

    Workaround: The tools.jar is not needed to run the Ant script, and for now, you can just ignore this message.

    Workaround: Save the stored procedure by clicking File->Save, pressing Ctrl+S  or clicking the Save icon.

    2.6 SQL Procedure Profiling

    Workaround: you can create a connection to the server without the retrieveMessagesFromServerOnGetMessage=true setting.

    2.7 Stored Procedure Debugger

    Workaround: To increase the Java timeout setting, click Window > Preferences from the workbench menu bar. Expand the Java node and click Debug. On the Debug preferences page, increase the Debugger timeout(ms) value in the Communication timeout section. It is recommended that you at least double the default value.

     Workaround: To enable the button, select the Input an evaluation radio button, set the value to a non-empty string (for example, 'a'), and then select the Input literal text radio button. The OK button will then be available.

    Workaround: Ensure that you specify the -g compiler option when you deploy Java stored procedures.

     Workaround: When you start a new debug session, you should first remove all of the old breakpoints and then add new breakpoints.

     Workaround: The session manager needs to be executed on the client machine that has the developer product installed. To start the session manager, run db2dbgm.bat file from the product Install bin directory.

    2.8 Data Core Functionality

    Workaround: When this happens, you can select the container that contains the container object and try to refresh again. For instance, if refreshing a table fails, then try to refresh the schema that contains the table. If the retries still fail, you will have to disconnect the database and do a reconnect.

    2.9 Single column of XML data type in Table Data Editor

    If you define a table with a single column of XML data type, or any table with non-unique rows, and then use the table editor to delete a row, all rows that match the selected row are deleted.

    Workaround: Do not use the table data editor to delete a row in a table with duplicate rows.