CA ERwin® Data Modeler - Cloud Object Storage | … · 2017-01-18 · Silent Install for CA ERwin Data Modeler and Crystal Reports (r7.3.6) ... (7.3.12 SP3) ... Chapter 7: Documentation

Release Notes r7.3

CA ERwin® Data Modeler

r7.3.12 SP3 Edition

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

CA Technologies Product References

This document references the following CA Technologies products:

■ CA ERwin® Data Modeler

■ CA ERwin® Model Manager

Contact CA Technologies

Understanding your Support

Review support maintenance programs and offerings.

Registering for Support

Access the CA Support online registration site to register for product support.

Accessing Technical Support

For your convenience, CA Technologies provides easy access to "One Stop" support for all editions of CA ERwin Data Modeler, and includes the following:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

For information about other Home Office, Small Business, and Enterprise CA Technologies products, visit http://ca.com/support.

Provide Feedback

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

If you would like to provide feedback about CA Technologies product documentation, complete our short customer survey, which is also available on the CA Support website, found at http://ca.com/docs.

CA ERwin Data Modeler News and Events

Visit www.erwin.com to get up-to-date news, announcements, and events. View video demos and read up on customer success stories and articles by industry experts.

https://support.ca.com/prodinfo/dmsupportofferings

https://support.ca.com/prodinfo/supportregistration

https://support.ca.com/prodinfo/erwin

http://www.ca.com/support

mailto:[email protected]

http://www.ca.com/docs

http://www.ca.com/docs

http://www.erwin.com/

http://www.erwin.com/

Documentation Changes

This Release Notes document is cumulative - it is updated as features are added or changed during the patch and Service Pack releases.The following list summarizes the documentation updates that have been made since the initial release (r7.3 GA) of CA ERwin Data Modeler:

Chapter 1: New Features and Enhancements

■ Macro Added (r7.3.5)—Addition of the macro DatabaseConnection to the Forward Engineering Template macros.

■ Metadata Integration Bridges Updated (r7.3.2, r7.3.4 SP1, r7.3.8 SP2, and r7.3.11)—List of Import/Export bridges added, removed, and renamed.

■ Enhancement made to Rename Column Dialog (r7.3.4 SP1).

■ Allow Special DBMS Characters check box added to the Derive Wizard, Naming Standards pane (r7.3.8 SP2).

■ Functionality was added to Complete Compare to allow export by value of calculated properties. Previously, Complete Compare only exported by state (r7.3.10).

■ Support for Identity columns for DB2 for i was added. You can use the Null Option in the Column Editor to specify the Identity column property (r7.3.10).

■ Changes were implemented to the Display Unified Attributes option in the Advanced Options pane in the Complete Compare wizard (r7.3.11).

■ Additional information about using the Include Only Generated Objects option (Advanced Options pane in the Complete Compare wizard) with indexes was provided (r7.3.11).

Chapter 2: System Information

■ Operating System Support - Note added regarding requirement that Administrative privileges are needed when installing, updating, or removing the software.

■ r7.3.8 SP2 includes certification on Microsoft Windows 7 (32-bit only), and Microsoft Windows XP (SP3).

Chapter 3: Installation Considerations

■ Silent Install for CA ERwin Data Modeler and Crystal Reports (r7.3.6)—Overview and examples for performing a silent install of CA ERwin Data Modeler and Crystal Reports.

Chapter 5: Known Issues

■ Known issue with Meta Integration Bridges for Microsoft Office Excel (r7.3.8 SP2)—Import and Export issues when working with the Microsoft Office Excel bridges.

■ The silent install is not supported on the Windows 7 operating system.

Chapter 6: Fixed Issues

■ Issues fixed in r7.3.12 SP3

Contents 7

Contents

Chapter 1: New Features and Enhancements 11

Support for Teradata 2.6/12 ...................................................................................................................................... 12

Model Validation Enhancements for Teradata .......................................................................................................... 13

Integrated SQL Query Tool ......................................................................................................................................... 13

ODBC-Based Metadata Access ................................................................................................................................... 14

Crystal Reports 2008 Included with CA ERwin DM .................................................................................................... 14

Enhancements to Complete Compare ....................................................................................................................... 15

Features Added to Improve Complete Compare Performance with CA ERwin Model Manager ....................... 15

Advanced Options ............................................................................................................................................... 16

Type Resolution Wizard ...................................................................................................................................... 17

Change to Type Selection Filtering ...................................................................................................................... 17

Demand Loading Enhancement .......................................................................................................................... 17

Demand Loading and DB Sync............................................................................................................................. 18

Object Selection Enhancement ........................................................................................................................... 18

Range Selection Enhancement ............................................................................................................................ 18

"Explain" Button Added ...................................................................................................................................... 18

Template Editor for Forward Engineering Template Files ......................................................................................... 19

Macro Enhancements ................................................................................................................................................ 19

Macro Added (r7.3.5) .......................................................................................................................................... 20

Universal File Close Dialog ......................................................................................................................................... 21

Enhancements to Open or Save a Model in XML Format .......................................................................................... 21

Enhancements to Triggers .......................................................................................................................................... 22

Customize Model Explorer Display............................................................................................................................. 23

Metadata Integration Bridges Updated (r7.3 Initial Release) .................................................................................... 24

Import Bridges Added/Removed ........................................................................................................................ 24

Export Bridges Added/Removed ......................................................................................................................... 24

Bridges Renamed ................................................................................................................................................ 24

Metadata Integration Bridges Updated (r7.3.2) ........................................................................................................ 26



Bridges Renamed ................................................................................................................................................ 26

Metadata Integration Bridges Updated (r7.3.8 SP2) .................................................................................................. 28



Bridges Renamed ................................................................................................................................................ 29

Metadata Integration Bridges Updated (r7.3.11) ...................................................................................................... 31


8 Release Notes


Bridges Renamed ................................................................................................................................................ 31

Metadata Integration Bridges Updated (7.3.12 SP3) ................................................................................................. 32



Table of Supported Bridges ................................................................................................................................. 38

Enhancement to Rename Column Dialog (r7.3.4 SP1) ............................................................................................... 43

Allow Special Characters During Derive (r7.3.8 SP2) .................................................................................................. 43

Support for Identity Columns for DB2 for i (r7.3.10) .................................................................................................. 44

Calculated Properties in Complete Compare (r7.3.10) .............................................................................................. 44

Display Unified Attributes Option in Complete Compare (r7.3.11) ........................................................................... 44

Using the Include Only Generated Objects Option with Indexes (r7.3.11) ................................................................ 46

Database Support Update .......................................................................................................................................... 49

Databases Removed ............................................................................................................................................ 49

Databases Added ................................................................................................................................................ 49

User Interface Changes for Selected Databases ................................................................................................. 49

Operating System Support Update ............................................................................................................................ 50

Integration With Microsoft Visual Studio Team System 2008 Database Edition ....................................................... 50

Metamodel Reference Documentation ..................................................................................................................... 50

Compiled HTML Online Help ...................................................................................................................................... 51

Documentation Bookshelf .......................................................................................................................................... 51

Feature-Specific Training Videos ................................................................................................................................ 52

Chapter 2: System Information 53

Operating System Support ......................................................................................................................................... 53

System Requirements ................................................................................................................................................ 54

Supported Target Server Databases ........................................................................................................................... 54

Chapter 3: Installation Considerations 55

Installation Wizard on DVD ........................................................................................................................................ 55

Silent Install for CA ERwin DM and Crystal Reports (r7.3.6) ...................................................................................... 56

Examples ............................................................................................................................................................. 56

Important Note ................................................................................................................................................... 56

Installing VSTS Database Edition ................................................................................................................................ 57

Chapter 4: General Considerations 59

Metadata Elements Renamed .................................................................................................................................... 60

Synchronization Limitation With VSTS Database Edition and CA ERwin Data Modeler............................................. 61

Contents 9

Chapter 5: Known Issues 63

Double-Byte Character Display .................................................................................................................................. 63

Known Issue With Meta Integration Bridges for Microsoft Office Excel .................................................................... 63

Silent Install on Windows 7 ........................................................................................................................................ 63

Chapter 6: Fixed Issues 65

Issues Fixed in this Release ........................................................................................................................................ 65

Chapter 7: Documentation 81

PDF Guides ................................................................................................................................................................. 81

New Release Notes PDF ............................................................................................................................................. 82

Release Numbers ....................................................................................................................................................... 82


Chapter 1: New Features and Enhancements

This chapter of the Release Notes for CA ERwin Data Modeler (CA ERwin DM) documents new features and enhancements for r7.3.

This section contains the following topics:

Support for Teradata 2.6/12 (see page 12) Model Validation Enhancements for Teradata (see page 13) Integrated SQL Query Tool (see page 13) ODBC-Based Metadata Access (see page 14) Crystal Reports 2008 Included with CA ERwin DM (see page 14) Enhancements to Complete Compare (see page 15) Template Editor for Forward Engineering Template Files (see page 19) Macro Enhancements (see page 19) Universal File Close Dialog (see page 21) Enhancements to Open or Save a Model in XML Format (see page 21) Enhancements to Triggers (see page 22) Customize Model Explorer Display (see page 23) Metadata Integration Bridges Updated (r7.3 Initial Release) (see page 24) Metadata Integration Bridges Updated (r7.3.2) (see page 26) Metadata Integration Bridges Updated (r7.3.8 SP2) (see page 28) Metadata Integration Bridges Updated (r7.3.11) (see page 31) Metadata Integration Bridges Updated (7.3.12 SP3) (see page 32) Enhancement to Rename Column Dialog (r7.3.4 SP1) (see page 43) Allow Special Characters During Derive (r7.3.8 SP2) (see page 43) Support for Identity Columns for DB2 for i (r7.3.10) (see page 44) Calculated Properties in Complete Compare (r7.3.10) (see page 44) Display Unified Attributes Option in Complete Compare (r7.3.11) (see page 44) Using the Include Only Generated Objects Option with Indexes (r7.3.11) (see page 46) Database Support Update (see page 49) Operating System Support Update (see page 50) Integration With Microsoft Visual Studio Team System 2008 Database Edition (see page 50) Metamodel Reference Documentation (see page 50) Compiled HTML Online Help (see page 51) Documentation Bookshelf (see page 51) Feature-Specific Training Videos (see page 52)

Support for Teradata 2.6/12

12 Release Notes

Support for Teradata 2.6/12

Support has been added for data modeling with Teradata Version 2.6 and Version 12. Editors have been added for the following objects:

■ Authorization

■ Cast

■ Database

■ File

■ Function

■ Join Index

■ Index (Key Group)

■ Macro

■ Method

■ Permission

■ Profile

■ Replication Group

■ Role

■ Stored Procedure

■ Table (Entity)

■ Trigger

■ User Id

■ View

You can access new features in the property editors from the Database menu or from the Model Explorer. Reverse Engineering and Forward Engineering functionality has been updated to support the new properties. Support is not provided for any password or encryption key information in the model.

For information about the individual Teradata property editors, see the online help.

Model Validation Enhancements for Teradata


Model Validation Enhancements for Teradata

You can create a Model Validation report before you forward engineer your model. The validation process checks for corrupt objects and reports other errors associated with correct forward engineering. A full suite of check model validation routines has been added for Teradata models. In a physical model, from the Tools menu choose Forward Engineering, then Check Model. You can also click the Check Model icon on the Database toolbar.

Click F1 in the Model Check dialog for detailed information about the objects and properties that are validated during a model check.

Integrated SQL Query Tool

The Query Tool provides an easy way to execute SQL SELECT queries against the model or against a database catalog. You can execute a query against the objects and properties in the current model, the metadata defining those objects and properties, and the action log that records the changes that are made to your model during the modeling session.

You can create new queries, open existing query files, or paste text from another source (such as a *.sql file) into a query.

Sample SQL queries based on the r7.2.x Report Template Builder reports are installed with the product in the \ODBC Reports\RTB Queries folder. Click the Open Query item on the Query Tool toolbar to open a sample report. Each sample report includes a comment summarizing the purpose of the query.

For more information on working with the Query Tool, see the ODBC Reporting Guide, which is located in the Doc subdirectory of your CA ERwin Data Modeler installation. You can also open this document from a shortcut on the Start menu.

ODBC-Based Metadata Access

14 Release Notes

ODBC-Based Metadata Access

CA ERwin Data Modeler r7.3 allows you to use any third-party reporting tool that has ODBC capability to query CA ERwin Data Modeler metadata. For example, you can use queries you created in Excel, Access, Crystal Reports and Cognos and run them against the CA ERwin Data Modeler metadata. At this time only query syntax (SQL SELECT statements) is supported.

