This section includes the list of issues that is fixed.
This section contains the following topics:
The following issues are fixed in this release:
Problem No.: 11926 Issue No.: 20959018-1 RE WITH DDL/PARSING ERROR
In CA ERwin Data Modeler r8.2, when a specific Oracle 10g model was reverse-engineered using a DDL file, the following parsing error was displayed:
RES-Syntax Error - Line 176. Offset 5 OVERFLOW
RES-Syntax Error - Line 182. oFFSET 132 1000
However, the model was displayed after the process completed.
Problem No.: 12098 Issue No.: 21175555-1 TLX MACRO RETURNS WROONG VALUE
In CA ERwin Data Modeler r8 and r9, the TLX macro returned wrong values for Boolean properties.
Problem No.: 12020 Issue No.: 21044154-1 ERROR IN RE IN DB2 Z/OS V8
In CA ERwin Data Modeler r8.2, when a specific DB2 Z/OS v8 model was reverse-engineered, the following error was displayed only when Properties was selected under Tablespace:
<Level=1><Warning> Error 113 for Properties on 'DB2_Tablespace' at Location.
\DAXConnection_DB2zOS.cpp
Object type identifier = 1075838981
Object id = 754
Property type identifier = 1075849772
<Level=2><Information> ESX-1015: Cache_Capacity has been removed due to an in compatibility with the value of property Cache_Identity_Column_Values.
[Entity:TVIP_DET_HIS_CPN] [Attribute:CPN_ID] [Property:Cache_Identity_Column_Values]
Problem No.: 12099 Issue No.: 21192281-1 UDB 9.7 ALTER DROP ALIAS
In CA ERwin Data Modeler r8.0, when an alias was deleted and the ALTER script was generated for a DB2 LUW 9.7 model, the script was incomplete. The table name from which the alias was deleted was not included in the script.
Problem No.: 12059 Issue No.: 21133126-1 (O)DEFAULT NULL ON DB2 9.1
In CA ERwin Data Modeler r8.2, when a DB2 z/OS 9.1 model that had non-identifying relationships with Nulls Not Allowed was compared against a script or database that was created from the same model, the relationship was shown as Nulls Allowed. This resulted in incorrect differences.
Problem No.: 12061 Issue No.: 21151887-1 CAN'T REMOVE IDENTITY FROM COL
In a SQL Server 2008 model in <ERwin > r8.2, when a domain had identity attached to it, the seed and increment values were shown in the Column Editor and the Forward Engineer script.
Problem No.: 12052 Issue No.: 21144894-1 DDL: EXTRA COLUMN IN DDL
When a specific DB2 z/OS v9.1 model was reverse engineered from a script and the resultant model was modified, at some point the syntax created for a specific index on a specific table showed an extra column.
Problem No.: 12115 Issue No.: 21184985 -1 ORACLE RE NOT WORKING
In CA ERwin Data Modeler r9, when a model was reverse engineered from a specific Oracle 11g database, some of the columns were missing in the tables.
Problem No.: 12120 Issue No.: 21188184-1 REP-1:DPLCT OBJCT NOT CREATED
When a SQL DDL file is reverse-engineered to an Oracle database, errors such as <Level=1><Warning> REP-1: Duplicate Object Not Created appeared although there were no duplicates in the SQL database that was being used.
Problem No.: 12192 Issue No.: 21170298-1 ADDITIONAL RELATIONSHIP
When a model was upgraded from CA ERwin Data Modeler r7.2 to r8.2, a phantom relationship line appeared in the Logical View of a Subject Area. This relationship did not exist in the original model.
Problem No.: 12132 Issue No.: 21183712-1 DB2 ZOS CAPTURE COMPARE PARTS
When a DB2 z/OS v8.1 model that included table partitions was upgraded from CA ERwin Data Modeler 7.x to r8.2 and compared with a model that was reverse-engineered from r7.x, the table partition columns did not convert correctly using the logical names in the reverse-engineered model.
Problem No.: 12300 Issue No.: 21262604-1 CAN'T RE WITH PROCEDURES/FUNCT
CA ERwin Data Modeler r8.2 crashed if procedures or functions were chosen while reverse-engineering to a DB2 z/OS v9 or v10 database. It did not crash if procedures or functions were not chosen.
Problem No.: 12083 Issue No.: 21176687-1 MODEL CAN'T BE OPENED
When a specific model was opened in CA ERwin Data Modeler r8.2.5, the application stopped working after the post load processing Window opened.
Problem No.: 12085 Issue No: 21094129-1, 20114719-2 * DOES NOT GO AWAY AFTER THE MODLE WAS SAVED TO MART
The asterisk on a model did not disappear when expected. The asterisk was supposed to indicate that no changes were made to the model.
Problem No.: 12041 Issue No.: 21126183-1 FE:IDENTITY SYNTAX EVEN AFTER SWITCHING DATATYPE TO STRING
In CA ERwin Data Modeler r8.2, when a model was forward-engineered to SQL Server 2008, the IDENTITY clause was included even if the data type was String, for example CHAR(5). This happened only when the logical data type was numeric and in the physical side the attribute or column was not associated with any User Defined Domain.
Problem No.: 12105 Issue No.: 21197031-1 IMPROPER ENTITY RESIZE ON WIN 7
When CA ERwin Data Modeler r8 was used with Windows 7 and the display setting was changed to Medium-125%, then the size of the entity drawing objects expanded beyond what was required to display the entity and attribute names and greatly affected the layout. In some cases, entities even overlapped.
Problem No.: 12084 Issue No.: 21176431-1 DIAGRAM DISPLAY UI DOES NOT REFRESH WHEN CHANGE INDEX TYPE
In CA ERwin Data Modeler r8.2, when AK index was changed to IE index by clearing the Unique check box in the Index Editor, the index was changed but the diagram did not refresh.
Problem No.: 12089 Issue No.: 21174597-1 VALIDE LOGICA ONLY OBJECT DURING PHYSICAL MODEL VALIDATION
In CA ERwin Data Modeler 8.2, when a Logical/Physical model included objects that were marked Logical Only, such objects were wrongly reported in the Model Validation Report when Check Model was clicked.
Problem No.: 11707 Issue No.: 20725187-1 TRANSFORMED RECURSIVE MM RELATIONSHIP HAS HIDDEN RELATIONSHIP LINE
In CA ERwin Data Modeler r8.1, when a many-to-many recursive relationship was right-clicked and transformed an entity with a single relationship was created. However, in the previous versions of CA ERwin DM, the same action resulted in one entity with two relationships.
Problem No.: 12118 Issue No.: 21195237-1 WRONG CONSTRAINT NAME IN SQL SYNTAX AFTER PK COL NAME CHANGE
In CA ERwin Data Modeler r8.2, when an ALTER script was generated for a SQL Server 2008 or an Oracle 10g or 11g database, the script included incorrect constraint name when the names of the parent table and the primary key of the parent table were changed.
Problem No.: 12147 Issue No.: 21222338-1 API CRASH WHEN COMMITTING THEME_REF UPDATE
In CA ERwin Data Modeler r8.2, the API crashed when the Theme_ref property was updated and then committed.
Problem No.: 12187 Issue No.: 21252390-1 SYNC WITH MODEL SOURCE/ONLY TABLE SYNC, NO COLUMN EXPORTED
When a model that was created in CA ERwin Data Modeler r7.3.10 was synched with a model that was created in r8.2.05, there were no columns in the Resolve Difference dialog. When the arrow to export a table was right-clicked in the logical model, only the entity name was exported to the physical model. No columns were exported from the Logical Only model.
Problem No.: 12215 Issue No.: 21273852-1 RELATIONSHIP LINES SKEWED
When a specific model that was created in CA ERwin Data Modeler r8.2.5 was opened in r8.2.6, the relationship lines were skewed.
Problem No.: 11969 Issue No.: 21009962-1 Index Constraint Name Db2 Zos
In CA ERwin Data Modeler r8.0, when a DB2 z/OS database was reverse engineered, the constraint name created in the model was different from the constraint name available in the database.
Problem No.: 12027 Issue No.: 21092984-2 Sync W/model Source Noise
In CA ERwin Data Modeler r8.2, synching with a model source was cumbersome for a particular model. The Resolve Differences screen included too many unwanted differences.
Problem No.: 12091 Issue No.: 21179517-1 MITI EXPORT FAILS
In CA ERwin Data Modeler r8.2.5, when a specific model was exported to the MITI bridge "W3C XML Schema 1.0 (XSD)", the application crashed.
Problem No.: 12223 Issue No.: 21266085-1 Cc Sql Server Col Udps
In CA ERwin Data Modeler r8.2.6, the Complete Compare function did not compare SQL Server extended properties (UDPs), whether at the database or the Physical level compare.
Problem No.: 130205 Issue No.: 21053050 ENHANCEMENT REQUEST COMM/DROP
When a NOT Null column is added to a table, CA ERwin Data Modeler usually generates the RENAME, CREATE, INSERT, and DROP statements in the FE or ALTER script. Sometimes, when the Not Null column does not have a default value, the INSERT statement fails when the model is forward-engineered. The DB2 z/OS FE template has been updated and a comment is added between the INSERT and the DROP table. The comment advices users to ensure that the INSERT statement is successfully executed before executing the DROP statement.
Problem No.: 11596 Issue No.: 20544802-2 SYNTAX ERROR IN DDL
In CA ERwin Data Modeler r7.3, for SQL Server 2005 and 2008 models, if a schema was added to a Domain, the schema was appended correctly to Create Rule, but was incorrectly appended in the syntax for the data type.
For example:
============================
CREATE TABLE dbo.Tbl_Name
(
col1 char(18) NOT NULL,
col2 dbo.decimal(18,3) NULL
)
go
============================
In the example col2 is associated with a Domain, but in FE options the corresponding domain was not selected.
Problem No.: 12199 Issue No.: 21259056-1 POST-UPGRADE ERRORS W/ ADDINS
When a specific model was upgraded from r7.3 to r8.2, custom add-ins were run and the model was viewed using ERwin Spy, the following error appeared:
Failed to init the tree view due to Model Objects Component ! Attempt to access a collection with invalid root object. The root model object with {799A0437-D91A-4CC5-998A-7C23E2130F39}+00000001 id is not available.
Problem No.: 12214 Issue No.: 21270454-1 DB2 PARTITION INDEX FIX
In CA ERwin Data Modeler r8.2.5, when a DB2 z/OS version 8.1 or 9.1 model was forward-engineered, the partitioned index statement in the DDL included ending range values, although the values were already defined at the table error. This resulted in the following error:
DSNT408I SQLCODE = -199, ERROR: ILLEGAL USE OF KEYWORD ENDING. TOKEN ) ,
WAS EXPECTED
Problem No.: 11968 Issue No.: 21021841-1 DB2 ZOS COMPARE NULL
When a specific DB2 z/OS v9.1 model was converted from r7.3.11 to r8.2.03, the columns that previously had the NULL option cleared were converted to NULL and displayed in the Column Editor. However, when this model was forward-engineered, these NULL values did not appear in the DDL.
Problem No.: 12058 Issue No.: 21131437 IDENTITY IS NOT BROUGHT IN WHEN RE DB2
In CA ERwin Data Modeler r8.1, when a DB2 z/OS 9.x database was reverse-engineered, the IDENTITY column was not available in the new model.
|
Copyright © 2013 CA.
All rights reserved.
|
|