Product Documentation
Abstract
This document lists the APARs that were fixed for the version 8.1 release of InfoSphere Data Architect.
Content
| Component | APAR or defect number | Description |
| Comparison and synchronization / DDL generation | JR38989 | Pre-iSeries V7.1: After deploying an iSeries physical data model to a database, differences appear when comparing the physical data model to the database. The ALLOCATE property is displayed as a difference. |
| Comparison and synchronization / DDL generation | JR41762 | Incorrect delta DDL is generated when changing a system-period temporal table to a bitemporal table in the same schema when synchronizing all objects except the table name. |
| Comparison and synchronization / Logical data modeling | JR41823 | When you synchronize a relationship that has changed its name, an unnecessary relationship is created in the synchronized model, and a duplicate primary key is created in the synchronized model. |
| Data design projects / Data modeling | JR41261 | Data models are not moved between projects until the data design projects are closed, then reopened. |
| Data design projects / Naming models | JR41219 | If you add a naming model from a different workspace than the current workspace that you are working with, the references to the naming model are removed when you navigate to another tab or view in the workspace. |
| Data model search / Diagramming | JR40644 | When searching in a data model, diagram elements are not found. |
| Data Source Explorer | JR41868 | When connected to a SQL Server 2008 database, columns that use the NVARCHAR data type return an error when loading the length of the column. |
| DDL generation | JR41621 | Duplicate primary keys are generated in DDL for MySQL physical data models, and alter statements are not created when generating the DDL. Comments are included with DDL scripts after disabling comments in the Generate DDL wizard. |
| Diagramming | JR40808 | Self-referential relationships do not appear correctly when you rearrange the data object in the diagram editor. |
| Diagramming | JR41689 | When you add arrows to a diagram, the arrowheads disappear when you close the diagram and reopen it. |
| Diagramming (printing) | JR41597 | You cannot specify a print margin that uses a leading decimal (such as .4 or .8); however, adding a digit before the leading decimal (such as 0.4 or 0.8) does not cause an error. |
| Logical data modeling | JR41623 | The DECFLOAT data type is not supported. |
| Logical data modeling | JR41837 | The documentation field in the Properties view of an attribute does not wrap text. |
| Logical data modeling / Naming models | JR41574 | When you add attributes with abbreviations to an attribute group of an entity, the attributes are created, but the abbreviation of the attributes is not created. |
| Logical data modeling | JR41914 | When an entity contains a primary key that references only one attribute, and alternate keys refer to more than one attribute, you cannot create a valid generalization. Alternate keys become primary keys of the subtype entity, and the single attribute is removed from the primary key. |
| Model analysis / Physical data modeling | JR42052 | When you analyze a SQL Server model, and certain data types of columns are set to the maximum value, the workbench returns an error. |
| Physical data modeling | PJ38702 | Column annotations and documentation of data models created in InfoSphere Warehouse Design Studio is lost when right-clicking on a column and selecting SQL > Update. |
| Physical data modeling | JR39228 | The Volumetrics tab of the Properties view of a table does not support maximum row values larger than 214748364. |
| Physical data modeling | JR41775 | The ON UPDATE option of the foreign key is disabled. |
| Logical data modeling | JR42255 | Submodels of logical data models cannot use an atomic domain type. A stack overflow error occurs. |
| Reverse-engineering / Physical data modeling | JR41012 | When reverse-engineering from a SQL Server 2005 data server, statistics objects are created as index objects. |
| Reverse-engineering / Physical data modeling | JR39072 | The user cannot create a physical data model by reverse-engineering if the connection profile does not specify a database driver. |
| Reverse-engineering / Physical data modeling | JR41696 | The secondary space allocation quantity property of a table space is truncated to 131068 when reverse-engineering from a DB2 for z/OS database. |
| Reverse-engineering / Physical data modeling | JR41690 | The source of a SQL Server stored procedure is incomplete. |
| Task Launcher | JR42408 | The link to the Connect and browse a database task is broken in the Overview tab of the Task Launcher. |
| Transformation (logical to physical) | When an inversion entry of an entity uses the Index property, forward and reverse scanning should be enabled by default. | |
| Transformation (logical to physical) | JR42039 | When you specify that the character case should persist when transforming from a logical data model to a physical data model, tables are created with uppercase characters. |
| Transformation (logical to physical) | Roll-up relationships are not being transformed in a physical data model, which creates duplicate unnecessary tables in the resulting data model. | |
| Transformation (logical to physical) | JR41646 | For physical data models for DB2 for Linux, UNIX, and Windows version 9.1 and earlier: The DBCLOB columns created during the logical-to-physical transformation process can exceed the allowable logging size (1GB) when logging is set. Logging is disabled in the resulting physical data model, even when logging is set. |
| Transformation (logical to physical) | JR40526 | If two entities are connected by a roll-up generalization, the required attribute of the sub-entity is transformed into a NOT NULL column. |
| Transformation (physical to logical) | JR39138 | If a table contains two consecutive separator characters (such as a space or underscore), one separator is lost in the resulting entity. |
| Transformation (physical to logical) | JR40824 | When transforming a MySQL physical data model into a logical data model, not all data types are transformed correctly. |
| Transformation (physical to logical) | JR41920 | Some Sybase data types are incorrectly transformed when transforming from a physical data model to a logical data model. |
| Transformation (UML to logical) | JR42263 | Documentation for a generalization is lost when transforming from a UML model to a logical data model. |
[{"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":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27023730