To enable this functionality, you activate the read-only ODBC-based driver provided with CA ERwin Data Modeler on the Integrations tab of the Options menu. This feature enables open access to the modeling metadata for reporting purposes.

This new feature lets you query one model at a time (the current model). Although you cannot query a model in CA ERwin Model Manager, you can query an open model from a mart, if it is the current model.

This feature is compliant with ANSI 92 specifications and therefore can be used with any standard ODBC query tool.

Crystal Reports 2008 Included with CA ERwin DM

Starting with CA ERwin DM r7.3, a licensed copy of Business Objects™ Crystal Reports® 2008 is provided with each copy of CA ERwin DM. The CA ERwin DM install wizard includes an option to install Crystal Reports 2008 edition.

With r7.3.6 or later, you can install Crystal Reports using a silent install. See the section on Silent Install under Installation Considerations below.

You can use CA ERwin DM as a data source to which you connect via Crystal Reports 2008. Two data sources are installed with CA ERwin DM:

■ ERwin - provides the option to select from among open models in the CA ERwin DM workplace

■ ERwin_current - reports on the current model in the CA ERwin DM workplace

The option to use Crystal Reports 2008 with CA ERwin DM widens the range of reporting features available to you. The CA ERwin DM metadata schemas are exposed via the data sources, enabling you to craft reports against all the CA ERwin DM metadata including the contents of the Action Log.

To help you get started, several sample reports are installed with CA ERwin DM to the \ODBC Reports folder.

Enhancements to Complete Compare



The following enhancements have been added to the Complete Compare functionality.

Features Added to Improve Complete Compare Performance with CA ERwin Model Manager

New features have been added to maximize performance when working with CA ERwin Model Manager models and Complete Compare. When two different users check out a model from CA ERwin Model Manager, change the model, and check it back in to the mart, the differences display in the Difference Reconciliation dialog (part of the Complete Compare user interface).

A conflict exists when two users check the same model out of the mart, and then change the same object or property. When each user checks their models back in to the mart, a "three-way merge" is necessary to reconcile the differences made by each user, and the unchanged objects and properties in the mart. The three-way merge of the models is sometimes slow for large models because all objects participate in the compare process.

This compare functionality has changed to reduce the scope of comparison to only objects that have changed for both the local and mart version of the models. The criteria for detecting changes include the following:

■ Objects that have been created in either the local or the mart copy.

■ Objects that have been deleted or modified in at least one of either the local or mart copy.

Two new options have been added to the Options dialog available from the Tools menu. The Model Manager tab of the Options dialog now includes the following check boxes:

Bypass Difference Reconciliation Dialog if there are no conflicts

Select this check box to skip the Difference Reconciliation dialog if no conflicts are detected between the version of the model in the mart and the local version. If no conflicts are detected, the local copy is updated from the mart version before the model is saved.

Show All Objects in Difference Reconciliation Dialog

Select this check box to turn off the options to optimize the compare process. The Difference Reconciliation dialog will display all objects including those that were not modified in the checked out model and in the mart copy of the model.

Note: This feature was first made available with the r7.2.5 SP1 release.


16 Release Notes

Advanced Options

Several options have been added to the Advanced pane of the Complete Compare wizard. They are:

Auto-Resolve Missing UDPs

In some cases, the Type Resolution box appears when Complete Compare detects missing UDPs or property differences for common UDPs. You can select to skip the Type Resolution popup box when all the differences are due to missing UDPs. When you select this check box, all missing UDPs are automatically copied to the target model. This option is not selected by default.

Display Unified Attributes

Select this check box to simplify the display of foreign-key attributes in the Resolve Differences dialog. When selected, a Unified Attributes group object is used to display all unified attributes (role-named or not) of the same unified set of attributes.

Any attributes that are aligned to the attributes under the Unified Group object appear as part of the Unified Group object, even if they are not unified attributes.

The Unified Attributes group object carries the unified name if all the attributes under it are part of the same unified set. If not, the name consists of a comma-delimited list of names of all the attributes under it.

Select Active Subject Area

Specifies that you want to select the active subject area by default in the Object Selection pane. This simplifies the subject area selection, especially in models that contain a large number of subject areas.

Ignore Code Comments

Select this option to exclude blocks of comments from the body of a trigger, before including it in the compare process. This enables Complete Compare to recognize that a trigger has not changed, if the only difference is in the comment text attached to the trigger.



Exclude Unaligned Objects/Display Only Aligned Objects

Two features on the Advanced Options pane of the Complete Compare wizard enable you to exclude unaligned model-level objects in either the left or right model. They are "Exclude Unaligned Objects in the Left Model" and "Exclude Unaligned Objects in the Right Model". In earlier versions of the product, these options were mutually exclusive - you could not select both. In CA ERwin Data Modeler r7.3 you can now select both check boxes to display only (model-level) aligned objects in the Resolve Differences dialog.

These features are useful when you work with a submodel or subject area of a larger model, and then want to compare changes against the larger model. When you select the "Exclude Unaligned Objects..." check box for the larger model, you exclude the model-level unaligned objects from the Resolve Differences dialog display. This results in a more relevant list of differences and a display that is easier to read.

Type Resolution Wizard

In earlier versions of CA ERwin Data Modeler when the type signatures of the two models were not identical, a popup window displayed, enabling you to review and accept the choices for missing types or type conflicts. In CA ERwin Data Modeler r7.3 this popup dialog has been replaced with a wizard. The wizard makes it easier to navigate and use the available options.

Change to Type Selection Filtering

In earlier versions of CA ERwin Data Modeler type selection in the Complete Compare wizard resulted in hiding the selected item from the user, not strictly removing the object from the compare process. This resulted in no performance improvement for type filtering. In CA ERwin Data Modeler r7.3 type selection has been updated so that filtering is applied strictly according to the choices made in the Type Selection pane of the Complete Compare wizard.

Demand Loading Enhancement

When working with a database in Complete Compare, selecting the Allow Demand Loading check box enables you load only the names of the top-level objects from the database catalog. When you perform an action on a partially loaded object in the Resolve Difference dialog, it is fully loaded in order to complete the compare action. In CA ERwin Data Modeler r7.3, demand loading has been optimized to improve overall performance.


18 Release Notes

Demand Loading and DB Sync

To optimize performance when doing a DB Sync, the Demand Loading option is now activated by default. In earlier versions, the check box (on the Right Model pane of the DB Sync wizard) was selected by default, but could be changed. In r7.3 you cannot clear this check box.

Object Selection Enhancement

When a model contains a large number of objects it may be difficult to locate the objects that have been selected in the Right and Left Object Selection panes of the Complete Compare wizard. For example, if you select a Subject Area set, it may be difficult to locate the selected objects in the list. A check box with the label "Hide Unselected Objects" has been added to the Object Selection panes. Select the check box to remove unselected objects from the Selected Objects display.

Note: This change also applies to the DB Sync Wizard.

Range Selection Enhancement

Range selection functionality has been added to the Object Selection panes in Complete Compare. You can now select a range of items on the same level using SHIFT+LEFTCLICK, or select individual items using CTRL+LEFTCLICK. For example, you can use SHIFT+LEFTCLICK to select a range of Entities in the "Selected Objects" list, then clear one check box next to an entity name to clear the check boxes for all the selected entities.

In earlier versions of the product, it was necessary to select or clear each check box individually.

"Explain" Button Added

To improve performance and to make compare results displayed in the Resolve Differences dialog easier to understand, a new "Explain" button has been added to the Resolve Differences dialog. When you click the Explain button, an Explanation dialog opens. For object rows, the text explains why the two objects were aligned. For property rows, the text explains why the two property values are equal. The "Explain" button replaces the "Details" button available in earlier versions of the product.

Template Editor for Forward Engineering Template Files


Template Editor for Forward Engineering Template Files

The Forward Engineer wizard now includes a link to a Template Editor, which you can use to view, modify, and create new template files for use with schema generation. The Template Editor features give you a wide range of options for controlling schema generation for your models. You can review and print database-specific features of the default template files, create a custom template file based on a default template file, or create a completely new template file. The Template Editor also includes new macros and extensive customization options.

You can access the new Template Editor from within the Forward Engineer wizard, or from an option on the Tools menu.

This feature replaces the r7.2.x Database Template option,where you could edit the *.erwin_fe_template files outside the program to modify the schema generation options. The new feature uses *.FET files which you work with using the template editor interface.

A technical document, Editing Forward Engineering Templates, is installed with the product in the \Doc folder beneath the folder where you installed CA ERwin Data Modeler. This guide provides an introduction to working with the new template editor. You can also open this PDF from a shortcut on the Start menu.

Macro Enhancements

This release introduces CA ERwin Data Modeler's Template Language (TLX), the new template/macro language for Forward Engineering templates. The macros available in earlier versions of CA ERwin Data Modeler are still accessible using the Macro Toolbox which you can open from the Domain Dictionary dialog, Model Naming Options dialog, Pre and Post Scripts dialog, Triggers dialog, and so on.

A technical document, the Template Language and Macro Reference Guide, is installed with the product in the \Doc folder beneath the folder where you installed CA ERwin Data Modeler. This guide provides extensive technical documentation for the Forward Engineering template macros. You can open help for an individual macro when you right-click the macro name in the Macros pane of the Template Editor.

Macro Enhancements

20 Release Notes

Macro Added (r7.3.5)

The following macro has been added to the list of r7.3 macros provided in the Forward Engineering Template Editor.

Macro Name:

DatabaseConnection

Description:

This macro returns information about the current database connection used by the model.

Prototype:

DatabaseConnection( Connection Parameter )

Parameter: Connection Parameter

Status: Req

Description: This identifies the type of information used by the connection.

Result:

This macro will fail in the following circumstances:

■ The required parameters are not passed in.

■ The model has no target database set.

■ The specified parameters cannot be parsed.

■ The model is not connected to a database.

Deprecation Level:

Active

Sample:

[ “Connected to database as user “

DatabaseConnection( “User” ) ]

Result:

Connected to database as user User1

Universal File Close Dialog


Universal File Close Dialog

The different Close dialogs in earlier releases have been replaced with a "universal" Close dialog to ensure a standardized look and feel throughout the product. When you finish working on a model either locally or from within CA ERwin Model Manager, you can close the current model and continue working on another, or you can close the model and exit. The Close Model dialog also shows the status of the file, such as if it was opened from the server, its lock status, and whether there are unsaved changes. The five model close scenarios are:

■ File/Close from the CA ERwin Data Modeler application menu

■ Service/Close from the CA ERwin Model Manager menu

■ Close model when closing the diagram window

■ File/Exit or Close models when exiting the CA ERwin Data Modeler application

■ Close button in the Complete Compare wizard

Note: You must be connected to CA ERwin Model Manager to save a model to the mart.

Enhancements to Open or Save a Model in XML Format

Changes have been implemented to let you save an XML file in one dialog. In earlier versions of the software, you needed to go through several dialogs to choose the proper XML format.

When you select Save As from the File menu, you can select one of the following XML format options as the file type from the Save as type drop-down menu:

XML Standard Files (*.XML)

Standard XML format does not expand macros or names. This file is suitable for importing back into CA ERwin Data Modeler.

XML Standard with Min Info Files (*.XML)

Only saves the minimum amount of information needed by CA ERwin Data Modeler to reopen the model. Properties that are derived from other properties or that are read-only are not saved. You can choose to not use this option and still use the standard XML format.

XML Repository Format Files (*.XML)

The Repository format expands names, macros, and physical names. Derived properties are exported. A file saved in this format cannot be opened with CA ERwin Data Modeler.

Enhancements to Triggers

22 Release Notes

Enhancements to Triggers

Changes have been implemented to allow you to create model objects for ERwin-generated triggers. In earlier versions of the software, triggers did not exist as objects in the model, they were created during the forward-engineering process but not recognized during reverse-engineering.

In CA ERwin DM r7.3, several features have been implemented to allow you to treat triggers as model objects. These enhancements allow you include the triggers in alter scripts, include triggers in Complete Compare scenarios, and associate triggers with model templates.

The RI Defaults tab on the Model Properties dialog now includes a check box with the label "Automatically Create RI Triggers". When you select this check box, you are prompted with an option to create RI triggers for existing relationships. The option is then enabled for new objects. If you click No to the prompt, RI Triggers are created only for new relationships. This check box is not selected by default - you must select it to activate this new feature.

In the Forward Engineer wizard, on the Options tab for the Triggers object, the wording of the triggers options has been updated to reflect the new distinction between ERwin-generated and User-Defined triggers. When you select to automatically generate RI triggers, a check box is provided with the label "Automatically Generate Missing RI Triggers".

The Reverse Engineer - Set Options dialog now includes a check box with the label "Include Generated Triggers". You select this check box to include RI Triggers in the reverse engineer process.

