IBM Support

Fixed APAR list for IBM InfoSphere Data Architect, version 7.5.2

Product Documentation


Abstract

This document lists APARs and other key customer issues that are fixed in InfoSphere Data Architect, version 7.5.2.

Content



Component
APAR number
Description
Compare and syncJR32423When comparing two models, selecting one change for a merge, results in the automatic selection of other dependent changes, even if the dependent changes are not required for the merge.
Compare and syncJR32780Order of ALTER TABLE statements to add columns should be consistent with the column order.
Compare and syncJR32124Differences are seen when comparing a data model with the original source immediately after reverse engineering.
Compare and syncJR32928Incorrect deltas are shown when comparing and merging two logical data models that contain multiple diagrams.
Compare and sync/physical data modelingJR32082Columns are being removed during compare and synchronization of Informix 11.5 physical data models.
DDL GenerationPK83421If you try to generate DDL for a physical data model schema that was created from reverse engineering from a DDL file, and that targets DB2 Version 9.1 for Linux, UNIX, and Windows, you might see an error that states "DDL Generation did not complete successfully". No output gets written to the .log file.
DDL GenerationJR32837For DB2 for z/OS indexes, PADDED or NOT PADDED keywords are generated during DDL generation even if index does not contain VARCHAR columns.
DDL GenerationJR32422PARTITIONED statement is missing from the generated DDL for a partitioned unique index if key columns are included in the properties for a key column but a column is not included in the table's key columns properties.
DDL GenerationPK85379
PK85378		No support for fully qualifying the index name in a LABEL ON clause.
DDL Generation/Physical data modelingJR32361If a column is deleted from a physical data model, and the column is included in an index, the column is not deleted from the index and DDL generation does not completed successfully.
Data extract and loadPK83951Loading data that includes Spanish characters from a .data file causes an error.
Data extract and loadPK84883When loading data from a .data file, existing data is replaced whether or not you check the "Replace existing data" check box in the wizard.
Data design projectJR33074Opening a Microsoft Word or Microsoft Excel file from the Data Project Explorer causes an error.
Data model diagrammingJR33221Undo of 'Show Implicit Relationship' does not clean up properly.
Data model diagrammingJR25540New Overview Diagram wizard should change the default setting of 'Infer Implicit Relationship' to unchecked.
Data model diagrammingJR33125Deleting a diagram after merging diagrams from two models into another model results in parts of the original diagrams being unexpectedly deleted.
Data diagrammingJR32414Korean translation for "Many-To-Many" relationship in the data diagram palette is translated incorrectly in Korean.
Data model diagrammingJR31708Non-identifying relationship with an optional foreign key relationship is not created properly.
Data model diagrammingJR23891Cannot reference a column of a table to the primary key column of the same table when using UML notation.
Data model diagrammingJR31201Diagram surface does not update after changing the "Required" option for an attribute.
Data model diagramming/Data model reportingJR31257Text from a note on a data model diagram is not included when you generate a data model report.
Data model import and exportJR32927CA ERwin SQL Server 2005 physical data model is imported as a DB2 model.
Data model import and exportJR32870CA ERwin IDS physical data model import to IDA: Columns with data type SERIAL are importing as INTEGER
Data model import and exportJR32954Cannot import an XSD file to a physical data model.
Data model reportingIC61085Generating a report from a large glossary model imported from Business Glossary results in a blank report and an "Out Of Memory" error is written to the log file.
Data model reportingJR32976Product freezes when generating a BIRT report for a large schema in a physical data model.
Data mode reportingJR32979BIRT reports do not contain all of the columns for a primary key.
Data model transformationJR32985When transforming a logical data model to an existing physical data model, the target for a dependency on an attribute is lost, even if the "Generate traceability" check box is checked.
Data model transformationJR31274When performing physical-to-logical data model transformation for an entity with two foreign key attributes that reference the same parent entity results, duplicate foreign key constraint names are generated for the two attributes when using the "Use Title Case" or "Use Lowercase" options.
Data model transformationJR31608LDM-to-UML transformation result using a Japanese locale is missing the LogicalDataModel profile.
Data model transformationJR26132Data server preference on Data Type Map preference page is not persisted.
Data model transformationJR27254Specified source for LDM-to-UML transformation does not persist.
Data model Web publishingJR32986HTML links for a data model that contains DBCS characters that has been published to the Web do not work.
Data model Web publishingJR32020Cannot publish an Informix or Teradata physical data model to the Web.
Data model Web publishingJR32951HTML Web published in Korean shows unicode values instead of Korean characters.
Data Source ExplorerPK80163Error when you select a filter for an Oracle stored procedure that is contained in the Packages folder.
Database connectionsJR31431Default driver path is wrong when connecting to an iSeries database if you do not have local DB2 installation.
Domain data modelingJR32136Exception when opening a model that references a domain model that is not in the workspace.
Help ContentsPK76867Connection to remote information center fails.
Logical data modelingJR32959Data Project Explorer does not show the attributes that are contained in an entity in a sorted or ordered manner.
Logical data modelingJR29814The Cancel button in Key Migration dialog does not cancel the entire Add / Delete relationship process.
Logical data modelingJR31994Opening a logical or domain data model from EME results in the product freezing.
Logical data modelingJR32105When a primary key attribute for an entity is deleted from a model in the Data Project Explorer, it is not deleted from corresponding diagrams.
Logical data modelingJR32533The product needs to update the foreign key in a logical data model where information is missing.
Logical data modelingJR31743Clicking elements with external references displays an error.
Logical data modelingJR32504Order of a primary key cannot be changed when a child entity has a relationship with another entity.
Logical data modelingJR32198Copy/paste is not working for multiple attributes.
Logical data modelingJR32690When an attribute that is part of a primary key for an entity is deleted, it should be automatically removed from the primary key.
Logical data modelingJR32452Properties view error when drawing relationships between entities that were created from an XSD-to-LDM transformation.
Logical data modeling/Data model transformationJR33079After UML-to-logical data model transformation, cannot add new objects to the generated overview diagram.
Mapping modelingJR27928Creating a mapping model takes too long to complete.
Mapping modelingJR31230Error indicators are seen in the mapping model editor if an entity or attribute name contains a slash character ("/").
Physical data modelingJR30557Errors are seen when reverse engineering a physical data model from an Oracle 10g DDL script.
Physical data modelingJR33214Table space definitions are lost when moving tables from one schema into another schema
Physical data modelingJR33173DB2 for Linux, UNIX, and Windows version 8.2 table space does not appear in a physical data model in the Data Project Explorer after being dragged and dropped from the Data Source Explorer .
Physical data modelingJR33087When you reverse engineer an Oracle v10g database into a physical data model, only RANGE partitions are created. Other types of partitions show an error.
Physical data modelingJR33081When you reverse engineer an Oracle v10g database or DDL script into a physical data model, synonyms are not included in the model.
Physical data modelingJR32685Table not found when reverse engineering a physical data model from a DB2 for z/OS or DB2 for Linux, UNIX, and Windows database.
Physical data modelingJR32768
JR32916		Problem setting 'Generated' and 'Primary Key' properties for a DB2 Version 9.5 for Linux, UNIX, and Windows column in the Properties view.
Physical data modelingJR32323Unable to delete schema and no error message given.
Physical data modelingJR32332When reverse engineering from a DB2 for Linux, UNIX, and Windows Version 8.1 database, the DEVICE keyword is replaced with FILE.
Physical data modelingJR32461Oracle package bodies that are created in a physical data model or created through reverse engineering are not persisted in the physical model.
Physical data modelingJR31971Creating a DB2 for Linux, UNIX, and Windows physical data model by reverse engineering a DDL file that contains CREATE TABLE statements with nested SELECT statements results in an error.
Physical data modelingJR32366Creating a physical data model from a DDL file that contains TIMESTAMP columns generated on update results in an error.
Physical data modelingJR31741Sort order change for an index is not saved.
Physical data modelingJR31368Label properties of a primary key table are not carried over to a table that has an identifying relationship to the primary key table.

[{"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":"7.5.2","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 June 2018

UID

swg27015776

Page Feedback