IBM Rational Data Architect Version 7.0.0.3 - Release Notes

1.0 About this release

IBM^(R) Rational^(R) Data Architect Version 7.0.0.3 contains enhancements and fixes to the Version 7.0, Version 7.0.0.1, and Version 7.0.0.2 releases. This fix pack is cumulative, and contains all fixes and new features from Versions 7.0.0.1 and 7.0.0.2, as well as the additional features and fixes described in the following sections.

Back to the table of contents.

1.1 New in this release

IBM Rational Data Architect Version 7.0.0.3 introduces new features or enhancements for the following components:

• General
• Data modeling
• Data diagramming
• Data model import and export

General

• Support is available for Teradata. Reverse engineering from a DDL script is not yet supported.

Data modeling

• Eclipse Business Intelligence and Reporting Tools (BIRT) data model reports:

  You can generate BIRT reports from data models. You can continue to generate classic reports for logical, physical, glossary, and mapping models with fixed content and format, which were available in previous versions of Rational Data Architect, or you can select to generate BIRT reports. Several sample reports are included with this release, which can be used as templates or further customized in the BIRT report designer. To create a BIRT report, select a data model object in the Data Project Explorer, click Data > Publish > Report, and specify in the dialog that opens which type of report you want to create. In addition, you can now generate data model reports from the Report Explorer. To use this method, select a data model object in the Data Project Explorer, right-click a report design in the Report Explorer, and select Generate Report.The following types of reports can be generated:

  • Diagram report
  • Logical data model report
    • Attribute report
    • Relationship report
  • Physical data model report
    • Column report
    • Tablespace report
  • Glossary model report
  • Domain model report
  • Mapping model report

  There is new detailed online help available for BIRT reports. Click Help > Help Contents to view the online help. See the known problem list for BIRT reporting for some known problems and workarounds.

• Apply Index wizard:

  The new Apply Index wizard helps you easily create a new index based on the same properties and naming convention as an existing index. This wizard is similar to the existing Apply Table Space wizard. To use this wizard, right-click an existing index in a physical data model in the Data Project Explorer, and select Apply Index.

• Auxiliary and volatile table support for DB2 for z/OS:

  You can create an auxiliary table by right-clicking a DB2 for z/OS schema and selecting Add Data Object > Auxiliary Table. You can specify a table as volatile on the General page of the Properties view for a DB2 for z/OS table.

• Prefix and suffix specification for table names:

  You can specify a prefix and suffix for table names on the Data > Naming Standard page of the Preferences window. This preference is used when new table names are generated, and also if naming standards are used during data model validation.

• Data model transformation enhancements:
  • Bidirectional support for LDM-to-UML and UML-to-LDM transformation compare and merge.
  • During logical-to-physical data model transformation, there is a new option in the Transform to Physical Data Model wizard to place all key columns first in a table.
  • There are now two separate data type mapping Preferences pages for logical-to-physical and physical-to-logical data model transformation. Previously, the same Preferences page was used for both transformation directions (JR27232).
  • You can now specify a template model in the Transform to Logical Data Model wizard. The resulting logical model is a copy of the template model with the addition of the logical model elements that result from the transformation.
  • Target package and schema browsing in physical-to-logical and logical-to-physical data model transformation: When you are transforming using a template model or transforming to an existing model, you can now browse packages or schemas in the target model and specify one as the target. The default target is the root package or schema of the template model or existing model. The resulting logical or physical elements are contained in the target package or schema and resulting relationships are resolved to existing elements in the target package or schema.
• Logical data modeling enhancements:
  • Support for the NUMERIC data type in logical data modeling and logical-to-physical data model transformation.
  • Support for derived attributes in logical data modeling and logical-to-physical data model transformation.
  • New Enforced property for relationships in logical data models.
  • You can create logical data model elements from RequisitePro requirements, and you can create requirements from logical data model elements. To use this feature, you must have IBM Rational RequisitePro installed. You can drag and drop data elements from a logical data model to a RequisitePro project, and you can drag and drop requirements to a logical data model in either the Data Project Explorer or in a data diagram. Drag and drop from the from the Link Clipboard to the diagram and undo of drag and drop from the Requirement Explorer to the diagram are not supported (JR27209).
• Key migration enhancements:

  You can specify whether to delete or modify foreign key attributes in a physical or logical data model if related primary key attributes are deleted or modified.

• Reverse engineering enhancements:
  • LABEL ON ... TEXT IS clause for tables and columns is now supported when reverse engineering from a DB2 for iSeries database. Reverse engineering from a DDL script is not yet supported.
  • You can now reverse engineer from Microsoft Access using the Generic JDBC driver.

Data diagramming

• The Column compartment in data diagrams is now enabled by default, improving usability.
• When a data model is opened, child diagrams are no longer automatically opened, improving data model performance.
• Other diagram performance issues have been addressed (JR26801).

Data model import and export

• You no longer need to manually set the path to the import export plugin in your system variables.

1.2 Product fix history

Problems in the following components have been fixed in this release:

• Data modeling and diagramming
• Data model import and export

Data modeling and diagramming

• Drag and drop of iSeries Schema from Database Explorer to Data Project Explorer Is failing.
• Reversed directional relationship cannot be added if names of chained relationships are null (PK51482).
• The default value of the attribute of an entity disappears in the Properties view if you click again in the Default Value field (JR27037).
• Incorrect domain details in a physical data model are generated when entities in a logical data model are referencing atomic domains under nested packages (JR27164).
• Unexpected changes are shown in the compare editor during CVS synchronization when a logical model is split across two or more resources and there is at least one non-default relationship with ends in two separate resources .
• Error comparing two domain or glossary models in the Resource Perspective.
• UML to LDM re-transformation does not preserve names of foreign keys upon deletion and recreation of relationships in UML (JR26042). The following changes were implemented:
  • Change the generation of foreign key attribute name to be deterministic and to be more compliant with UML semantics:
    • Use the name specified in the LDM profile, if it exists.
    • If a role is specified, use the primary key attribute name from the parent entity prefixed with the role name as the generated attribute name for the foreign key.
    • If a role is not specified, use the primary key attribute name from the parent entity.
    • If the generated attribute exists, provide an detailed message in the error log so users can fix the UML model.
  • Add syntax and name checking in the UML-to-LDM transformation and generate error messages in the log when errors are encountered so users can fix them.