Customize Model Explorer Display


Customize Model Explorer Display

Two template files are provided with CA ERwin Data Modeler that let you customize the display of object names in the Model Explorer. By using macros in the template file, you can override the default display of selected object names.

The file Logical Names.ont includes display options for the logical model. The file Physical Names.ont includes display options for the physical model. The files are installed to the \Documents and Settings\<user>\Application Data\CA\ERwin Data Modeler\7.3\Templates folder.

Comments and a sample macro are provided in the file to customize the display of the parent/child relationship phrase in the Model Explorer. By default, the display is formatted to include the elements <parent name> <relationship name> <child name>. You can modify the macro to exclude one of the elements, for example if you wanted to exclude the parent name in the display. You can add or edit entries in this file to customize the display in Model Explorer. These entries are optional; if there is no macro specified for an object type, the Model Explorer displays the object's name.

Note: If earlier versions of CA ERwin Data Modeler these files were named ModelExplorer logical display names.tmpl and ModelExplorer physical display names.tmpl respectively.

Metadata Integration Bridges Updated (r7.3 Initial Release)

24 Release Notes


The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r7.3 (Initial Release). You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu.

The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide. This PDF guide is available from the Start menu, or in the \Doc folder where you installed the product.

Import Bridges Added/Removed

Support has been added for the following MIMB import bridges:

■ Cognos ReportNet QueryStudio (File)

■ Oracle Business Intelligence Answers

■ Oracle Business Intelligence Enterprise Edition

■ Oracle Business Intelligence Server

■ Oracle Warehouse Builder

■ Sypherlink Harvester 5.x

Support has been dropped for the following MIMB import bridges:

■ Ab Initio SA XML Exporter

■ Microsoft SQL Server Analysis Services 7.0 to 9.0 (via DSO)

Export Bridges Added/Removed

Support has been added for the following MIMB export bridges:

■ CA Repository for Distributed Systems

■ CA Repository for z/OS

Support has been dropped for the following MIMB export bridges:

■ ASG Rochade (via CWM XMI)

■ Sybase PowerDesigner OOM 9.x to 15.x (via UML XMI)

Bridges Renamed

■ IBM Webshere DataStage to IBM InfoSphere DataStage

■ IBM DB2 Data Warehouse Edition/OLAP Acceleration (Cube Views) to IBM InfoSphere Warehouse/Cubing Services for OLAP



■ IBM DB2 Data Warehouse Edition/Rational Data Architect to IBM InfoSphere Warehouse/Rational Data Architect

■ IBM Rational Rose 98(i) to 2000 to IBM Rational Rose 6.0 (98i) to 6.5 (2000)

■ IBM Rational Rose 2000e to 2003 to IBM Rational Rose 7.x (2000e and newer)

■ Oracle Data Integrator - Beta to Oracle Data Integrator

Metadata Integration Bridges Updated (r7.3.2)

26 Release Notes


The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r7.3.2 (Patch Release). You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu.

The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide (r7.3.2 Edition). This PDF guide is available from the Start menu, or in the \Doc folder where you installed the product.



■ Microsoft Office Excel Advanced


■ Adaptive Repository & Foundation (via MIR XMI)

■ Adaptive Repository & Foundation (via CWM XMI)

■ Adaptive Repository & Foundation (via UML XMI)



■ Microsoft Office Excel Advanced

■ Microsoft SQL Server Integration Services (Project)


■ Adaptive Repository & Foundation (via MIR XMI)

■ Adaptive Repository & Foundation (via CWM XMI)

■ Adaptive Repository & Foundation (via UML XMI)

Bridges Renamed

■ Business Objects Crystal Reports XI (File) to SAP BusinessObjects Crystal Reports XI (File)

■ Business Objects Data Integrator (via CWM XMI) to SAP BusinessObjects Data Integrator (via CWM XMI)

■ Business Objects Designer (File) to SAP BusinessObjects Designer (File)



■ Business Objects Desktop Intelligence (File) to SAP BusinessObjects Desktop Intelligence (File)

■ Business Objects Metadata Manager (via MIR XMI) to SAP Business Objects Metadata Manager (via MIR XMI)

■ CA Gen 4.1a to 7.5 to CA Gen 4.1a to r7.6

■ Cognos Series 7 Impromptu to IBM Cognos Series 7 Impromptu

■ Cognos ReportNet Framework Manager to IBM Cognos ReportNet Framework Manager

■ Cognos 8 Framework Manager Services to IBM Cognos 8 Framework Manager Services

■ Cognos ReportNet QueryStudio (File) to IBM Cognos ReportNet QueryStudio (File)

■ Cognos ReportNet ReportStudio (File) to IBM Cognos ReportNet ReportStudio (File)

■ IBM Rational Data Architect (RDA) to IBM InfoSphere Data Architect

■ IBM InfoSphere Warehouse/Rational Data Architect to IBM InfoSphere Warehouse/InfoSphere Data Architect

■ Microsoft SQL Server Integration Services to Microsoft SQL Server Integration Services (File)

■ Telelogic Tau (via UML XMI) to IBM Telelogic Tau (via UML XMI)

■ Telelogic (Popkin) System Architect 7.1 to 11x (File) to IBM Telelogic (Popkin) System Architect 7.1 to 11x (File)

■ Telelogic (Popkin) System Architect 10.4 to 11.x (Encyclopedia) to IBM Telelogic (Popkin) System Architect 10.4 to 11.x (Encyclopedia)

Metadata Integration Bridges Updated (r7.3.8 SP2)

28 Release Notes


The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r7.3.8 SP2. You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu.

The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide (r7.3.8 SP2 Edition). This PDF guide is available from the Start menu, or in the \Doc folder where you installed the product.



■ Borland Together (via UML 2.x XMI)

■ Informatica Developer - Beta bridge

■ IBM Rational Software Architect (RSA) (via UML 2.x XMI)

■ Microsoft SQL Server Analysis Services (via DSV File)

■ Microsoft SQL Server Integration Services (via DSV File)

■ OMG UML 2.x XMI 2.x

■ SAP BusinessObjects Data Integrator

■ Sparx Enterprise Architect (EA) (via UML 2.x XMI)


■ Microsoft Office Excel (advanced)

■ MicroStrategy 7.0 to 8.1

■ SAP BusinessObjects Crystal Reports 8.5 to 9.5 (File)

■ SAP BusinessObjects Data Integrator (via CWM XMI)

■ Sun Netbeans XMI Writer

■ Sypherlink Harvester

■ Sypherlink Harvester 5.x



■ Database data definition language (DDL)

■ Informatica Developer - Beta bridge

■ Microsoft SQL Server Integration Services (via DSV File)





■ Embarcadero ER/Studio (via ERX)

■ Microsoft Office Access

■ Microsoft Office Excel (advanced)


■ RedHat (MetaMatrix) Enterprise Designer (via MIR XMI)

■ SAP BusinessObjects Data Integrator (via CWM XMI)

■ SchemaLogic SchemaServer (via MIR XMI)

■ Sun Netbeans XMI Writer

■ Unisys ClearPath (via MIR XMI)

Bridges Renamed

■ Borland Together (via UML XMI) to Borland Together (via UML 1.x XMI) (Export)

■ CA Component Modeler 4.x (via UML XMI) to CA Component Modeler 4.x (via UML 1.x XMI) (Export)

■ Embarcadero Describe (via UML XMI) to Embarcadero Describe (via UML 1.x XMI) (Export)

■ Embarcadero EA/Studio (via DM1) to Embarcadero ER/Studio Business Architect (via DM1) (Import/Export)

■ Embarcadero ER/Studio to Embarcadero ER/Studio Data Architect (Import/Export)

■ Gentleware Poseidon (via UML XMI) to Gentleware Poseidon (via UML 1.x XMI) (Export)

■ IBM Cognos 8 Framework Manager Services to IBM Cognos 8 BI Reporting - Framework Manager (Import)

■ IBM Cognos 8 Framework Manager Services to IBM Cognos 8 BI Reporting - Framework Manager (Import/Export)

■ IBM Cognos ReportNet Framework Manager to IBM Cognos 8 BI Reporting - Framework Manager for ReportNet (Import)

■ IBM Cognos ReportNet Framework Manager to IBM Cognos 8 BI Reporting - Framework Manager for ReportNet (Import/Export)

■ IBM Cognos ReportNet QueryStudio (File) to IBM Cognos 8 BI Reporting - QueryStudio (Import)

■ IBM Cognos ReportNet ReportStudio (File) to IBM Cognos 8 BI Reporting - ReportStudio (Import)


30 Release Notes

■ IBM Telelogic System Architect 7.1 to 11.x (File) to IBM Rational System Architect 7.1 to 11.x (File) (Import/Export)

■ IBM Telelogic System Architect 10.4 to 11.x (Encyclopedia) to IBM Rational System Architect 10.4 to 11.x (Encyclopedia) (Import/Export)

■ IBM Telelogic Tau (via UML XMI) to IBM Telelogic Tau (via UML 1.x XMI) (Import/Export)

■ Microsoft SQL Server Analysis Services 9.0 (File) to Microsoft SQL Server Analysis Services 2005 to 2008 (File) (Import)

■ Microsoft SQL Server Analysis Services 9.0 (via DSV) to Microsoft SQL Server Analysis Services (via DSV File) (Export)

■ NoMagic MagicDraw (via UML XMI) to NoMagic MagicDraw (via UML 1.x XMI) (Import/Export)

■ Sparx Enterprise Architect (EA) (via UML XMI) to Sparx Enterprise Architect (EA) (via UML 1.x XMI) (Import/Export)

■ Sybase PowerDesigner CDM 8.0 to 12.0 to Sybase PowerDesigner CDM 8.0 to 15.x (Export)

■ Sybase PowerDesigner OOM 9.x to 15.x (via UML XMI) to Sybase PowerDesigner OOM 9.x to 15.x (via UML 1.x XMI) (Import/Export)

■ Tigris ArgoUML (via UML XMI) to Tigris ArgoUML (via UML 1.x XMI) (Import/Export)




The list of supported Metadata Integration Bridges from Meta Integration Technology, Inc. (MIMB) was updated for r7.3.11. You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu.

The full list of supported import and export bridges is documented in Appendix B of the CA ERwin Data Modeler Implementation Guide (r7.3.11 Edition). This guide is available from the Start menu, the bookshelf, or in the \Doc folder where you installed the product.



■ IBM InfoSphere Discovery - Beta bridge

■ IBM InfoSphere Discovery (via CWM XMI)

■ Microsoft Office Excel (multi-model)



■ Oracle Business Intelligence Enterprise Edition



■ Meta Integration Business Rules

■ Meta Integration Repository (MIR) XMI Business Glossary


■ Composite Software Composite Studio (via MIR XMI)

■ Meta Integration Repository (MIR) Transformations to Views XMI file

Bridges Renamed

■ Database data definition language (DDL) to Database Data Definition Language (DDL) (Export)

■ Grandite Silverrun-RDM 2.4.4 to 2.7.2 to Grandite Silverrun-RDM 2.4.4 to 2.8.4 (Import)

■ IBM Cognos 8 BI Reporting - Framework Manager to IBM Cognos BI Reporting - Framework Manager (Import/Export)

Metadata Integration Bridges Updated (7.3.12 SP3)

32 Release Notes

■ IBM Cognos 8 BI Reporting - Framework Manager for ReportNet to IBM Cognos BI Reporting - Framework Manager for ReportNet (Import/Export)

■ IBM Cognos 8 BI Reporting - QueryStudio to IBM Cognos BI Reporting - QueryStudio (Import)

■ IBM Cognos 8 BI Reporting - ReportStudio to IBM Cognos BI Reporting - ReportStudio (Import)


CA ERwin Data Modeler has been updated to support Meta Integration® Model Bridge (MIMB) version 7.04 from Meta Integration® Technology, Inc. You can access the bridges when you click Import, From External Format or Export, To External Format on the File menu. This topic lists the import and export bridges that are updated in CA ERwin Data Modeler release 7.3.12 SP3.





■ CA Component Modeler 3.52 (ParadigmPlus)

■ CA Component Modeler 4.x (via UML 1.x XMI)

■ CA COOL:BusinessTeam (GroundWorks) 2.2.1

■ CA COOL:DBA (Terrain for DB2) 5.3.2

■ CA COOL:Xtras Mapper (TerrainMap for DB2)

■ CA ERwin 3.x (ERX)

■ CA ERwin 4.x Data Modeler

■ CA Gen

■ CA Repository for Distributed Systems

■ CA Repository for z/OS

■ COBOL Copybook Flat Files

■ Database (via JDBC)

■ Database (via ODBC)

