| CA |
4.0 Supported Target Server Databases
5.0 Installation Considerations
5.1 Installing API Components
5.2 Upgrade Note for 4.1.4 SP4 to r7 or r7.1
6.0 General Considerations
6.1 Template Files for Customizing Model Explorer Display
6.2 Performance When Converting 4.1.4 Models to r7.1 Format
6.3 Understanding Complete Compare Differences After Converting Your Models
6.4 AllFusion ERwin DM API and Changes in Metadata
6.5 XML Option Sets are Database-Specific
6.6 Published Fixes
7.0 Known Issues
7.1 Requirement for Connecting to SQL Server 2005
7.2 Reverse Engineering Oracle Materialized Views
7.3 Reverse Engineering Scripts With Reserved Words
Welcome to AllFusion ERwin Data Modeler r7.1, a member of the AllFusion Modeling Suite. This file contains product installation considerations, operating system support, known issues, and information about contacting CA Customer Support.
AllFusion ERwin Data Modeler (AllFusion ERwin DM) requires that you have one of the following operating systems installed:
The following requirements must be met or exceeded for AllFusion ERwin DM r7.1 to install and run correctly:
The following list of target server databases are supported in AllFusion ERwin Data Modeler r7.1.
The AllFusion ERwin Data Modeler API and two related components (ERwin SPY, and the ERwin Sample API Client) are included in the installation when you choose the Complete Setup Type during setup. If you choose the Custom Setup Type during setup, you can choose to customize the install location, and review the space needed to install each feature.
If you installed AllFusion ERwin Data Modeler 4.1.4 SP4, note that changes to the ERwin metamodel for that version are not available in r7 or r7.1. Metamodel changes were made for Sybase 15 and Sybase IQ 12.5 in 4.1.4 SP4. When you upgrade to r7 or r7.1 from 4.1.4 SP4, you may encounter the following:
Two template files are provided with r7.1 that allow you to 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 ModelExplorer logical display names.tmpl includes display options for the logical model. The file ModelExplorer physical display names.tmpl includes display options for the physical model. The files are installed to the default installation directory for the product (C:\Program Files\CA\AllFusion ERwin Data Modeler r7).
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 work with ERwin data models from version 4.1.4 in r7.1. When you open a 4.1.4 model for the first time in r7.1, there is a one-time performance cost to convert the 4.1.4 model to the r7.1 format. Testing has shown the one time performance cost ranges from 50%-1000%. Individual results may vary due to differences in models and hardware.
If you are working with ERwin 4.1.4, you can upgrade a model by opening and saving it in r7.1. You can also "round-trip" your r7.1 model by saving it as a 4.1.4 model and opening it again in r7.1. You can use Complete Compare to compare the models as you work with them in version 4.1.4 and r7.1.
The technical document "Understanding Complete Compare Differences After Converting Your Models" helps you understand differences you may encounter in Complete Compare when working with 4.1.4 and r7.1 models. You can find the document on http://supportconnect.ca.com in the Technical Document Index on the Product Home Page for AllFusion ERwin Data Modeler.
There are .csv files located in the Doc directory after you install AllFusion ERwin DM that describe the changes in metadata between Version 4.1.4 and r7.1. Specifically, these .csv files describe changes to object type names and property type names, and also lists new and replaced object and property types.
For more information, see the AllFusion ERwin DM API Reference Guide.
In r7.1, a new feature allows you to create custom Option Sets for Forward- and Reverse Engineering, and to save the Option Set as an XML file. Because XML Option Sets are database-specific, you cannot use an XML Option Set created for one target server with a model using another target server. To avoid an error message when you change target servers and then Forward or Reverse Engineer, create a unique XML Option Set for each target server in your modeling environment.
All published fixes for this product can be found through Published Solutions on SupportConnect.
If you are trying to connect to SQL Server 2005 from a machine that does not have the SQL Server 2000 client installed, you will not be able to connect to SQL Server 2005 using AllFusion ERwin Data Modeler or AllFusion Model Manager. AllFusion ERwin Data Modeler and AllFusion Model Manager require the use of DB-Library for connecting to SQL Server databases. SQL Server 2005 no longer distributes the DB-Library files, though DB-Library is supported for connecting to SQL Server 2005.
In order to be able to connect to SQL Server 2005, the file NTWDBLIB.DLL needs to be installed on your workstation. If you have a SQL Server 2000 installation CD, the SQL Server 2000 client can be installed from the CD by executing sqlredis.exe located on in the \x86\Other folder. If you do not have a SQL Server 2000 installation CD, you will need to contact Microsoft support.
A known Oracle bug (4464328) creates problems when reverse engineering from an Oracle database. Materialized views that are dependent on views or materialized views not owned by the connecting user will not contain proper column information after reverse engineering.
To avoid the problem, AllFusion ERwin DM can retrieve the dependency information from the SYS.DBA_DEPENDENCIES catalog view instead of the SYS.ALL_DEPENDENCIES catalog view. However, this requires that the connecting user performing the reverse engineer has SELECT privilege on the DBA_DEPENDENCIES view. If the user does not have this privilege, AllFusion ERwin DM will use the ALL_DEPENDENCIES view.
This problem does not exist for reverse engineering materialized views that are only dependent on tables.
You cannot reverse engineer a script that includes keywords that are designated as reserved words by the target database. For example, in Oracle, reserved words like "table", "view", and "order" cannot be used in the database without quotes. If you reverse engineer a script with reserved words, a generic parser error message displays, warning you of the syntax error.
To learn more about the reserved keywords for your target database, please refer to the SQL documentation provided by your database vendor.
You can enclose reserved words in quotes to avoid this problem. In the Forward Engineering dialog, use the "Quote Names" option listed under "Other Options".
Updated guides for this product are available at http://ca.com/support.
The file names for the PDF guides are as follows:
| Guide Name | File Name |
|---|---|
| AllFusion ERwin Data Modeler Implementation Guide | ERwin_Impl.PDF |
| AllFusion ERwin Data Modeler Methods Guide | ERMethods.PDF |
| AllFusion ERwin Data Modeler Release Summary | ERwin_RelSum.PDF |
| AllFusion ERwin Data Modeler API Reference Guide | ERwin_API_Ref.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.
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.1. 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.
For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at http://ca.com/support.