• Type, Null, and Description of table columns are not output when creating a physical model PDF report in a double-byte character environment (JR26681).
• When creating references to a source model that is stored in ClearCase, the source model is checked out but not modified, while the model is modified but not checked out (JR26921).
• The Separate button in the compare editor is not enabled after pairing two items in a data model.
• Primary key created during logical-to-physical transformation is not compliant with naming standards (JR27225).
• An erroneous error occurs during model analysis if some relationships have an empty inverse verb phrase (JR27381).
• Check constraints in generalization entities are not created in subtype tables in a physical data model after logical-to-physical data model transformation (JR27398).
• Relationship settings are not preserved during logical-to-physical data model transformation for a DB2 for z/OS Version 8 server in new-function mode (JR27466).
• NullPointerException when the properties of a relationship in a logical data model are modified.
• The deferrable constraint option is not enabled in the Properties view for Oracle (JR26284).
• Table indexes are not generated when reverse engineering an Informix 10 database into a physical data model (JR26383).
• ON UPDATE clause is erroneously generated for DB2 for z/OS Version 8 (New-Function Mode) when generating DDL from a physical data model (JR26663).
• Opening a data model in a project causes another data model to be opened and the data models cannot be selectively closed (JR26397).
• Cannot close all editors if data models have circular dependencies.
• Layout Constraint and Font Style information is not stored for a logical data model diagram (JR26959).
• Incorrect domain details are generated in a physical data model when entities in a logical data model referencing atomic domains under nested packages (JR27164).
• Data model analysis does not flag two attributes with the same name in a logical data model.
• Data model analysis erroneously returns a key constraint check violation warning for a many-to-many relationship in a logical data model (JR27246).
• Merging an attribute deletion between two logical data models in the Resource perspective by using the compare editor returns an error.

Data modeling import and export

• Circle M's appear when importing an RDA model into Rational Rose, which originally came from Rational Rose (JR26895).
• Select SE 7 to RDA import: fixed Synonym import issue.
• Ca ERwin 4.x to RDA import: fixed data type mapping issues.
• RDA to XML export: fixed diagram with Notes issue.
• Fixed RDA to Microsoft Excel export issue.
• Fixed export RDA Domain model issue.

Back to the table of contents.

2.0 Installation information

This section describes the installation requirements and specific installation instructions for this fix pack.

Important note about upgrading from Microsoft Windows XP to Windows Vista:

If you plan to upgrade your Microsoft Windows XP operating system to Windows Vista and IBM Rational Data Architect, Version 7.0 is currently installed, refer to the instructions on the Support Web site, http://www.ibm.com/support/docview.wss?uid=swg21257411.

For information about installing Rational Data Architect, Version 7.0, including installation prerequisites, see the Installation Guide online at http://www3.software.ibm.com/ibmdl/pub/software/rationalsdp/v7/rda/70/docs/install_instruction/install.html.

For instructions on installing Rational Data Architect on a Windows Vista computer for the first time, see Installing Rational Data Architect, Version 7.0.0.3 on a Windows Vista computer.

2.1 Hardware requirements

There are no additional processor or memory requirements for installing this fix pack; however, there might be additional disk space requirements depending on whether you are installing the fix pack at the same time that you install Rational Data Architect, Version 7.0 or if you are installing the fix pack as an update:

• If you are installing the fix pack at the same time that you install Rational Data Architect, Version 7.0, then the disk space requirements are essentially the same as for version 7.0.
• If you are installing the fix pack as an update, however, you might need up to an additional 2 GB of disk space. Your actual disk space requirements depend on the features that you selected when you installed version 7.0 of the product.

If you choose to download the update as a compressed file for local installation, you require approximately 2 GB to store and extract the compressed file.

2.2 Software requirements

This section describes the additional software requirements for installing Rational Data Architect, Version 7.0.0.3; to see the requirements for installing Rational Data Architect 7.0, see the Installation Guide.

Before you can install this fix pack, you must install IBM Installation Manager, Version 1.1. In Installation Manager, if you have not disabled the default setting to search the linked repositories during installation and update, IBM Installation Manager, Version 1.1 is automatically installed on your computer when you attempt to update or install packages using an earlier version of Installation Manager.

If you are extending an Eclipse IDE, then before you install this fix pack you must install version 3.2.2 or higher of the Eclipse IDE and one of the following Java runtime environments:

• For Windows: IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 5.0 service release 4; Sun Java 2 Platform Standard Edition Runtime Environment Version 5.0 Update 11 for Microsoft Windows
• For Linux: IBM 32-bit Runtime Environment for Linux on Intel® architecture, Java 2 Technology Edition, Version 5.0 service release 4; Sun Java 2 Platform Standard Edition Runtime Environment Version 5.0 Update 11 for Linux x86

Note:

For Windows Vista: If you install Eclipse inside the Program Files directory (C:\Program Files), then you must run Rational Data Architect as the administrator. (Right-click the program shortcut and click Run as administrator.

To update an existing Eclipse IDE to version 3.2.2 or later, if you have internet access, complete the following steps:

1. Start Rational Data Architect for WebSphere Software.
2. Click Help > Software Updates > Manage Configuration.
3. In the Manage Configuration dialog box, expand the folder that contains the current Eclipse IDE and click the entry starting with Eclipse Project SDK 3.2.1.r321.
4. In the right-hand pane, click Scan for updates.
5. In the Update Site Mirrors window, select an update site mirror and click OK.
6. In the Updates wizard, on the Search results page, select an Eclipse update site and click Next.
7. Follow the on-screen instructions in the Updates wizard to install the update.

   Note: When you are prompted to verify the update of the features that have not been digitally signed, click Install All.
    

8. After the update completes, in the Install/Update window, click Yes to restart the product.

Now your Eclipse IDE meets the prerequisite version for installing this fix pack.

2.3 Other requirements

Internet access is usually required because, by default, the update is located and installed by Installation Manager directly from the IBM update repository for Rational Data Architect, Version 7.0.

Important: When Rational Data Architect is installed, the location of its update repository is automatically embedded in Installation Manager. For Installation Manager to search the default update repository, the preference Search the linked repositories during installation and updates on the Repositories preference page must be selected. This preference is selected by default.

To install the fix pack from a different repository location (for example, if the fix pack is available on a shared drive or HTTP or HTTPS server), you must add the repository location in Installation Manager. To add a repository location:

1. Start Installation Manager
2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.
3. On the Repositories page, click Add Repository.
4. In the Add repository window, enter the URL of the repository location or browse to it and enter a file path, and then click OK.
5. Click OK to close the Preference page.

2.4 Installation instructions

The following are the two common ways to install this update:

• If IBM Rational Data Architect, Version 7.0, 7.0.0.1, or 7.0.0.2 is already installed on your system, then you can install this update by using the Update Packages wizard in IBM Installation Manager. For general instructions on installing an update, refer to the section "Updating Rational Data Architect" in the Installation Guide. For detailed instructions, see Installing Rational Data Architect, Version 7.0.0.3 as an update.
• If you are installing IBM Rational Data Architect, Version 7.0 for the first time or if you are installing an additional instance of it, then you can install this update at the same time that you install IBM Rational Data Architect, Version 7.0 by clicking Check for updates on the Install page of the Installing Packages wizard in IBM Installation Manager. For general instructions on installing an update, refer to the section "Installing IBM Rational Data Architect using the IBM Installation Manager graphical interface" in the Installation Guide.

  Important - if you are installing Rational Data Architect for the first time on Windows Vista, see Installing Rational Data Architect, Version 7.0.0.3 for the first time on a Windows Vista computer for instructions.

By default, the update is installed directly from the IBM update repository; however, it is also available for download. For details, see the specific installation instructions noted below for Rational Data Architect, Version 7.0.0.3.

2.4.1 Reverting to previous versions of Rational Data Architect 7.0

The rollback feature in the Uninstall Packages wizard and the rollback command for silent installation was not supported in Installation Manager, Version 1.0.0.3 at the time that Rational Data Architect 7.0.0.1 was released. Therefore, if you installed Rational Data Architect, Version 7.0, and then updated to version 7.0.0.1, it is not possible for you to revert to version 7.0 by using the wizard or the command.

Workaround: To revert to an earlier version of a package, you must uninstall the entire package. A single uninstallation procedure removes the version 7.0 package and the upgraded version 7.0.0.1 package. After uninstalling, you need to reinstall the version 7.0 package.

To install Rational Data Architect Version 7.0.0.3, Installation Manager 1.1 is required. Installation Manager 1.1 supports rollback. The following scenarios describe the rollback behavior:

• If you installed Rational Data Architect Version 7.0.0.1 or 7.0.0.2 using Installation Manager 1.0.0.3 or 1.0.0.4, you must upgrade to Installation Manager 1.1, then install Rational Data Architect Version 7.0.0.3. If you follow this scenario, you can roll back to Version 7.0.0.1 or Version 7.0.0.2, but you cannot roll back to Version 7.0. Use the workaround above to revert to Version 7.0.
• If you installed Rational Data Architect Version 7.0 but did not install Version 7.0.0.1 or 7.0.0.2, you must upgrade to Installation Manager 1.1, then install Rational Data Architect Version 7.0.0.3. If you follow this scenario, you can roll back to Version 7.0.

2.4.2 Installing into a package group with other Rational products

If you are installing Rational Data Architect 7.0.0.3 into a package group that is shared with other Rational Version 7.0 products that support sharing with Rational Data Architect (for example, Rational Application Developer) you must update the other Rational Version 7.0 products to the 7.0.0.4 level. RDA 7.0.0.3 cannot coexist with other Rational 7.0.0.3 products.

2.4.3 Installing Rational Data Architect, Version 7.0.0.3 as an update

Install the fix pack with the same user account that installed the product.

Restrictions:

• Rational Data Architect, Version 7.0, 7.0.0.1, or 7.0.0.2 must be installed.
• The product cannot be open when you install this fix pack. Also, ensure that all browsers and other applications opened by Rational Data Architect are closed.

To find and install Rational Data Architect, Version 7.0.0.3 as an update:

1. Start IBM Installation Manager.

   On Windows Vista:

   You must run Installation Manager as administrator. (Right-click the program shortcut and click Run as administrator.)

2. On the Start page of Installation Manager, click the Update Packages button.
3. If a new version of Installation Manager is found, you are prompted to confirm that you want to install it before you can continue. Click OK to proceed. Installation Manager automatically installs the new version, stops, restarts, and resumes.
4. In the Update packages wizard, select the Installed Location for Rational Data Architect and click Next. Installation Manager searches for updates in the Rational Data Architect repository on the Web, as well as any repository locations that you entered. A progress indicator shows the search is taking place.
5. By default, recommended updates are displayed and selected on the Update Packages page. Ensure that you select Version 7.0.0.3 for Rational Data Architect, then click Next.
6. On the Licenses page, read the license agreements for the update. On the left side of the License page; click each item to display the license agreement text.
   1. If you agree to the terms for all of the license agreements, click I accept the terms of the license agreements
   2. Click Next to continue.
   3. On the Summary page, review the information displayed, and then click Update. A progress indicator shows the percentage of the installation completed.
7. When the update process completes, a message that confirms the success of the process is displayed near the top of the page. Click View log file to open the log file for the current session in a new window. You must close the Installation Log window to continue.
8. For Windows Vista: Refer to section 2.5 Starting Rational Data Architect on Windows Vista for information about starting Rational Data Architect on Windows Vista.

2.4.4 Downloading the fix pack for local installations

You can download a compressed file containing the Rational Data Architect, Version 7.0.0.3 fix pack; the files that you extract from the compressed file form a repository for the fix pack. You can install the fix pack from the repository on your own computer, or you can copy the repository to a shared drive or an HTTP or HTTPS server.

To download and install the fix pack, complete the following steps:

1. Download the fix pack from http://www3.software.ibm.com/ibmdl/pub/software/rationalsdp/v7/rda/7003/zips/rda-7.0.0.3.zip
2. Extract the compressed file in an appropriate directory. For example, extract the file to C:\temp.
3. Add the fix pack repository location in IBM Installation Manager:
   1. Start IBM Installation Manager.
   2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.
   3. On the Repositories page, click Add Repository.
   4. On the Add repository window, browse to and enter the path to the repository.config file in the rda7fp3\ directory. For example, enter C:\temp\rda7fp3\repository.config and then click OK.
   5. Click OK to close the Preference page.
4. Install the fix pack as described previously in this document.

   Note:During the process of updating from a local repository, Installation Manager might prompt you for the location of the repository for Rational Data Architect, Version 7.0. If you installed the product from CDs or other media, they must be available when you use the update feature.

2.4.5 Installing Rational Data Architect, Version 7.0.0.3 for the first time on a Windows Vista computer

The steps for Installing Rational Data Architect, Version 7.0.0.3 on a Windows Vista computer are essentially the same as installing on other Windows computers. However, there are some important differences that are summarized below.

Sample installation steps are provided in this section. For additional details and installation scenarios, see the Installation Guide.

Installation notes for Windows Vista:

• You must run Installation Manager as the administrator. (Right-click the program shortcut and click Run as administrator.) It is not sufficient to run as a user in the administrator group.
• If you are starting the installation of Rational Data Architect from the launcher program, then you must run the launcher program as the administrator.

  Note:

  If the launcher program starts automatically (for example, if you are installing from a CD), stop the launcher program and then restart it using the Run as administrator command; navigate to the CD or disk image, right-click on install_win32.exe (at the top level of the CD or image) and click Run as Administrator.

• Selecting installation directories within the Program Files directory (typically C:\Program Files) is not recommended.

  Note:

  If you select either an installation location or shared resources directory within the Program Files directory, then the packages that you install must be run as administrator. See 2.5 Starting Rational Data Architect on Windows Vista for details.

Sample installation steps for Rational Data Architect, Version 7.0.0.3 on Windows Vista

1. If you have not done so already, read the release information by opening the readme.html file in the Documents\ folder.
2. Start the installation launcher program as administrator. (Right-click the installation launcher (install_xxx.exe) and click Run as administrator.
3. If IBM Installation Manager is not detected on your system, then you are informed that you must install it before you can continue.
   1. Click OK to install IBM Installation Manager. The IBM Installation Manager installation wizard starts. Follow the on-screen instructions in the wizard to complete the installation of IBM Installation Manager.
   2. When the installation of IBM Installation Manager completes successfully, click Finish to close the wizard.
   3. Read the message that opens and click OK. Installation Manager starts and automatically opens the Install Packages wizard.
4. If IBM Installation Manager is detected on your system, Installation Manager starts and automatically opens the Install Packages wizard.
5. On the Install page, click Check for updates.
6. If a new version of Installation Manager is found, you are prompted to confirm that you want to install it before you can continue. Click OK to proceed. Installation Manager automatically installs the new version, stops, restarts, and resumes.
7. Click Check for new updates and extensions and select the latest version of the product (7.0.0.3).
8. Follow the on-screen instructions in the Install Packages wizard to complete the installation. Note that you should not choose a Shared resources directory or an installation location in the Program Files directory (C:\Program Files).

2.5 Starting Rational Data Architect, Version 7.0.0.3 on a Windows Vista computer

If the installation location or shared resources directory for Rational Data Architect is in a directory in the path C:\Program Files, then you must run Rational Data Architect as the administrator. To run as administrator, right-click the program shortcut and click Run as administrator.

On Windows Vista, the Program Files directory is virtualized in order to allow users who are not running as the administrator to have write access to this protected directory. However, the virtualization workaround is not compatible with Rational Data Architect.

If you selected an installation location or shared resources directory in the path C:\Program Files and you do not want to require running Rational Data Architect as administrator, then do one of the following steps:

• If you selected an installation location in a directory in the path C:\Program Files, then reinstall Rational Data Architect (and any other programs sharing the same installation location) and select an installation location that is not in the path C:\Program Files.
• If you selected a shared resources directory in the path C:\Program Files, then reinstall Rational Data Architect and all Rational Software Development Platform products (regardless of their installation location) and select shared resources directory and installation locations that are not in the path C:\Program Files.

For more information on running Rational Data Architect on Windows Vista, refer to the technote at http://www.ibm.com/support/docview.wss?uid=swg21257842

2.6 Uninstalling the fix pack

See Reverting to a previous version of Rational Data Architect 7.0 for additional information.

Before you uninstall Rational Data Architect, Version 7.0.0.3, perform the following steps:

1. Log in with a user account that has the same privileges as the account that was used to install the packages to be uninstalled.
2. Close Rational Data Architect, Version 7.0.0.3 and any other applications that you installed with IBM Installation Manager.
3. If any applications opened by Rational Data Architect are still open, such as a browser or IBM WebSphere Application Server, then close them.

To uninstall Rational Data Architect, Version 7.0.0.3:

1. Start IBM Installation Manager.
2. On the Start page, click Uninstall Packages.
3. Follow the instructions in the wizard.

For additional instructions on uninstalling Rational Data Architect, see the Installation Guide or see the Installation Manager online help.

3.0 Known problems, limitations, and workarounds

The following information is the currently known limitations, problems, and workarounds. The Rational Data Architect Support Web site also contains technotes and service flashes that describe changes to the documentation and known limitations and workarounds that were discovered after this document was created. The Rational Support Web site address is: www.ibm.com/software/data/integration/rda/support/

• Samples and Tutorials Galleries on Windows Vista
• Connecting to ODBC sources on Linux or Windows
• MySQL
• BIRT reporting
• Compare and synchronization
• Impact analysis on Linux
• Data diagrams
• Physical data modeling
• Data model transformation
• Data model import and export
• Domain data modeling
• Reverse engineering from a DDL file
• DDL generation
• DDL parser for DB2 for z/OS
• DDL parser for Oracle
• Server discovery
• Discover function and mapping editor
• Federation support
• Object name character limitations
• ClearCase
• RequisitePro
• SQL Tools
• XML
• Routine development
• Stored procedure debugger
• Table data editor
• EMF Preferences window error

Samples and Tutorials Galleries on Windows Vista

-- The Samples Gallery and Tutorials Gallery do not support the new high resolution display setting "Larger scale(120DPI)- make text more readable" on Windows Vista operating system. The gallery content does not display if this option is set.

This setting enables through the following steps:

1. Open the Control Panel.
2. Click Ease of Access Center > Make Computer easier to see > Change the size of text and icon.
3. Select  Larger scale(120DPI)- make text more readable.
4. Click Save settings.

Workaround

If you changed to the new high resolution display option, change to a lower resolution setting (for example, the default 90 DPI setting).

-- On the Japanese version of the Windows Vista operating system, the Samples Gallery and Tutorials Gallery require Mozilla Firefox as the Web browser preference; the gallery content does not display on other Web browsers.

Workaround

 Install Mozilla Firefox, and then set the Web Browser preference to Mozilla Firefox (click Window > Preferences > General > Web Browser).

Connecting to ODBC sources on Linux or Windows

Due to a JDK problem with previous releases, you might not be able to connect to ODBC data sources using RDA on Linux or Windows unless you have DB2 Universal Database for Linux, UNIX, and Windows version 8.2 FixPak 11 or later.

MySQL

Limited support for MySQL 4.1: The following properties are not displayed correctly in the Properties view: unique index, auto increment columns, column default value for NULL and binary. In addition, C procedures and functions are not supported.

BIRT reporting

• By default, you can only create BIRT reports in HTML format. To enable PDF format, you must download the itext-1.3.jar file from the BIRT download site on eclipse.org and copy it into the eclipse/plugins/com.lowagie.itext_*/lib directory. If the lib directory does not already exist, add the directory.
• Joint dataset sometimes returns an incorrect result in a BIRT report.
• The parameter window does not open if a BIRT relationship report is generated from the Data perspective. To work around this problem, generate relationship reports from the Report Design perspective by selecting File > View Report as HTML or File > View Report as PDF.
• Package and constraint counts are not represented in Domain reports.

Compare and synchronization

• Sometimes a Compare With > Original Source action does not complete because the database connection timed out. To work around this problem, you can either disconnect from and then reconnect to the database, or reset the connection time-out limit to a very large number such as 9000. The default value is 120. To change the connection time-out limit, click Window > Preferences > Data and enter a new value in the Connection timeout field.
• If you have installed the ClearCase Remote Client, you must complete some setup steps before you can use the data object compare editor to compare an object that is under source control. If you do not perform these steps, you will see an xtools error message when you try to compare objects that are under source control.
  1. Click Window > Preferences.
  2. Expand the the ClearCase Remote Client node under the Team node and click Editors/Workspace.
  3. Select Use tools in the IDE if they support the selected file type in the When comparing and merging files area.
• When you are using the compare editor to merge data objects, do not edit the objects that you are comparing outside of the compare editor. For example, do not make changes in the Properties view. If you edit the objects outside of the compare editor, you might see an error message or unexpected behavior.
• Some results of compare and synchronization show no differences between some data type changes.
• When you compare an object in the Database Explorer with another object, and then synchronize the information, the DDL that is generated is not always accurate.
• When you are comparing objects in the compare editor and you perform a Copy from Right to Left action, the Generate Left DDL button is not enabled.
• In the following scenario, the delta DDL statement from the comparison is generated incorrectly:
  1. Reverse engineer a schema that contains an alias into a physical data model in a data design project.
  2. Modify the existing alias to point to a different table.
  3. Compare the modified alias with the original (right-click the alias object, then select Compare With > Original Source).
  4. In the compare editor, click Copy from Left to Right to copy the changes to the server version of the alias.
  5. Click Generate Right Delta DDL, and save the DDL statement.
  6. The DDL statement is incorrectly generated. It includes a CREATE TABLE statement for the new aliased table, even though that table already exists.

  To work around this problem, modify the DDL statement in the SQL editor before you deploy it.

Impact analysis on Linux

• On Linux operating systems, the Analyze Impact window does not have a default selection for Objects Returned. You must make a selection or you will see an error.

Data diagrams

• The Delete from model action on a diagram shortcut object does not delete the diagram object from the model. To work around this issue, you can delete the diagram object from the model by using the Delete action in the Data Project Explorer.
• Large diagrams can fail to be saved as images when you right-click in a blank area of a diagram and select File > Save As Image File. Entries are created in the log file if logging is enabled, but there is no error message. To work around this problem, break up the large diagram into smaller diagrams.
• On Linux operating systems, diagram print functions do not work.
• The new Zoom icon on the data diagram palette is not accessible from the keyboard. To use this function from the keyboard, select the Zoom menu action from the data diagram toolbar.

Physical data modeling

• When you are creating a new physical data model by using the New Physical Data Model wizard, you might see an error if you manually specify a template location. This error can be safely ignored.

Data model transformation

• When you select a template physical model in the Transform to Physical Data Model wizard, the template support allows the reuse of UDTs only. For example, any UDTs that are defined in the template model and which match the domains (marked as UDT) in the logical data model, are re-used during transformation. Any other information in the template is just cloned, and is not looked up and re-used by the transformation.
• If you transform a logical data model to a UML model, you will see an error that says there is no valid license key for the Transformation Fuse Utility. You can continue with the transformation. but you can only create a new UML model or replace an existing UML model. You cannot merge the transformation to an existing UML model. Comparing and merging to an existing UML model is not supported in Rational Data Architect, but you can use this feature if you have both Rational Data Architect and Rational Software Architect installed in the same Eclipse instance.

Data model import and export

• On Linux operating systems, you cannot run the Data Model Export wizard for IBM Rational Rose and Sybase Power Designer bridges.

Domain data modeling

• If a domain model or a project containing a domain model is renamed, the domain references in the project properties are not automatically updated. To work around this problem, manually add the renamed project or the project containing the renamed model back into the domain references for the project.

Reverse engineering from a DDL file

For DB2 Universal Database for Linux, UNIX, and Windows and zSeries only: By default, the parser assumes that the terminator is the semicolon (";"). If the file uses a different terminator character, you must include the following statement in the first line of your DDL file:

-- <ScriptOptions statementTerminator="@" />

Where "@" is the terminator character that your DDL file uses.

DDL generation

• When you run Generate DDL for a schema with nicknames, you might see a message in the Data Output view similar to the following: Table xxx already has a primary key. The message shown in the Data Output view can be ignored.
• DDL statements for stored procedures whose name requires a delimiter in the DDL statement (for example, CREATE PROCEDURE "a.b") is not generated correctly. The delimiting quotation marks are not generated. In the example statement, the DDL is generated as CREATE PROCEDURE a.b. To work around this issue, modify the generated DDL statement to include the delimiting characters.

DDL parser for DB2 for z/OS

The following DDL statements have limitations:

Statement	Limitations
ALTER TABLE	The following alterations are not supported: ADD PARTITION ADD/DROP RESTRICT ON DROP DROP MATERIALIZED QUERY
SET CURRENT SQLID	Only supported: SET CURRENT SQLID = string-constant
SET SCHEMA	Only supported: SET SCHEMA = schema-name, SET SCHEMA = string-constant
--	The -- style of comments is not supported for DB2 for z/OS.

DDL parser for Oracle

• The REPLACE clause is not supported.

Server discovery

On a Linux operating system, the Undefined Remote Servers do not appear for ODBC data sources, unless you create an ODBC wrapper with the wrapper name ODBC outside of the Rational Data Architect product, such as the DB2 Universal Database Control Center, or a command line. You must name the wrapper ODBC so that it is properly discovered. The wrapper on a Linux operating system is defined with a MODULE wrapper option, as in the following example:

CREATE WRAPPER odbc LIBRARY 'libdb2rcodbc.so' OPTIONS (MODULE '/usr/lib/odbc.so')

In this example, MODULE '/usr/lib/odbc.so' is the full path to the library that contains the ODBC Driver Manager.

Discover function and mapping editor

• The reference to data model files (DBM, LDM or XSD) in an MSL file is not updated automatically when you copy, move, or import the data model files. The mapping editor will not load the MSL file correctly if the reference to the data model files is invalid. Update the reference manually in the MSL file by opening it with a text editor (right-click the MSL file and select Open With > Text Editor). Change the XML attribute "location" of the <msl:inputs> and <msl:outputs> elements to the correct path to the data model file starting with the project name (for example, /myProject/SourceDB.dbm).
• When you switch focus from a mapping line to a tree node in the mapping editor, the property page is empty directly after the switch. To work around this issue, select the tree node again to see the tree node properties.
• There might be some cases when the Advanced Configuration wizard does not recognize your Wordnet installation. If this problem occurs, ensure that the WNHOME system variable is set for Wordnet. The variable should be set to the root directory where Wordnet is installed, for example, C:\Program Files\WordNet\2.1.
• If you run discovery with data sampling algorithms against a DB2 Version 9 for Linux, UNIX, and Windows database and discovery returns an error, run the following bind command from a DB2 command line on the database: C:\SQLLIB\bnd>db2 bind db2schema.bnd
• If you add a bookmark to a mapping line, the bookmark is indicated by an icon on the mapping line in the editor and Outline view, and the bookmark is also added to the Bookmark view. However, the screen reader does not read that there is a bookmark on a mapping line in the mapping editor. To work around this issue, you can use the screen reader to read the bookmarks in the Bookmark view.
• When you launch the Discover Relationships function, be aware that aliases are treated as tables. You should decide whether to include them in the set of source schemas, or the target schema when you define the scope of the discover function.
• For the algorithms that include data sampling, only the data in Oracle and DB2 databases are sampled. To cache the sampled data, you must specify a cache database. Only DB2 UDB for Linux, UNIX, and Windows is supported as a cache database.
• On Linux operating systems, the thesaurus option for the semantic name algorithm using Wordnet and Sureword is not supported. The thesaurus option using a glossary model is supported.
• On Linux operating systems, an ellipsis [...] button is missing from the Data sampling connection information table on the Specify Connection Information for Data Sampling and Caching page of the Advanced Configuration wizard. Without this button, you cannot open a window to select a connection for the target physical data model, so you cannot move forward in the wizard. This problem prevents Signature or any algorithm based on data matching from being used in discovery.
• User Defined Types (UDTs) are not sampled when you discover relationships.
• In the Mapping Editor preferences, when you set the preferences for discovering relationships, the Algorithms page contains a selection for how to order multiple algorithms. You can specify the Composition by sequence or Composition by weight. When you select Composition by weight, this assigns a weighting value to each algorithm. Currently the option only applies to algorithms that return a single value.
• The SQL/XML query generation ignores the actual value of "x" of an XSD attribute maxOccurs="x"' if x is a number greater or equal to 1. The generated query will create XML elements for all rows from a source column. It will not limit the amount of selected rows to the number defined under maxOccurs. This is due to the incapability of SQL2003-conforming SQL/XML queries to express this requirement. For elements that are defined with the attribute maxOccurs="0", the mapping editor prohibits a mapping. Therefore, elements defined as maxOccurs="0" will not appear in the result.
• When UDTs are present on the target side, the generated scripts might not parse due to null value handling for UDTs.
• In the following two scenarios, not all of the artifacts are generated in the DDL script, and the script cannot be deployed without modification:
  • You are mapping from source table T1 in A.dbm to target table T2 in B.dbm, and neither A nor B are federated to an Information Integrator server. In this case, the only deployment platform available will be A.dbm and only an insert script is generated. No table object T2 for A.dbm is generated, even though this is necessary for the script to run. If you want to run the script, you must create the table.
  • You are mapping from source table T1 in A.dbm to target table T2 in B.dbm, and both A.dbm and B.dbm are federated to an Information Integrator server. In this case, the Information Integrator sever is available as a deployment option. However, if you select the Information Integrator server, only the nicknames for T1 and the insert script is generated. You must generate the nicknames for T2 from B.dbm onto the Information Integrator server before the script will run properly.

Federation support

• You can generate DDL scripts for a federated server from the Database Explorer . After you generate a script, you can deploy it to like servers on DB2 Universal Database for Linux, UNIX, and Windows, DB2 Universal Database for iSeries, Oracle, SQL Server, Teradata, Web services, XML, and Sybase. To deploy the DDL scripts on any other data source, you must deploy them using the DB2 command line (run them as DB2 scripts). When you deploy, you might get a message saying that the wrapper already exists. If you see this error, then disconnect from the database and reconnect.
• After you create a federated server in the Database Explorer, the newly created server will not automatically be displayed in the Defined Server folder. You must refresh the folder to see the new server.

Object name character limitations

• Do not create an object that has quotation marks in the name. An object name delimited with quotation marks does not work. The following examples are not currently supported:

  """PROCEDURE"""
  """TABLE"""
  """SCHEMA"""."""PROCEDURE"""

• The mapping editor does not support the slash ("/") character in object names. The following example is not supported in the mapping editor: DBM/NAME

ClearCase

• If you attempt to use the ClearCase SCM Adapter in an environment where the adapter has not been set up, the product will shut down.
• You can not expand the folders of objects in a development project that was checked out by using the ClearCase resource manager.
• You might see the following warning after you install the ClearCase Remote Client for Eclipse:

  The current configuration contains errors and this operation can have unpredictable results.

  You can ignore this warning.

RequisitePro

• All of the menus associated with RequisitePro integration appear in English only.
• A link policy between any requirement type and the Atomic Domain element kind in the Link Policy panel is not honored. To work around this problem, select Data Domain as the Element Kind in the Link Policy panel instead of selecting Data Atomic Domain as the Element Kind.

Glossary modeling

• You cannot access the naming content assist icon in the Properties view by using the keyboard. To work around this issue, click Window > Preferences > Data > Naming Standard to view the naming standard patterns.
• Screen readers cannot read the content assist window in the Properties view. To work around this issue, you can open the glossary model that is associated with the current project in the glossary model editor to read the entries.
• When you create a new glossary model from the File > New menu, the destination folder is blank. To work around this issue, highlight a data project in the Data Project Explorer before clicking File > New > Glossary Model.

SQL Tools

• The SQL Editor does not currently support host variables during the Run SQL action. To work around this issue, you can run the SQL from the SQL builder, if it is a DML statement.
• If you modify a statement in the SQL source area of the SQL builder and then you save the statement while it is invalid, the current text is not saved. Instead, the text that was in the SQL source area before modifications were made to the SQL source area is saved. If you attempt to run the invalid statement from the SQL builder, the last valid statement is run instead.
• In the SQL builder, the product does not draw lines in the graphical tables for conditions that are specified in the WHERE clause that represent a join.
• The full SQL syntax is not supported. For example, User Defined Types (UDTs) and Table functions are not supported.

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.
• If you define a table that contains XML data, but does not include a primary key, updating the XML column will fail in the table editor. You must add a primary key or unique index to the table that contains the XML data.
• Working with multiple root elements in the Annotated XSD mapping editor can lead to errors when you save the annotated XSD file. To work around this issue, create a separate set of XML Schema document files for each root element.
• If you select an XML schema to register for DB2 for Linux, UNIX, and Windows Version 9, and that schema has been registered before in the same project, sometimes the XML Schema Registration wizard shows an additional temporary copy of the same schema in the schema list. You must manually delete the temporary copy before you can complete registration.

Routine development

• If you create a stored procedure with a name like "a.b"."a.b", you can deploy it to a DB2 for z/OS server without a problem, and schema "a.b" containing stored procedure "a.b" is successfully created. However, you cannot drop the stored procedure.
• User-defined types (UDTs) are not supported as parameters for routines.
• When you deploy a stored procedure or a user-defined function using the Ant deployment feature, the following message might appear if you do not have the tools.jar file located in your classpath: Unable to locate tools.jar. Expected to find it in F:\jre\1.4.2\lib\tools.jar. Ignore this message. tools.jar is part of the Java Runtime Environment (JRE), not part of the Ant deployment feature.
• To deploy Java stored procedures that target DB2 UDB for iSeries from the file system by using Ant deploy, you must ensure that you have the jt400.jar in your system classpath.
• When you create a Java stored procedure and change the method name, right-clicking in the editor and clicking Save does not work. To save the updated stored procedure, click File > Save.
• If you attempt to deploy an exported stored procedure by using the instructions in DeployInstructions.txt, you might get an error message that says : ...[createsp] Could not connect to the target database. [createsp] com.ibm.db2.jcc.DB2Driver...To work around this issue, ensure that db2jcc.jar and the appropriate license files are in your system classpath.
• Before you delete a data development project, close the open routines and SQL editors that belong to the project. If you do not close the open routines and SQL editors, the project and its contents will still be deleted, but you will see error messages.
• You might see a cannot load class error when you deploy or run Java stored procedures. This error can occur if there is a mismatch in JDK version between RAD v7 and the DB2 server, if the DB2 server is on a down-level JDK. To prevent this error, 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.
• If you drag and drop a stored procedure or UDF between unlike servers (for example, from a DB2 UDB for Linux, UNIX, and Windows server to a DB2 UDB for z/OS server), you will see a warning during the drag and drop operation about certain incompatibilities between the two servers. If you continue with the operation and then try to open the stored procedure or UDF, you might see an error.
• Running SQL Profiling against a DB2 UDB for Linux, UNIX, and Windows V8.2 server may cause a null pointer exception if the server is missing the prerequisite stored procedure (SYSIBM.SQLCAMESSAGECCSID) that is required by the JCC driver to retrieve error message text. To work around this issue, you can create a connection to the server without the retrieveMessagesFromServerOnGetMessage=true setting.
• During monitoring of the execution of SQL procedures, profiling events are generated for DML statements such as INSERT, SELECT, DELETE, and UPDATE that are issued in the procedure. However, events are not generated in a deterministic fashion for variable assignments and control structures such as WHILE or IF. Therefore, tuning data will not be captured for these procedural statements.

Stored procedure debugger

• In the Data perspective, you might get the "session manager not available" error message when you select the debug option for a stored procedure. The error message indicates that the session manager on the DB2 server is not starting or is unreachable. To fix the problem, you will need to run the session manager that is shipped with the product.

  To start and configure the session manager that is shipped with the product:

  1. Start the session manager:
     • On Windows:
       1. Open a command window and change to the <product installation>\rda\bin directory. By default, the product is installed in the C:\Program Files\IBM\SDP70 directory on Windows.
       2. From the command prompt, run db2dbgm.bat and note the IP address and the port number for the session manager.
     • On Linux:
       1. Open a terminal window and change to the <product installation>/rda/bin directory. By default, the product is installed in the /opt/IBM/SDP70 folder on Linux.
       2. From the terminal window, run sh db2dbgm.sh and note the IP address and the port number for the session manager.
  2. Start the product and modify preferences for the debugger to use the local session manager:
     a. Click Window > Preferences, expand the Run/Debug node, and click DB2 Stored Procedure Debugger.
     b. In the Debugger pane, select Use already running session manager.
     c. In Host field, specify the IP address of the machine. You can also obtain the IP address from the command or terminal window where the session manager is running.
     d. In the Port field, specify the port for the local session manager. By default, the port number is 4554. You can also obtain the port number from the command prompt or terminal window where the session manager is running.
• When you are connected to a UNIX DB2 server, timeout exceptions can occur when you are adding breakpoints or running in debug mode.
• The debugger does not run for a stored procedure whose name contains both English and Chinese characters.
• Watch expressions are only supported for dynamic Java stored procedures. They are not supported for SQL and SQLJ stored procedures.
• The debugger does not stop at a breakpoint if it is not positioned at the first token of an executable statement, such as SET. In addition, it does not stop on DECLARE CONTINUE, CLOSE CURSOR, or ROLLBACK.
• If you are debugging a Java stored procedure and you select a Terminate action, it might take several minutes for the debug session to fully terminate. New debug sessions that are started during this time may behave erratically.
• If you are debugging a Java stored procedure that calls a second Java stored procedure, you cannot debug the second stored procedure. You cannot step into the nested store procedure, and any breakpoints that you set in the nested stored procedure will be ignored. This restriction is for DB2 UDB for Linux, UNIX, and Windows.
• If you get a Timeout occurred while waiting for packet error while you are debugging a Java stored procedure, try increasing the Java timeout setting. 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.
• When you are debugging a Java stored procedure, if you use the Change Value action to modify a variable that has an empty string value, the OK button in the edit dialog might not become enabled. To enable the OK 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.
• If you do not see local variables when you are debugging a Java stored procedure, the stored procedure might have been deployed without the -g compiler option. Ensure that you specify the -g compiler option when you deploy Java stored procedures.
• If you see an 'invalid stack frame' message in the Variables view, go to the Debug view and click on the thread object above the stack frame and then click on the stack frame. This should refresh the Variables view and the error should no longer appear.
• When you are debugging an SQLJ stored procedure that is running on DB2 UDB for iSeries V5 R4, the current line that is being executed will not correspond to the indicated SQLJ source line displayed in the Debug view unless you have applied an iSeries PTF that updates the linemap to correspond to the SQLJ source instead of the Java source.
• Debugger preferences for session manager timeout are not recognized. These preferences are set as follows: Click Window > Preferences, expand the Run/Debug node, and click DB2 Stored Procedure Debugger. Modify the Session manager timeout in minutes field.
• The debugger cannot process a stored procedure that has large number of variables on DB2 for Linux, UNIX, and Windows. The maximum number of variables is 200.
• Cursor movement in a debug session: In some cases, when there is more than one variable declaration in a procedure, you must click Step Into or Step Over more than once in order to move to the next line. For example, you must click twice on this line: DECLARE v_dept, v_actdept CHAR(3); and three times on this line: DECLARE v_bonus, v_deptbonus, v_newbonus DECIMAL(9,2); You must click a number of times equal to the number of variable declarations.
• If you start a debug session for a Java stored procedure and add breakpoints, then disable the breakpoints, the breakpoints are still enabled. To work around this issue, when you start a new debug session, you should first remove all of the old breakpoints and then add new breakpoints.
• In some cases when you are working with multiple data development projects, you might see an error when you attempt to debug a stored procedure that says "Unable to locate stored procedure PROCNAME. Procedure may have been deleted from workspace" or "Source not found".
• If you are debugging a SQL stored procedure right after you terminate a debug session of a Java stored procedure, the debugger might shows "User defined function ... has been interrupted by the user."  To work around this issue, try debugging the SQL stored procedure again.

Table data editor

• If you define a table with a single column of data type XML, 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. To work around this issue, do not use the table data editor to delete a row in a table with duplicate rows.
• 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. To work around this issue, create a primary key for tables that contain XML columns.

EMF Preferences window error

• If you open the EMF Compare/Merge Preferences page, you will see a "no valid license key" error. This Preferences page is not supported in Rational Data Architect, but you can use it if you have both Rational Data Architect and Rational Software Architect installed in the same Eclipse instance.

IBM Corporation
      J46A/G4
       555 Bailey Avenue
       San Jose, CA 95141-1003
       U.S.A.