■ Embarcadero Describe (via UML 1.x XMI)

■ Embarcadero ER/Studio Business Architect (via DM1)

■ Embarcadero ER/Studio Data Architect

■ Embarcadero ER/Studio Repository

■ EMC ProActivity 3.x & 4.0

■ Gentleware Poseidon (via UML 1.x XMI)

■ Grandite Silverrun-RDM 2.4.4 to 2.8.6

■ IBM Cognos BI Reporting - Content Manager Packages

■ IBM Cognos BI Reporting - Content Manager QueryStudio

■ IBM Cognos BI Reporting - Content Manager ReportStudio

■ IBM Cognos BI Reporting - Framework Manager

■ IBM Cognos BI Reporting - PowerPlay Transformer

■ IBM DB2 Cube Views

■ IBM DB2 Data Server (via JDBC)

■ IBM InfoSphere Data Architect (IDA)

■ IBM InfoSphere Federation Server (via JDBC)

■ IBM Lotus Notes (via JDBC-ODBC)


34 Release Notes

■ IBM Rational System Architect (SA) 10.4 to 11.x (Encyclopedia)

■ IBM Rational System Architect (SA) 7.1 to 11.x (File)

■ Informatica PowerCenter (Repository)

■ Micro Focus (Merant) AppMaster Builder

■ Microsoft Office Access (via JDBC-ODBC)

■ Microsoft Office Excel (Java Alpha)

■ Microsoft SQL Server Analysis Services 2005 to 2008 (Repository)

■ Microsoft SQL Server Analysis Services 7.0 to 2000 (Repository)

■ Microsoft SQL Server Analysis Services 7.0 to 2000 (via ODBO)

■ Microsoft SQL Server Database (via JDBC)

■ Microsoft SQL Server Reporting Services (Repository)

■ MicroStrategy MDX Adapter (via ODBO)

■ Oracle Data Integrator (ODI) 11g - Beta bridge

■ Oracle Database (via JDBC)

■ Oracle Warehouse Builder (OWB)

■ Oracle Warehouse Builder (OWB) (via CWM XMI)

■ SAP BusinessObjects Crystal Reports XI (Repository)

■ SAP BusinessObjects Data Integrator (BODI)

■ SAP BusinessObjects Designer (Repository)

■ SAP BusinessObjects Desktop Intelligence (Repository)

■ SAP BusinessObjects Web Intelligence XI

■ SAP ERP Central Component (ECC) - Beta bridge

■ SAP NetWeaver Business Warehouse (BW) (via ODBO)

■ SAP NetWeaver Business Warehouse (BW) (via XML)

■ SAP NetWeaver Master Data Management (MDM) - Beta bridge

■ SAS OLAP Server (via ODBO)

■ Sybase Database (via JDBC)

■ Sybase PowerDesigner CDM 7.5 to 16.x

■ Sybase PowerDesigner PDM 7.5 to 16.x

■ Syncsort DMExpress

■ Teradata Database (via JDBC)



Support has been removed for the following MIMB import bridges:

■ IBM Cognos BI Reporting - PowerPlay Transformer - Beta bridge

■ IBM InfoSphere Data Architect

■ IBM InfoSphere Discovery - Beta bridge

■ IBM InfoSphere Warehouse - Cubing Services for OLAP

■ IBM Rational System Architect 10.4 to 11.x (Encyclopedia)

■ IBM Rational System Architect 7.1 to 11.x (File)

■ Meta Integration Repository (MIR) XMI file

■ Meta Integration Repository (MIR) XMI multimodel content

■ Microsoft SQL Server Integration Services (File)


■ Oracle Business Intelligence Answers

■ Oracle Business Intelligence Server

■ Oracle Data Integrator 11g


■ Oracle Warehouse Builder (via CWM XMI)


■ SAP NetWeaver Business Warehouse (BW) - Beta bridge

■ SAP NetWeaver Business Warehouse (BW) (via XML) - Beta bridge

■ SAP NetWeaver Master Data Management (MDM)

■ SAS Data Integration Studio (via MIR XMI)

■ SAS Information Map Studio (via MIR XMI)

■ SAS Management Console (via MIR XMI)

■ SAS Metadata Management (via MIR XMI)

■ Sybase PowerDesigner CDM 7.5 to 15.x

■ Sybase PowerDesigner PDM 7.5 to 15.x


36 Release Notes



■ CA Gen

■ Composite (Beta)

■ IBM DB2 Cube Views

■ IBM InfoSphere Data Architect (IDA)

■ IBM Rational System Architect (SA) 10.4 to 11.x (Encyclopedia)

■ IBM Rational System Architect (SA) 7.1 to 11.x (File)

■ Meta Integration Repository (MIR) Application Server

■ Microsoft Office Excel (Java Alpha)

■ Microsoft SQL Server Analysis Services (Repository)

■ Oracle Data Integrator (ODI) 11g - Beta bridge

■ Oracle Warehouse Builder (OWB)

■ Oracle Warehouse Builder (OWB) (via CWM XMI)

■ SAP BusinessObjects Data Integrator (BODI)

■ SAP NetWeaver Master Data Management (MDM) - Beta bridge



Support has been removed for the following MIMB export bridges:

■ Adaptive Metadata Manager (via MIR XMI)

■ CA ERwin 3.x (ERX)

■ CA Gen 4.1a to 7.6

■ HP Knightsbridge CDMA

■ IBM InfoSphere Data Architect

■ IBM InfoSphere DataStage

■ IBM InfoSphere Warehouse - Cubing Services for OLAP

■ IBM Rational System Architect 10.4 to 11.x (Encyclopedia)

■ IBM Rational System Architect 7.1 to 11.x (File)

■ Informatica Metadata Manager

■ Informatica Metadata Manager (via MIR XMI)

■ Meta Integration Business Rules

■ Meta Integration Repository (MIR) Profiling (XML)

■ Meta Integration Repository (MIR) XMI Business Glossary

■ Meta Integration Repository (MIR) XMI file

■ Meta Integration Repository (MIR) XMI multimodel content

■ Microsoft Office Visio Database (via ERX)


■ Oracle Warehouse Builder (via CWM XMI)


■ SAP BusinessObjects Metadata Management (BOMM) (via MIR XMI)

■ SAP NetWeaver Master Data Management (MDM)

■ SAS Management Console (via MIR XMI)

■ Sybase PowerDesigner 7.0 (via ERX)


38 Release Notes

Table of Supported Bridges

The following table contains a complete, up-to-date list of Meta Integration Technology, Inc. (7.04) bridges that are currently available in CA ERwin Data Modeler (as of r7.3.12 SP3). The information contained in the table replaces the information contained in the section Supported Metadata Integration Bridges in the Implementation Guide.

Notes:

■ Read the information displayed in the tip text area on the Source and Destination pages of the Import from External Format and Export to External Format dialogs carefully. Complete any requirements as appropriate before proceeding.

■ IBM Rational System Architect 7.1 to 11.x (File) and IBM Rational System Architect 10.4 to 11.x (Encyclopedia) must be installed on your local computer before you use these import and export bridges.

Application Mode

Adaptive Metadata Manager (via CWM XMI) Import/Export

Altova XMLSpy Export

Borland Together (via UML 1.x XMI) Import/Export

Borland Together (via UML 2.x XMI) Import

CA Component Modeler 3.52 (ParadigmPlus) Import/Export

CA Component Modeler 4.x (via UML 1.x XMI) Import/Export

CA COOL:Biz 5.1 Import

CA COOL:BusinessTeam (GroundWorks) 2.2.1 Import

CA COOL:DBA (Terrain for DB2) 5.3.2 Import

CA COOL:Enterprise (ADW) 2.7 Import

CA COOL:Xtras Mapper (TerrainMap for DB2) Import

CA ERwin 3.x (ERX) Import

CA ERwin 4.x Data Modeler Import

CA ERwin Web Portal Export

CA Gen Import/Export

CA Repository for Distributed Systems Import/Export

CA Repository for z/OS Import/Export

COBOL Copybook Flat Files Import

Composite (Beta) Export



Application Mode

Database (via JDBC) Import

Database (via ODBC) Import

Database Data Definition Language (DDL) Export

Embarcadero Describe (via UML 1.x XMI) Import/Export

Embarcadero ER/Studio Business Architect (via DM1) Import/Export

Embarcadero ER/Studio Data Architect Import/Export

Embarcadero ER/Studio Repository Import

EMC ProActivity 3.x & 4.0 Import

Gentleware Poseidon (via UML 1.x XMI) Import/Export

Grandite Silverrun-RDM 2.4.4 to 2.8.6 Import

IBM Cognos BI Reporting - Content Manager Packages Import

IBM Cognos BI Reporting - Content Manager QueryStudio Import

IBM Cognos BI Reporting - Content Manager ReportStudio Import

IBM Cognos BI Reporting - Framework Manager Import/Export

IBM Cognos BI Reporting - Framework Manager for ReportNet Import/Export

IBM Cognos BI Reporting - PowerPlay Transformer Import

IBM Cognos BI Reporting - QueryStudio Import

IBM Cognos BI Reporting - ReportStudio Import

IBM Cognos Series 7 Impromptu Import

IBM DB2 Cube Views Import/Export

IBM DB2 Data Server (via JDBC) Import

IBM DB2 Warehouse Manager (via CWM XMI) Import/Export

IBM InfoSphere Data Architect (IDA) Import/Export

IBM InfoSphere DataStage Import

IBM InfoSphere Discovery (via CWM XMI) Import

IBM InfoSphere Federation Server (via JDBC) Import

IBM InfoSphere Warehouse - InfoSphere Data Architect Import/Export

IBM Lotus Notes (via JDBC-ODBC) Import

IBM Rational Rose 4.0 Import/Export

IBM Rational Rose 6.0(98i) to 6.5(2000) Import/Export


40 Release Notes

Application Mode

IBM Rational Rose 7.x (2000e and newer) Import/Export

IBM Rational Rose XDE Developer (via Rose MDL) Export

IBM Rational Software Architect (RSA) (via Rose MDL) Export

IBM Rational Software Architect (RSA) (via UML 2.x XMI) Import

IBM Rational Software Modeler (RSM) (via Rose MDL) Export

IBM Rational System Architect (SA) 10.4 to 11.x (Encyclopedia) Import/Export

IBM Rational System Architect (SA) 7.1 to 11.x (File) Import/Export

IBM Telelogic Tau (via UML 1.x XMI) Import/Export

Informatica Data Analyzer Export

Informatica Developer Import/Export

Informatica PowerCenter Export

Informatica PowerCenter (File) Import

Informatica PowerCenter (Repository) Import

IRI CoSORT RowGen Data Definition File Export

IRI CoSORT SortCL Data Definition File Export

Kalido DIW Import

Meta Integration Repository (MIR) Application Server Export

Micro Focus (Merant) AppMaster Builder Import

Microsoft Office Access (via JDBC-ODBC) Import

Microsoft Office Excel Import/Export

Microsoft Office Excel (Java Alpha) Import/Export

Microsoft Office Visio Database (via ERX) Import

Microsoft Office Visio UML (via UML 1.x XMI) Import

Microsoft SQL Server Analysis Services (Repository) Export

Microsoft SQL Server Analysis Services (via DSV File) Import/Export

Microsoft SQL Server Analysis Services 2005 to 2008 (File) Import

Microsoft SQL Server Analysis Services 2005 to 2008 (Repository) Import

Microsoft SQL Server Analysis Services 7.0 to 2000 (Repository) Import

Microsoft SQL Server Analysis Services 7.0 to 2000 (via ODBO) Import

Microsoft SQL Server Data Source View Import/Export



Application Mode

Microsoft SQL Server Database (via JDBC) Import

Microsoft SQL Server Integration Services (File) Export

Microsoft SQL Server Integration Services (via DSV File) Import/Export

Microsoft SQL Server Reporting Services (File) Import

Microsoft SQL Server Reporting Services (Repository) Import

Microsoft SQL Server Repository 2.1b (via XIF) Import/Export

Microsoft SQL Server Repository 3.x (via MDC) Import/Export

Microsoft SQL Server XML Data Reduced (XDR) Schema Import

Microsoft Visual Studio / Modeler 2.0 (via MDL) Import/Export

MicroStrategy MDX Adapter (via ODBO) Import

NoMagic MagicDraw (via UML 1.x XMI) Import/Export

OMG CWM 1.x XMI 1.x Import/Export

OMG CWM Pre-1.0 XMI 1.1 Import/Export

OMG UML 1.x XMI 1.x Import/Export

OMG UML 2.x XMI 2.x Import

Open Text eDOCS Data Integration (Hummingbird) Genio Import/Export

Oracle Data Integrator (ODI) 11g - Beta bridge Import/Export

