Product Documentation
Abstract
This document provides the list of APARs fixed in InfoSphere Data Architect version 9.1.
Content
|
Product feature |
APAR ID
|
Description
|
| Data model comparison |
JR45488
|
The compare editor is not showing differences between data objects. |
| Data model comparison and synchronization / DDL generation |
JR45783
|
DDL that contains DROP statements requires more time to generate. |
| Data model publishing: Web |
JR45874
|
The workbench performance slows when publishing a domain model to the web. |
| Data model publishing: Web | JR46452 | Navigation in the data model that is published to the web does not work. |
| Data modeling |
JR45777
|
The abbreviations of InversionEntry objects are not displayed in the Properties view. |
| Data modeling: Physical |
JR46004
|
The default value for the PCTFREE property for a DB2 for z/OS object is too low. |
| Data modeling: Physical / Cross-model references |
JR46282
|
The user sees a warning about cross-model references when copying a column that has a traceability dependency. |
| General product |
JR43290
|
When maximizing the Properties view, the editor is blank. |
| Importing and exporting |
JR43301
|
Exporting large models to the Microsoft Excel format causes an exception. |
| MITI |
JR46139
|
On Linux, the Import and Export wizard does not open. |
| MITI |
JR46156
|
Data models are not exported to the Sybase PowerDesigner 15.3 format. |
| Product upgrade / Workspace migration |
JR45538
|
When migrating a workspace from version 8.1 to version 8.5, atomic domain references are broken. |
| Transformation: Logical to physical |
JR42751
|
In French versions of the product, the number of characters of a database name is high after transformation. |
| Transformation: Logical to physical / General product |
JR46393
|
The content of the context help for the first page of the logical-to-physical transformation is irrelevant. |
| Transformation: Logical to XML schema |
JR44700
|
When transforming from a logical data model to an XML schema, atomic domain references with names that contain spaces are not resolved. |
| Transformation: Physical to logical |
JR46207
|
Non-qualified references to atomic domains are created when transforming from a physical data model to a logical data model. |
Related Information
[{"Product":{"code":"SS9UM9","label":"IBM InfoSphere Data Architect"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
03 April 2020
UID
swg27038343