Oracle Database (via JDBC) Import

Oracle Designer Import/Export

Oracle Hyperion Application Builder (via CWM XMI) Import/Export

Oracle Hyperion Essbase - Beta bridge Import

Oracle Hyperion Essbase Integration Services (EIS) Import/Export

Oracle Warehouse Builder (OWB) Import/Export

Oracle Warehouse Builder (OWB) (via CWM XMI) Import/Export

SAP BusinessObjects Crystal Reports XI (File) Import

SAP BusinessObjects Crystal Reports XI (Repository) Import

SAP BusinessObjects Data Integrator (BODI) Import/Export

SAP BusinessObjects Data Integrator (BODI) Import

SAP BusinessObjects Designer (File) Import/Export

SAP BusinessObjects Designer (Repository) Import


42 Release Notes

Application Mode

SAP BusinessObjects Desktop Intelligence (File) Import

SAP BusinessObjects Desktop Intelligence (Repository) Import

SAP BusinessObjects Web Intelligence XI Import

SAP ERP Central Component (ECC) - Beta bridge Import

SAP NetWeaver Business Warehouse (BW) (via ODBO) Import

SAP NetWeaver Business Warehouse (BW) (via XML) Import

SAP NetWeaver Master Data Management (MDM) - Beta bridge Import/Export

SAS Data Integration Studio (via CWM XMI) Import/Export

SAS OLAP Server (via ODBO) Import

Select SE Import

Sparx Enterprise Architect (EA) (via UML 1.x XMI) Import/Export

Sparx Enterprise Architect (EA) (via UML 2.x XMI) Import

Sybase Database (via JDBC) Import

Sybase PowerDesigner CDM 6.x Import

Sybase PowerDesigner CDM 7.5 to 16.x Import

Sybase PowerDesigner CDM 8.0 to 15.x Export

Sybase PowerDesigner OOM 9.x to 15.x (via UML 1.x XMI) Import/Export

Sybase PowerDesigner OOM 9.x to 15.x (via UML 2.x XMI) Import

Sybase PowerDesigner PDM 6.1.x Import

Sybase PowerDesigner PDM 7.5 to 16.x Import

Sybase PowerDesigner PDM 8.x to 15.x Export

Sybase PowerDesigner XSM 10.x to 15.x Export

Syncsort DMExpress Import/Export

Talend Data Integration - Beta bridge Import/Export

Teradata Database (via JDBC) Import

Tigris ArgoUML (via UML 1.x XMI) Import/Export

Visible IE:Advantage 6.1 Import

W3C XML DTD 1.0 Import

W3C XML Schema 1.0 (XSD) Import/Export

Enhancement to Rename Column Dialog (r7.3.4 SP1)


Notes:

■ For information about how to use the metadata integration wizards, see the CA ERwin Data Modeler online help.

■ For Oracle Data Integrator 11g, the new Java API based architecture is supported.

■ For Oracle Warehouse Builder 11.2, the new API architecture for 11.2 (different from 11.1) is supported.

Enhancement to Rename Column Dialog (r7.3.4 SP1)

In a logical/physical model, if you create column names using domains, you may want to maintain a different name on the logical side (attribute) and physical side (column).

A check box has been added to the Rename Column dialog that enables you to break or maintain name inheritance between attribute and column names.

For example, in a physical model, you can drag and drop a domain into a table to create a new column. By default, a corresponding attribute is created on the logical side of the model, using the same name. To maintain a unique column name, click Rename in the Column Editor to open the Rename Column dialog, then clear the check box for "Use logical/physical name inheritance". This allows you to alter the physical name without affecting the logical name.

Note: An asterisk next to the property name indicates that the value is derived from inheritance. If you do not see the asterisk, the inheritance override check box also is not displayed, indicating that inheritance is not in effect.

This option appears in the r7.3.4 (SP1) release and later.

Allow Special Characters During Derive (r7.3.8 SP2)

An enhancement has been made to the Derive Model Wizard, Naming Standards Tab. The "Allow Special DBMS Characters" check box has been added. This feature only applies when deriving a physical-only model from a logical-only model. When you select the check box you can allow special characters in a physical object name when it is derived from the logical model. This feature enables you to override the restriction on invalid or special characters in physical model object names. See the SQL Reference Documentation for your target server for more information about special characters.

Previously, this feature only appeared on the Model Naming Options dialog, Physical tab.

Support for Identity Columns for DB2 for i (r7.3.10)

44 Release Notes

Support for Identity Columns for DB2 for i (r7.3.10)

Support for Identity columns for DB2 for i was added for r7.3.10. You can use the Null Option in the Column Editor to specify the Identity column property.

Calculated Properties in Complete Compare (r7.3.10)

Functionality was added to Complete Compare to allow export by value of calculated properties. Previously, Complete Compare only exported by state.

Calculated properties do not exist in the model. They are calculated based on other properties in the model. Currently when calculated properties are exported, CA ERwin Data Modeler forces the recalculation of the property in the target model. Since the domain or foreign key from which the target property value was calculated remains unchanged, the export looked like it failed. Now Complete Compare allows calculated properties to be exported by value; when a calculated property is exported, a menu displays that lets you choose whether to export the state (existing functionality), or export the value.

Note: Once the value of the property is exported, the property breaks its link with the domain or FK level properties from which it inherited its value.

Display Unified Attributes Option in Complete Compare (r7.3.11)

The Display Unified Attributes advanced option in the Complete Compare wizard was changed in r7.3.11.

Display Unified Attributes Option in Complete Compare (r7.3.11)


When this option is selected, all lead and non-lead unified foreign key (FK) columns and the corresponding key group members are included in Complete Compare. When this option is not selected, then Complete Compare only includes the lead unified FK column and corresponding key group members. The non-lead unified FK columns and corresponding key group members are not included in the Complete Compare.

Example: Two models being compared in the Complete Compare process

In the previous example, the columns are not unified in the left model under entity E/3. In the right model the columns are unified under entity E/3.

The following example shows the Complete Compare results screen if you did not select the Display Unified Attributes option. There will not be any effect of this selection in the left model as nothing is unified. In the right model, only the unified lead FK column is included in the compare. Here you will see the differences in the columns and key group members of FK and PK; these are valid differences.

Using the Include Only Generated Objects Option with Indexes (r7.3.11)

46 Release Notes

The following example shows the Complete Compare results screen if you selected the Display Unified Attributes option. Again, there is no difference on the left model as nothing is unified. In the right model, now all of the unified FK columns (lead and non-lead) and corresponding key group members are included in the compare. The unified FK columns show some property level differences, and no differences in the key group members.


Additional information about the Complete Compare advanced option Include Only Generated Objects was provided for r7.3.11.

The Complete Compare advanced option Include Only Generated Objects works for indexes only when you use a Database Level Compare. It does not apply for the Logical, Physical, and Logical Physical Level Compare.

The following table illustrates the conditions when indexes are filtered in Complete Compare for Database Level Compare with this advanced option selected:

Index Generate Generate As Constraint Filtered in Complete Compare

PK Not selected Not selected Yes

FK Not selected Any value Yes



AK Not selected Not selected Yes

IE Not selected Any value Yes

Note: In this table, Any value means that the Generate As Constraint option can be selected or not selected.

The following table illustrates the conditions when indexes are not filtered in Complete Compare for Database Level Compare with this advanced option selected:

Index Generate Generate As Constraint Filtered in Complete Compare

PK Any value Selected No

PK Selected Any value No

FK Selected Any value No

AK Any value Selected No

AK Selected Any value No

IE Selected Any value No

Note: In this table, Any value means that the Generate As Constraint option can be selected or not selected.

The Indexes are compared in Complete Compare even though the Generate or Generate As Constraint options (or both) are not selected in the Index Editor because you are using the Physical Level Compare. Using the Include Only Generated Objects option has no effect on Indexes except when you use the Database Level Compare.

The following illustrations demonstrate this behavior. The FK indexes DONOTGENERATE and XIF1SCN_API_AUD_CNFM_SHMT with the Generate check box not selected appear in the Physical Level Compare and are hidden in the Database Level Compare.

Example: Physical Level Compare


48 Release Notes

Example: Database Level Compare

Database Support Update


Database Support Update

The following information describes updates to database support for CA ERwin Data Modeler.

Databases Removed

Support has been dropped for the following target server databases in CA ERwin Data Modeler:

■ Ingres 2.5

■ Oracle 8i

■ Progress 8.x

■ SQL Server 7.0

Databases Added

Support has been added for the following target server databases in CA ERwin Data Modeler:

■ Oracle 11x

■ Teradata 2.6/12 (see Support for Teradata 2.6/12 (see page 12) for more information)

■ DB2/zOS 9 (certification)

■ SQL Server 2008 (certification)

■ DB2 iSeries 6 (certification, r7.3.4 SP1 and later)

User Interface Changes for Selected Databases

Changes have been made to the user interface to support new modeling features for selected databases. Changes include:

■ The SQL tab on the View editor for SQL Server, Oracle, and Teradata has been changed. Two tabs are now used to provide the features. A SQL tab provides read-only information about the DDL statement that is used during forward engineering. A User-Defined SQL tab provides a box for editing a user-provided DDL statement. The box is blank by default.

■ An enhancement has been added for MySQL. The AUTO_INCREMENT feature is now supported. When you select a numeric datatype such as Integer in the Column editor (MySQL tab), the Identity option becomes available. When you select this option and perform forward engineering, it generates the AUTO_INCREMENT syntax.

Operating System Support Update

50 Release Notes

Note: There can be only one AUTO_INCREMENT column per table.

■ The Privilege object was replaced by the Permission object for SQL Server 2005/2008 logical/physical and physical models.

Operating System Support Update

CA ERwin Data Modeler r7.3 includes support for Microsoft Windows 7, Microsoft Vista, and Microsoft Windows 2008 Server. Support for Windows 2000 has been dropped.

Note: See Operating System Support (see page 53) for the complete list of supported operating systems.

Integration With Microsoft Visual Studio Team System 2008 Database Edition

CA ERwin Data Modeler r7.3 includes an integration with Microsoft Visual Studio Team System 2008 Database Edition (VSTS Database Edition).

In addition to support for this version, support is included for the previous version, Microsoft Visual Studio 2005 Team Edition for Database Professionals.

Metamodel Reference Documentation

A new metamodel reference document has been produced that provides a comprehensive list of the CA ERwin DM metadata object classes, property classes, aggregations, and associations. This metadata information can be used in any of the following CA ERwin DM functional areas:

■ API

■ Forward engineering templates

■ Macros

■ Metadata reports

The PDF is called ERwin Metamodel Reference.PDF. It is part of the CA ERwin Data Modeler Technical Documentation Series, which is installed to the \Doc folder. You can also open this PDF from a shortcut on the Start menu.

This document replaces the output you could create from the Generate Metamodel Documentation option on the Help menu in earlier versions of the product.

Compiled HTML Online Help


Compiled HTML Online Help

Online help for all products in the Modeling Suite is now provided in Compiled HTML (CHM) format. This replaces Windows Help (HLP) format provided previously. The CHM help modules include full search capability, indexing, and a comprehensive table of contents. You can click the help button or press F1 in any program context and the online help file opens to the topic relevant to the feature you are using. The table of contents and topics are also synchronized, so that the topic opens the table of contents tree to the appropriate location at the same time it displays the help topic.

Documentation Bookshelf

The Documentation Bookshelf is a free-standing HTML-based reference tool that provides easy access to the online help and core reference documentation for CA ERwin Data Modeler and CA ERwin Model Manager. The Bookshelf provides a "front end" user interface where you can open individual PDF Guides or online help files, or search a combined index for all deliverables.

The Bookshelf is automatically installed with the product unless you select not to install it in the installation wizard. Click the Bookshelf item on the Start menu to open the bookshelf.

A zip file containing the complete Bookshelf is also provided as a download from the Product Documentation Downloads area on the CA ERwin Data Modeler support page.

For more information on using the Bookshelf features, click the "Getting Started" link at the bottom of the main Bookshelf window. This topic introduces the layout of the Bookshelf, the various search options.

Note: The Bookshelf does not include the Template Language and Macro Reference Guide, or the ERwin Metamodel Reference Guide files from the Technical Documentation Series. To access these documents, open them from the \Doc folder where you installed the product. You can also open these PDFs from a shortcut on the Start menu.



Feature-Specific Training Videos

52 Release Notes

Feature-Specific Training Videos

Two new training videos are provided with CA ERwin Data Modeler r7.3 to assist you in getting started with new features. The videos are installed with the program, and can be accessed from the Start menu under CA, ERwin, ERwin Data Modeler r7.3, Videos. The two videos are:

ODBC Data Source

Introduces the new ODBC reporting functionality.

Customizing Forward Engineering Templates (ERwin FE IDE)

Provides an overview of customization options in the Forward Engineering Templates Editor, including an example of modifying a template and using it in schema generation.

Chapter 2: System Information 53

Chapter 2: System Information

Review the following system information before installing and using the product.


Operating System Support (see page 53) System Requirements (see page 54) Supported Target Server Databases (see page 54)

Operating System Support

CA ERwin Data Modeler requires that you have one of the following operating systems installed:

■ Microsoft Windows Vista

■ Microsoft Windows 2008 Server

■ Microsoft Windows 2003 Server

■ Microsoft Windows XP (through SP3)

■ Microsoft Windows 7

Note: CA ERwin Data Modeler support for Microsoft Windows 7 has only been certified on the 32-bit version and not on the 64-bit version.

Administrative Privileges Required for Installation

Because the installation process for CA ERwin Data Modeler writes to the registry and system folders, the person installing, upgrading, or removing CA ERwin Data Modeler must have Administrative privileges. If you run an install without Administrative privileges, all files may not be installed or upgraded, and users will encounter problems when running the software.

Compatibility with Microsoft Visual Studio

CA ERwin Data Modeler includes integration features for the following versions of Microsoft Visual Studio:

■ Microsoft Visual Studio 2005 Team Edition for Database Professionals, part of the Microsoft Visual Studio Team Suite

■ Microsoft Visual Studio Team System 2008 Database Edition (VSTS Database Edition)

The integration also requires that you install the Visual Studio Power Tools. An option to install the Power Tools is provided on the last screen of the installation wizard.

System Requirements

54 Release Notes

System Requirements

The following requirements must be met or exceeded for CA ERwin Data Modeler to install and run correctly:

■ Microsoft-based workstation, Intel Pentium 4 or equivalent

■ 2 GB available hard drive space

■ 2 GB RAM minimum; more is recommended for large models

■ DVD-readable device (only if installing from DVD media)

Note: The minimum screen resolution supported is 1024 x 768. If your screen resolution is less than the minimum supported, some portions of the screen will not be visible.

Supported Target Server Databases

The following target server databases are supported in CA ERwin Data Modeler r7.3.

■ Access (2000/2002/2003)

■ DB2 iSeries (5.x/6)

■ DB2/UDB (8.x/9.x)

■ DB2/zOS (7, 8/9)

■ FoxPro (stabilized support)

■ Informix (7.x, 9.x/10.x/11.x)

■ Ingres (2.6, 2006)

■ MySql (5.x)

■ ODBC/Generic (2.0, 3.0)

■ Oracle (9.x, 10.x/11x)

■ Progress (9.x/10.x)

■ Redbrick (stabilized support, 5.x)

■ SAS (stabilized support)

■ SQL Server (2000, 2005/2008)

■ Sybase (12.5/15)

■ Sybase IQ (12.x)

■ Teradata (2.6, 12)


Chapter 3: Installation Considerations

Review the following installation considerations before installing the product.


Installation Wizard on DVD (see page 55) Silent Install for CA ERwin DM and Crystal Reports (r7.3.6) (see page 56) Installing VSTS Database Edition (see page 57)

Installation Wizard on DVD

When you install from the product DVD, the installation wizard has been enhanced to make it easier for you to install more than one product from the CA ERwin Modeling Suite at a time. After the wizard starts, you are prompted to select from a list of applications to change or install. For example, you can select to install CA ERwin Data Modeler and Crystal Reports 2008 at the same time. After the install process completes, you are prompted to provide your license key for each product using the License Verification dialog.

If you select to install a product for which you do not have a license key, you can use the product for a trial period of thirty days.

Silent Install for CA ERwin DM and Crystal Reports (r7.3.6)

56 Release Notes

Silent Install for CA ERwin DM and Crystal Reports (r7.3.6)

Starting with patch release r7.3.6, you can perform a silent (unattended) installation/upgrade of CA ERwin Data Modeler and/or Crystal Reports. The following commands apply to the install shell executable provided when you download a patch or service pack from the CA ERwin Data Modeler product page on support.ca.com. The following commands and parameters can be used:

PRODUCT=DM

Installs CA ERwin Data Modeler

PRODUCT=CR

Installs Crystal Reports

/s

Makes the setup.exe process silent.

/qn

Makes the setup.msi process silent.

/v" parameters"

Passes the parameters specified in the quotes to the underlying setup.msi file.

Examples ERInstallShellSetup_DMCR.exe /s /v" /qn PRODUCT=DM,CR"

Installs/upgrades the products in the order: CA ERwin Data Modeler, Crystal Reports.

ERInstallShellSetup_DMCR.exe /s /v" /qn PRODUCT=CR"

Installs/upgrades only Crystal Reports. Note: requires that CA ERwin Data Modeler r7.3 build 1666 or later is already installed.

ERInstallShellSetup_DMCR.exe /s /v" /qn"

When the product switch is not provided, both products are installed/upgraded.

Important Note

The silent install is not supported on the Windows 7 operating system.

Installing VSTS Database Edition


Installing VSTS Database Edition

When you install CA ERwin DM, the installation script checks for a copy of Microsoft Visual Studio 2005 Team Edition for Database Professionals or Visual Studio Team System 2008 Database Edition. If it detects a copy of either version, the integration components are automatically installed unless you cancel the selection to install the components. You can also modify an existing installation of CA ERwin DM to add the VSTS Database Edition integration. See the installation instructions in Chapter 1 of the Integration Guide, provided in PDF format in the \Doc folder where CA ERwin DM is installed.


Chapter 4: General Considerations

This section contains general information you should know before using CA ERwin Data Modeler r7.3.


Metadata Elements Renamed (see page 60) Synchronization Limitation With VSTS Database Edition and CA ERwin Data Modeler (see page 61)

Metadata Elements Renamed

60 Release Notes

Metadata Elements Renamed

For CA ERwin DM r7.3, much of the metadata has been renamed. The renaming affects object types, property types and SCAPI-specific property types. The name changes fall into two categories:

First are the changes to make the names more consistent and to better represent the model data. An example of this is the property type "For" which has been renamed "For_Character_Type".

Second is the replacement of space characters with underscores in all metadata element names. Prior to CA ERwin DM r7.3, both object type and property type names accessed via SCAPI contained spaces, but those same names used underscores instead when saved to XML. To remove this inconsistency, all space characters within such names have been replaced by underscores.

For most users of CA ERwin DM, this change is transparent and will not affect your day-to-day work. Awareness of this change, however, is important for users of SCAPI and the new CA ERwin DM ODBC interface. If you worked with the pre-r7.3 metadata names, you should be aware of the r7.3 changes. SCAPI applications and scripts created prior to r7.3 must be updated to account for the new metadata names before use with CA ERwin DM r7.3. To assist in this updating process, the following CSV files are installed to the \doc folder where you install CA ERwin DM r7.3:

Renamed Metadata (SCAPI).csv

Contains the full set of changed metadata names. It is a two column CSV file that contains the old name, new name pairs.

Renamed Metadata (XML).csv

Contains the subset of metadata names that appear as changed in XML files. Metadata names whose only change was the replacement of space characters are not changed at all from the perspective of CA ERwin DM XML format, and therefore do not appear in this file.

Renamed SCAPI Properties.csv

Contains the SCAPI-only property names that were renamed.

Replaced Properties.csv

During the renaming process, several groups of properties emerged as essentially synonymous. Rather than create an artificial differentiator into the names, the names were merged. This file lists the properties affected by this process, providing the original property name and the replacement name.

Synchronization Limitation With VSTS Database Edition and CA ERwin Data Modeler


Synchronization Limitation With VSTS Database Edition and CA ERwin Data Modeler

When you add a CA ERwin DM model to a VSTS Database Edition project, a connection is established between the two products. When you save and close your CA ERwin DM model, your changes are made to the VSTS Database Edition schema.

A known problem with the Microsoft VSTS Database Edition API results in certain user objects not being renamed or deleted from the VSTS Database Edition schema after being renamed or deleted in the CA ERwin DM model. This applies to objects that are not owned by the schema, such as user, database role, partition function, partition scheme, and the schema itself. If you rename or delete these objects from a model and save your changes, the objects are not automatically renamed or deleted in the VSTS Database Edition project. You must manually delete the instances of these object types from the VSTS Database Edition Schema View. If you do not manually modify the VSTS Database Edition schema, the objects are automatically repopulated into the CA ERwin DM model the next time you open it in VSTS Database Edition.

This issue will be resolved when an updated API is available from Microsoft.

Chapter 5: Known Issues 63

Chapter 5: Known Issues

This section contains known issues you should know before using CA ERwin Data Modeler r7.3.


Double-Byte Character Display (see page 63) Known Issue With Meta Integration Bridges for Microsoft Office Excel (see page 63) Silent Install on Windows 7 (see page 63)

Double-Byte Character Display

Some double-byte characters added to the Windows operating system since 2004 do not display correctly in CA ERwin DM when Vista is your operating system. This only applies to some languages in which CA ERwin DM is certified but not localized (such as Korean, Russian, Chinese) and does not affect English or European languages.

Known Issue With Meta Integration Bridges for Microsoft Office Excel

There is a known issue in r7.3.8 SP2 when working with the Microsoft Office Excel import and export Meta Integration bridges.

■ Importing XLS and XLSX Excel files using the Microsoft Office Excel import bridge fails.

■ Exporting to XLS Excel file format using the Microsoft Office Excel export bridge fails when the bridge parameter for “Format” is set to “Standard-1_0.”

Microsoft and Meta Integration Technology are aware of this issue and will provide a fix for a future CA ERwin DM patch release.

Silent Install on Windows 7

There is a known issue with r7.3.8 SP2 when running the silent install on Windows 7. At this time, we do not support the silent install on the Windows 7 operating system.


Chapter 6: Fixed Issues

This section includes the issues that are fixed in CA ERwin Data Modeler release 7.3.12 SP3.


Issues Fixed in this Release (see page 65)

Issues Fixed in this Release

The following issues are fixed in CA ERwin Data Modeler release 7.3.12 SP3:

Problem No.: 100 SUPERTYPE SUBTYPE NULL OPTION

Issue No.: 20059769-1

In a specific model that was created using CA ERwin Data Modeler release 7.3.10, when the supertype subtype rollup was used, the non-key column NULL option in the subtype tables were not handled properly. Subtype non-key NOT_NULL was not displayed as NULL in the rolled-up table.

Problem No.: 10525 CC - ERWIN CRASHES

Issue No.: 18640105-1

In a specific model that was created using CA ERwin Data Modeler release 7.3.5 or 7.3.6, a Complete Compare session caused the model to crash. The target server of the model was SQL Server 2005 and the following options were selected:

■ Allow demand loading - physical level compare

■ Exclude unaligned options in the right model

■ Include only generated objects

■ Select active subject area

■ Use name matching

Problem No.: 10593 WRONG DROP COLUMN

Issue No.: 18627485-1

When a specific model was compared with another model that was reverse-engineered from an Oracle database, filtering only on indexes and key constraints, the generated alter script included DROP COLUMN statements.


66 Release Notes

Problem No.: 10596 ADD PARTITION RANGE

Issue No.: 18741645-1, 18903579-2, 20100747-1

In CA ERwin Data Modeler release 7.3.6, if a partition was added to an existing partitioned table in a specific Oracle model, the following code was included in the ALTER script :

SQL> create table tempabc (col1 varchar2(10), col2 int )

2 partition by range (col1)

3 ( partition p1 values less than ('A%')

4 );

Table created.

SQL> alter table tempabc

2 add partition p2 values less than ('C%');

Table altered.

However, if a partition was added to an existing partitioned table, the script in the Alter Script/Schema Generation dialog included a drop and create table statement, instead of simply altering the table.

Problem No.: 10602 RE CRASH

Issue No.: 18723518-1, 19754859-1

CA ERwin Data Modeler crashed when a specific model was reverse-engineered from an Oracle database.

Problem No.: 10738 ERWIN NEEDS TO CLOSE

Issue No.: 19051753-1

In a specific model that was created using CA ERwin Data Modeler release 7.3.8, when an identifying relationship between two tables was deleted and the PK was moved to the other table, the Migration Conflict dialog appeared. When clicked OK, the application crashed.



Problem No.: 10744 CHECK MODEL ERRORS 2

Issue No.: 19072346-1

In a model that was created using CA ERwin Data Modeler release 7.3.8, when an entity was marked as Logical Only and the model was checked before forward engineering, the following error was displayed for this entity:

Table should contain at least one column in order to successfully generate.

Primary key on the table has no members defined.

However, no such message was generated for other entities.

Problem No.: 10768 CC AND IGNORE CODE COMMENTS

Issue No.: 19079110-1

CA ERwin Data Modeler release 7.3.8 and 7.2.8 did not find the changes in a specific store procedure code when the Ignore code comments option was selected.

Problem No.: 10769 ORACLE.FET, FIX REQUEST

Issue No.: 19041989-1

In CA ERwin Data Modeler release 7.3.8, for an Oracle 10g model, when a Validation Rule/Check Constraint value was changed and the check constraint was associated with a column, the resultant Alter Script syntax included SQL statements to drop the constraint and then modify it. This is incorrect as the syntax should be drop and add, instead of drop and modify.

Problem No.: 10830 FOCUS PROBLEM

Issue No.: 19187714-1

In CA ERwin Data Modeler release 7.3.8 and 7.3.9, the down arrow on the keyboard did not work properly on the SQL Server Partition Tab Editor dialog.

Problem No.: 10832 RE OF PARTN INDEX INCORRECT

Issue No.: 19192162-1

In CA ERwin Data Modeler release 7.3.8, when a specific model that included a partitioned index was reverse-engineered, incorrect index members were shown. The partitioning column of the partitioning index was included as the first member of the partitioned index.


68 Release Notes

Problem No.: 10862 SYBASE - REFERENTIAL CONSTRAINT

Issue No.: 19222734-1

In CA ERwin Data Modeler release 7.3.9, a Sybase 15.x model included a table with 12 foreign keys. When a column was added to the middle of the table, the foreign keys were dropped in the ALTER script. However, the keys were not included subsequently.

Problem No.: 10880 EXTERNAL ORGANIZATION CAPTURE

Issue No.: 19248991 -1

CA ERwin Data Modeler release 7.3 did not reverse-engineer a specific model that included external sources (External Organization database).

Problem No.: 10888 CC: TRIGGERS MISMATCH

Issue No.: 19257105-1

In CA ERwin Data Modeler release 7.3.3, when a specific Logical/Physical model was compared with a database, some of the triggers were shown as not aligned, although they were aligned.

Problem No.: 10903 MISSING SP/RE FM SS 2008 DB

Issue No.: 19266419-1

In CA ERwin Data Modeler 7.3.8, when a specific model was reverse-engineered from AdventureWorks 2008 Database, one of the stored procedures was not reverse-engineered.

Problem No.: 10985 ATTRIBUTE TO COLUMN PROBLEM

19627310-1, 20095616-1, 20353336-1, 20420873-1, 20459037-1, 20462500-1, 20551142-1, 20551680-1, 20659093-1, 20844484-1

In CA ERwin Data Modeler release 7.3.9, when a naming standards file and a macro were used for name mapping, the macro did not expand properly.

Problem No.: 11085 COMMENTS IN SCRIPT GENERATION

Issue No.: 19715117-1

In CA ERwin Data Modeler release 7.3.10, for a DB2/zOS Version 8/9 model, the DDL was generated for the comments added to columns, although the Comments option was not selected in the Alter Script Schema Generation dialog.



Problem No.: 11096 CRASH CLOSING ERWIN

Issue No.: 19668378-1, 19722798-1, 19735644-1, 19853099-1, 19893324-1, 19905620-1, 20046281-1, 20100521-1, 19573063-1, 19962097-1

CA ERwin Data Modeler release 7.3.5 crashed when the application was closed.

Problem No.: 11100 SS2005 RE UDP

Issue No.: 19675013-1, 20061605-1, 20267787-1

In CA ERwin Data Modeler 7.3.10, when a specific SQL Server 2005 database was reverse-engineered, the following error message was displayed:

An unexpected condition has occurred. this condition is not inherently fatal".

GDM-39, GDM-41, GDM-40, GDM-33.

This error appeared only the first time the database was reverse-engineered. Subsequent reverse-engineering processes went on without any errors. If the application was closed, reopened and then closed, the errors recurred.

Problem No.: 11120 CRASH WHEN FUNCTION IS RE'D

Issue No.: 19496235-1, 20050955-1, 20060390-1, 20116801-1, 20151662-1

In CA ERwin Data Modeler 7.3.10, when a specific SQL Server 2005 database was reverse-engineered, the application crashed when Function was selected as an object to be reverse-engineered.

Problem No.: 11148 FE SQL SYNTAX RELATIONSHIP SHOULD NOT GENERATE IN SQL SYNTAX

Issue No.: 19949054-1

In a specific model in CA ERwin Data Modeler release 7.3.10, although a relationship was set to not generate, it still appeared in Forward Engineering SQL Syntax.

Problem No.: 11162 SWITCH TRANSFORM TO SHOW SOURC

Issue No.: 19992173-1

In CA ERwin Data Modeler release 7.3.10, when supertype subtype roll down transform was performed for an entity, the application either did not respond or crashed when Show Transform Source Objects or Show Transform Target Objects was clicked.


70 Release Notes

Problem No.: 11163 VIEW SYNTAX CRRASHING ERwin

Issue No.: 19983213-1, 20416583-1

In CA ERwin Data Modeler release 7.3.10, when a specific SQL Server 2008 database or a View (SQL syntax) was reverse-engineered, the application crashed.

Problem No.: 11178 DDL SCRIPT ALTER CONSTRAINT ST

Issue No.: 19917340-1

In CA ERwin Data Modeler release 7.3.10, a specific model generated storage information on indexes on some of the ALTER TABLE statements. This happened only when the ALTER TABLE statements included addition of indexes that had a constraint state.

Problem No.: 11179 XML IMPORT FIX

Issue No.: 20063339-1

In CA ERwin Data Modeler 7.3, when sub-type super-type rollup transform was performed and source-to-target mapping was done on a model, the model became corrupted. When the model was saved as an XML file and the XML file was opened, the model was empty.

Problem No.: 11190 ADD MODEL SOURCE ERROR: GDM23

Issue No.: 19948001-1

In CA ERwin Data Modeler release 7.2, when the Add Model Source function was used on a specific model, the following error was displayed:

GDM-23 WARNING: A transaction rollback was attempted out of sequence.

Problem No.: 11241 COLUMN LOST AFTER DERIVING

Issue No.: 19973773-1

In CA ERwin Data Modeler release 7.3, when a Logical/Physical model for Oracle 10g/11g was derived from a Logical only model, some columns from the child tables were missing. This happened for all options on the Model Naming Options dialog.

Problem No.: 11248 CC CAUSES CRASH

Issue No.: 20102332-2

In CA ERwin Data Modeler release 7.3, when a specific model was compared against a blank model, the application crashed.



Problem No.: 11249 CAN'T RE VIEW PRIMARY KEYWORD

Issue No.: 20474352-1

In CA ERwin Data Modeler release 8.1, the Views in an Oracle 11g database could not be reverse-engineered, as it included the reserved word or keyword Primary without quotes.

Problem No.: 11266 LOGICAL ONLY WILL NOT UNCHECK

Issue No.: 20225656-1, 20236843-1, 20236843-2, 20254739-1

In CA ERwin Data Modeler release 7.3.10, in some of the models that were created using Teradata Database 12, when a relationship was changed from Logical Only to Logical/Physical, it did not stay Logical/Physical. When the model was saved as XML and opened again, it solved the problem, but caused other problems.

Problem No.: 11293 CRASH ON OPENING NEW MODELS

Issue No.: 20052461-1, 20261885-1, 20340854-1, 20718381-1

On a specific computer that had CA ERwin Data Modeler release 7.3.7, new models could not be created. When a new model was created, the application crashed. Existing models could be opened, but new Subject Areas could not be created in existing models.

Problem No.: 11332 MISSING TRANSFORMS IN 7.3.11

Issue No.: 20260685-1

When a specific model was upgraded to CA ERwin Data Modeler release 7.3.11, all the column-denormalization transforms were missing. The conversion log was not created.

Problem No.: 11333 MISSING TRANSFORMS ISSUE 2

Issue No.: 20260685-2

When a specific model was converted from CA ERwin Data Modeler release 7.3.6 to 7.3.11, the model did not open properly and many transforms were missing.


72 Release Notes

Problem No.: 11401 CANNOT ADD MORE ATTRIBUTES

Issue No.: 20352349-1

In CA ERwin Data Modeler release 7.3.11, for an existing Oracle 10.x/11.x model, new columns could not be added. The following error message was displayed:

ESX-174101: Column exceeds limit for table.

However, columns could be added to a new model.

Problem No.: 11405 DB2.FET inline FK generate

Issue No.: 20291170-1

In CA ERwin DM release 7.3, for a DB2 z/OS version 7 through 9 model, the FK constraints of a relationship were included in the Forward Engineering script, despite not selecting the Generate option.

Problem No.: 11420 RES ORACLE prodOptFieldDType

Issue No.: 20380093-1

In CA ERwin DM release 7.3.11, an Oracle 11g database could not be reverse-engineered if it included an external column and the access parameter for the column exceeded a certain number of characters.

Problem No.: 11424 DEFALTS LOST ON CONVERSION

Issue No.: 20378094-1, 20552287-1

When a DB2 z/OS model was converted from CA ERwin Data Modeler release 7.3.9 to 7.3.11, the default values were not retained. In addition, for some models the CCSID property was not selected for the tables.

Problem No.: 11435 ODBC.FET

Issue No.: 20387067-1

In CA ERwin Data Modeler release 8.0, when the DISTINCT clause was used for a View for an ODBC model, the Forward Engineering script included incorrect SQL.

Problem No.: 11460 CRASH AFTER SWITCH SOURCE/TARG

Issue No.: 20414253-1

When a DB2 z/OS model was converted to CA ERwin Data Modeler release 7.3.11, the transforms did not switch from the target mode to the source mode. The application crashed when the Show Source Mode icon was clicked.



Problem No.: 11461 DERIVE:LP-LO, DOMAIN CHANGE

Issue No.: 20361389-1

When a Logical Only model was derived from a specific Logical/Physical model in CA ERwin Data Modeler release 7.3.11, the domain names were changed. When this model was compared with a blank model, the following error message was displayed:

An Attempt was made to read property type 'Parent_attribute_ref' (1075849136) on

object type 'Domain' (1075838983) but no association exists between the pair.

Problem No.: 11467 SWITCH TARGET/SOURCE IMPOSSIBL

Issue No.: 20414483-1

When a specific model was converted to CA ERwin Data Modeler release 7.3.11, it did not switch from Show Source to Show Target mode of transforms.

Problem No.: 11482 GDM-91 ERROR DELETING COLUMN

Issue No.: 20437174-1

In CA ERwin Data Modeler release 7.3.11, for a SQL Server 2005 or 2008 model, if the length of an attribute was set to the maximum length allowed, and later the column was deleted from the model, the GDM-91 error was displayed.

Problem No.: 9179 CONV./UPPER CASE NOT SUBJ AREA

Issue No.: 16660447-1

In AllFusion ERwin Data Modeler 7.2.5, when the tables and column names were changed from lower case to upper case in the main Subject Area, the change was not applied to other Subject Areas that included these tables and columns.

Problem No.: 1201 CAN'T EXPORT CALCULATED

Issue No.: 19515334-1, 19583692-2, 19616984-1

For a specific model in CA ERwin Data Modeler release 7.3.10, [calculated] differences could not be resolved in the Model Manager Difference Reconciliation dialog. In addition, these differences could not be imported or exported.

Problem No.: 1213 3 way merge performance

Issue No.: 19765728-1

For a specific model in a SQL Server 2008 Mart in CA ERwin Data Modeler release 7.3.10, the Conflict Resolution screen was displayed after more than 50 minutes after a user action.


74 Release Notes

Problem No.: 1217 UPG 2000 TO 2008

Issue No.: 20020824-2, 20129735-1

When the Model Manager was migrated from SQL Server 2000 to SQL Server 2005, users could log in. However, when the MM Security Manager was opened for the first time, the security profiles were deleted. Users could not log in to Model Manager.

Problem No.: 10529 PROBLEM WITH LOGICAL, PHYSICAL

Issue No.: 19168624-2, 19168624-3, 19618117-1

In CA ERwin Data Modeler 7.3, the Identifying Relationship line disappeared in the Logical model, when the Physical Only property of the relationship was selected and unselected.

Problem No.: 10529 PROBLEM WITH LOGICAL, PHYSICAL

Issue No.: 19168624-1

In CA ERwin Data Modeler 7.3, when the Logical Only property was selected for two entities, the property was applied automatically to the relationship between the entities. However, when the property was unselected for the entities, it did not change for the relationship automatically.

Problem No.: 10797 ESX-1017 on RE of Validation Rules from SQL Server 2005/2008

Issue No.: 19111099-1

In CA ERwin Data Modeler release 7.3.8, when the validation rules were reverse-engineered from a SQL Server 2005 database, the following error message was displayed:

Advisory File Created <Level=0><Information> Reverse Engineer <Level=>

<Successful Transaction> Set Property: Type Object type identifier = xxxxxxxx

Object id = xxx Property type identifier = xxxxxxxxxxx <Level=2><Information>

ESX-1017: Valid_Value object has been deleted due to incompatibility with the

value of property Type [Validation_Rule:CK__tblAPRecu__are_L__0116BF70]

This resulted in the validation rule syntax mismatch with the SQL Server 2005 Database.

Problem No.: 10847 BAD TD PPI SYNTAX FROM RE

Issue No.: 19194992-1

For a Teradata Database 12 model, CA ERwin Data Modeler release 7.3.8 did not parse the partition expression in the partition clause properly.



Problem No.: 10855 Set Logical Data Type on REDB for L/P Models

Issue No.: 18859175-1

When a Logical/Physical model was created by reverse engineering in CA ERwin Data Modeler release 7.2, users could enter physical data type values in the logical model.

Problem No.: 11122 XFRM-POSTLOAD ERRORS IN 7.3.11

Issue No.: 19852577-1

When transforms were upgraded from an earlier version to CA ERwin Data Modeler release 7.3.11 and recreated in 7.3.11, if these transforms were saved in an earlier version and again opened in 7.3.11, the transforms included several post load processing errors.

Problem No.: 11138 REQUIRE 6.3 MITI VERSION

Issue No.: 19850995-1

An end-user was not able to download the MIMB-OEM/6.3.0.dev file from the Meta Integration FTP server while using CA ERwin Data Modeler release 7.3.

Problem No.: 11145 SHOW SOURCE/TARGET CRASHES

Issue No.: 19930130-1

When the Show Transform Source Objects icon was clicked in CA ERwin Data Modeler release 7.3, all transforms were not displayed.

Problem No.: 11146 7.2 TO 7.3 TERADATA CONVERSION

Issue No.: 19889822-1

When CA ERwin Data Modeler was upgraded from 7.2.9 to 7.3.10, for some of the Teradata models, no editor opened, except for the Column Editor.

Problem No.: 1211 7.2.8 ERW/MM MODEL GDM-41

Issue No.: 19859315-1

When a model was switched from Logical to Physical in CA ERwin Data Modeler release 7.2.8, it took a long time to load and displayed the error message, GDM-41. After the model was upgraded to CA ERwin Data Modeler release 7.3.10, the following message was displayed and the model did not open:

Upgrading transactioned metadata:(7.2 schema 12.2) to (7.3 schema 0.2) Failed.


76 Release Notes

Problem No.: 1212 MM Performance

Issue No.: 19849345-1, 19922847-1, 20258464-1, 19932844-1

When a model was upgraded from CA ERwin Data Modeler release 7.1.2 to 7.3.10, it took around 30 minutes to open. In CA ERwin Data Modeler release 7.1.2, it took only three minutes.

Problem No.: 11145 SHOW SOURCE/TARGET CRASHES

Issue No.: 19930130-1

In CA ERwin Data Modeler release 7.3.6, transforms were displayed on the Physical model, but did not display on the Logical model.

Problem No.: 11789 RE FROM ISERIES RESULTS IN MULTIPLE INDEXES

Issue No.: 20846941-1

When a DB2 iSeries database was reverse-engineered into a CA ERwin Data Modeler release 7.3.11 model, a duplicate index was created for each index.

Problem No.: 11504 ERWIN 7.3 SQL

Issue No.: 19679584-1, 20447252-1, 20728300-1, 20728300-2

When several objects were retrieved through queries in CA ERwin Data Modeler 7.3.9, the content was truncated after the first 255 characters. This happened for objects such as UDP values, stored procedures, tables and columns.

Problem No.: 10975 RE ISERIES DB HAS 2 AK INDEX WITH SAME NAME

Issue No.: 19424691-2

When a specific DB2 iSeries database was reverse-engineered into CA ERwin Data Modeler release 7.3.9, two Alternate Key (AK) indexes were created for the same index member. The original database had only one AK index for this index member.

Problem No.: 1207 COPY REPORT TO MM NOT WORKING

Issue No.: 19627483-1, 20869333-1

The Copy Report to ERwin MM option did not work in CA ERwin Data Modeler releases 7.3.8, 7.3.9, and 7.3.10.



Problem No.: 11140 INCORRECT SYNTAX NEAR PRIMARY

Issue No.: 19926320-1

In CA ERwin Data Modeler release 7.3.8, when a model was forward-engineered to SQL Server 2008, the following error message was displayed:

ALTER DATABASE dgetstats_test_v090910_Forward_Engineer MODIFY FILEGROUP PRIMARY

ReadWrite [Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax

near the keyword 'PRIMARY'. Execution Failed!

Problem No.: 11312 GETTING ERROR OPENING ERWIN

Issue No.: 20222505-1, 20224619-1, 20266280-1, 20273873-1

When CA ERwin Data Modeler release 7.3.10 was opened, the following message was displayed:

Application error erwin.exe instruction at (ref) memory cannot be read.

Problem No.: 11053 UDD GENERATED SQL

Issue No.: 19583692-1

In CA ERwin Data Modeler release 7.3.10, when a column was attached to a domain and User Datatype was selected in the Forward Engineering Schema Generation dialog, the DDL still included the domain data type for the column instead of the column data type.

Problem No.: 11423 PROPERTY LOGICAL ONLY

Issue No.: 20362598-3, 20385431-1

In CA ERwin Data Modeler release 7.3.11, when the Logical Only check box was selected for an entity, the following message was displayed:

Entity Editor

Set Property: Is_Logical_Only

Set Property: Is_Logical_Only

Set Property: Index_Members_Order_Ref

EXC-85: Failed to set property [Index_Members_Order_Ref]

Problem No.: 11353 NO WARNING WHEN DELETE ENTITY IN ENTIRE MODEL

Issue No.: 20321366

In CA ERwin Data Modeler 7.3.10, when an entity was dragged from the Model Explorer to a Subject Area and the Delete was clicked, the entity was deleted from not just the Subject Area, but the entire model, without displaying any confirmation message.


78 Release Notes

Problem No.: 11801 FE:INDEX PHYSICAL PROP MISS

Issue No.: 20870137

When a CA ERwin Data Modeler release 7.3.11 model was forward-engineered to a Sybase Adaptive Server 12.5 or 15 database, the DDL did not include some of the properties in the SQL of index, for those indexes that had the Physical Only check box selected in the Index Editor.

Problem No.: 10718 DB2 DDL SCRIPT FORMAT/SPACING

Issue No.: 19525685-1

When a DB2 z/OS version 8 or 9 model was forward-engineered or compared in CA ERwin Data Modeler release 7.3.5 and 7.3.10, the DDL script did not include blank lines or spacing between the statements.

Issue No.: 18794987-1 CHECK CONSTRAINT

CA ERwin Data Modeler releases 7.2.8 and 7.3.7 did not recognize a leading space in a validation rule during Complete Compare. Consequently, a mismatch was displayed for these values.

Problem No.: 10020-2 CC NOGEN NOT LIMITED

Issue No.: 17998582-1

In CA ERwin Data Modeler releases 7.2 and 7.3, when a database level compare was performed with a Subject Area and a database, the Resolve Differences dialog included some ungenerated objects, although the Include Only Generated Objects check box was selected.

Problem No.: 10113-2 AK(DB)PK(MDL)SAMENAMECCIMPRTPR

Issue No.: 18120598-1

When a CA ERwin Data Modeler 7.3.2 model and a database included the same index with the same name and members, where the index in the model was a primary key and the index in the database was a unique index, if this model and the database were compared and differences resolved, duplicate indexes were found and a rolename was lost.



Problem No.: 9962-2 CONSTRAINT WONT SYNC IN CC RD

Issue No.: 17916959-1, 18640389-1, 18774366-1, 18848567-1, 18863793-1, 19099210-1

In CA ERwin Data Modeler release 7.3, when a model was compared with a database, a constraint that was shown as a difference in the Resolve Difference dialog did not synchronize with the database. However, when a physical level comparison was performed in CA ERwin Data Modeler 7.2.9, the constraint was synchronized.

Problem No.: 1245 ERWIN ABNORMAL TERMINATION

Issue No.: 20751200-1, 20788623-1

When opening a model from an Oracle Model Manager mart in CA ERwin Data Modeler releases 7.2.9 and 7.3.11, if the Windows group policy Do not keep history of recently opened documents was enabled, CA ERwin Data Modeler crashed without any error message.

Problem No.: 120824 ERWIN 7.X AND OTHER VERSIONS

Issue No.: 21096061-1

When installing CA ERwin Data Modeler release 7.0 through 7.3.11, if another version of the application (for example, 8.1 or 9.0) is present on the same computer, then the newly installed release (7.0 through 7.3.11) did not export to CA Repository XML format. The following error message was displayed:

Failed to instantiate COM component.

In addition, any Web Portal installation that harvested from CA ERwin Data Modeler release 7 through 7.3.11 files or Mart did not work on that computer.

Problem No.: 11935 PAPER SIZE CHANGE FORGOTTEN

Issue No.: 20456281-1, 20998512-1

The Print Setup dialog did not retain the changes to the Color Appearance and the Paper Size options in CA ERwin Data Modeler release 7.3.11. When the values for these fields were changed, the application reverted the values to default. These values could be changed only through the Windows Control Panel.


80 Release Notes

Problem No.: 12003 WRONG INTERNAL STATE VALURE AFTER TRANSFORM MODE SWITCH

Issue No.: 20976721-1, 21074745-1

When a specific Teradata model that was saved in the Model Manager was updated by multiple users and the users saved the model, it took a long time for the Conflict Resolution dialog to appear. Before the dialog appeared, the following message was displayed:

Could not locate the object in the Modelset in order to calculate its changed

status.

Problem No.: 12003 CAN'T EXPORT INTERNAL STATE

Issue No.: 21074745-1

When a specific model was compared with a blank model and the entire model was exported to the blank model, the supertype/subtype identity transforms showed a difference for the internal state—Mode Changing. These rows could not be exported to the blank model.

Chapter 7: Documentation 81

Chapter 7: Documentation

This section contains information about current product documentation.


PDF Guides (see page 81) New Release Notes PDF (see page 82) Release Numbers (see page 82)

PDF Guides

The core PDF guides for this product are as follows:

■ CA ERwin Data Modeler Implementation Guide (ERwin_Impl.PDF)

■ CA ERwin Data Modeler Release Notes (ERwin_RelNotes.PDF)

■ CA ERwin Data Modeler Methods Guide (ERwin_Methods.PDF)

■ CA ERwin Data Modeler API Reference Guide (ERwin_API_Ref.PDF)

■ CA ERwin Data Modeler and Microsoft Visual Studio Team System 2008 Database Edition Integration Guide (ERwin_VSTS_Int.PDF)

The following documents in the Technical Documentation Series are also provided:

■ ODBC Reporting Guide (ODBC Reporting Guide.PDF)

■ Editing Forward Engineering Templates (Editing Forward Engineering Templates.PDF)

■ Template Language and Macro Reference (Template Language and Macro Reference.PDF)

■ Metamodel Reference (ERwin Metamodel Reference.PDF)

To view PDF files, you must download and install the Adobe Reader from the Adobe website if it is not already installed on your computer.

New Release Notes PDF

82 Release Notes

New Release Notes PDF

Earlier versions of the CA ERwin Modeling Suite products included a readme.html and Release Summary PDF file. The readme file included information about system requirements, supported operating systems, installation considerations, general considerations, a list of the published documentation for the product, and last-minute known issues. The Release Summary provided short descriptions of new features and enhancements for the current release.

For easier access these documents have been combined to a new PDF file, the Release Notes. The list of new features and enhancements is presented in the first chapter. Subsequent chapters include all the information previously published in the readme file.

You can access the Release Notes file from the final screen of the installation process, from the Start menu, and from the \Doc folder, located beneath the folder where you installed the product. The file is also available on the Product Documentation Downloads area on the CA ERwin Data Modeler support page.

Release Numbers

The release number on the title page of a document might not correspond to the current product release number; however, all documentation delivered with the product, regardless of release number on the title page, will support your use of the current product release. The release number changes only when a significant portion of a document changes to support a new or updated product release. If no substantive changes are made to a document, the release number does not change. For example, a document for r7 may still be valid for r7.3. Documentation bookshelves always reflect the current product release number.

Occasionally, we must update documentation outside of a new or updated release. To indicate a minor change to the documentation that does not invalidate it for any releases that it supports, we update the edition number on the cover page. First editions do not have an edition number.

