(495) 925-0049, ITShop интернет-магазин 229-0436, Учебный Центр 925-0049
  Главная страница Карта сайта Контакты
Поиск
Вход
Регистрация
Рассылки сайта
 
 
 
 

Конференция "ERwin"

Обсуждение вопросов, связанных с компанией Computer Associates, ее продуктами ERwin Data Modeler, ERwin Web Portal, ARCserve и др.

 
 
Добавить сообщение »

Тема: Информация об ERwin 4.0 Service Pack 2

Автор:  Новиков Сергей Дата: 16.01.2002 18:57
Данный Service Pack, дополняющий функциональность ERwin и не требующий предварительной установки ERwin4.0/SP1, размещен на нашем ftp.

Вот полные сведения о нём.

Computer Associates ERwin 4.0 SP2 Readme.txt File

Date Last Updated: January 10, 2002

Copyright (c) 2002. Computer Associates International, Inc.
All rights reserved.

This Readme.txt file presents last-minute product information for ERwin 4.0 and ERwin 4.0 - Service Pack 2.

When you open this file in Microsoft Notepad, be sure to turn on the Word Wrap, which is located on the Edit menu.

* How to Print This File
To print this Readme file, open it in Notepad or another word processor, then choose Print on the File menu.
------------------------------------------------------------
Contents
------------------------------------------------------------
1.A. Installation of ERwin 4.0 - Service Pack 2
1.B. Installation of ERwin 4.0 - Service Pack 1
1.C. Installation of ERwin 4.0

2.A ERwin 4.0 - Service Pack 2 Advisory Notes
2.B ERwin 4.0 - Service Pack 1 Advisory Notes
2.C Resolved Problems
2.D. API Enhancements

3.A Contacting Computer Associates Technical Support

-------------------------------------------------------------
1.A. Installation of ERwin 4.0 - Service Pack 2
-------------------------------------------------------------
If you intend to share your models with others, you must install Service Pack 2 on all workstations on which the model may be saved or opened. Models created or saved using ERwin 4.0 Service Pack 2 in a previous version of ERwin 4.0 can not be opened in previous versions due to additional information stored in the model.

If you previously installed a version of ERwin 4.0 (including Patch 1 and Service Pack 1), the ERwin 4.0 - Service Pack 2 setup program will detect the presence of the previous version and will automatically install the necessary Service Pack files.

The setup program installs only the files that are updated for the Service Pack. All other files remain intact and unchanged. The setup program will not delete or change any files that you created including those with the following extensions: .er1, .nsm, .dsm, .xml or .sql files.


-------------------------------------------------------------
1.B. Installation of ERwin 4.0 - Service Pack 1
-------------------------------------------------------------
If you intend to share your models with others, you must install Service Pack 1 on all workstations on which the model may be saved or opened. Models created or saved using ERwin 4.0 Service Pack 1 in a previous version of ERwin 4.0 can not be opened in previous versions due to additional information stored in the model.

If you previously installed a version of ERwin 4.0 (including Patch 1), the ERwin 4.0 - Service Pack 1 setup program will detect the presence of the previous version and will automatically install the necessary Service Pack files.

The setup program installs only the files that are updated for the Service Pack. All other files remain intact and unchanged. The setup program will not delete or change any files that you created including those with the following extensions: .er1, .nsm, .dsm, .xml or .sql files.

If you are using the ERwin-Paradigm Plus integration, you will need an updated version of the Paradigm Plus ERwin Add-In. This maintenance can be obtained on the Paradigm Plus page at: [открыть ссылку]


------------------------------------------------------------
1.C. Installation of ERwin 4.0
------------------------------------------------------------
Use the autorun setup program on the ERwin 4.0 CD to install the product. The autorun setup program is automatically executed when you insert the CD in the drive. You can also execute it by selecting the
setup.exe program in the root folder of the ERwin 4.0 CD.


-------------------------------------------------------------
2.A. ERwin 4.0 - Service Pack 2 Advisory Notes
-------------------------------------------------------------
* There are no advisory notes for Service Pack 2.


-------------------------------------------------------------
2.B. ERwin 4.0 - Service Pack 1 Advisory Notes
-------------------------------------------------------------
* Service Pack 1 Build 1506 Replaced with Build 1511

- A problem was detected with the original Service Pack 1 build 1506. If you had installed the earlier build, please replace it with Build 1511.

- If you have saved a model in Build 1506, non-key attributes may be lost due to the model validation procedures introduced in Service Pack 1 to correct the rolename problems. The following scenario describes how the problem appears in a data model.

For example, a data model includes two tables, named T1 and T2. Table T1 has two Primary Key columns named A and B. Table T2 has two Non-key columns, also named A and B. When a relationship is formed between T1 and T2, the primary keys that migrate from T1 are rolenamed as AA and BB as primary keys in T2.

However, the model validation procedure provided in Build 1506 causes the non-key attributes in T2 to be converted to foreign keys when the relationship was corrected; thus losing the rolenames and the non-key attributes.

- If a similar problem exists in your data model, choose one of the following methods to resolve it after you install the latest version of ERwin 4.0 SP1:

Manually Delete and Recreate the Relationship
----------------------------------------------
1. Open the data model in ERwin 4.0 SP1 (latest build).
2. Delete the relationship between T1 and T2.
2. Add the non-key attributes to T2.
3. Create the relationship between T1 and T2 again.

Use Model-to-Model Complete Compare (If you have a version of the data model that was created with a build prior to 1506 - GA 1298 or Patch 1 1338 or 3.5.2 model)
----------------------------------------------
1. Open the data model in ERwin 4.0 SP1 (latest build).
2. Use Complete Compare to resolve the differences between the two versions of the data model.
3. Import the non-key attributes in T2 from the early version of the data model to the newest version.

Use Model-to-Database Complete Compare (If you have not saved the changes to the database.)
----------------------------------------------
1. Open the data model in ERwin 4.0 SP1 (latest build).
2. Use Complete Compare to import the non-key attributes in T2 from the database into the newest version of the data model.


* Transforms

- Complex transforms can now be applied successively. Complex transforms include Two Table Roll Up, Two table Roll Down, Supertype-Subtype Roll Up, Supertype-Subtype Roll Down, Vertical and Horizontal Partitioning.


* Model Validation

A file conversion problem exists when opening ERwin 3.5.2 models using pre-Service Pack 1 versions of ERwin 4.0 (GA through Patch 1 build 1338). Under specific circumstances, migrated attributes/columns are not properly associated with their parent attributes/columns. Specifically, these symptoms are present only when a migrated key includes multiple attributes/columns. You will notice the problem when a relationship is deleted or modified because ERwin will not delete or modify all of the related migrated columns. In addition, the parent attributes/columns are not correctly migrated through the model to the related child entities/tables.

This problem has been addressed in ERwin 4.0 Service Pack 1. When you open a model in ERwin 4.0 Service Pack 1 (that was saved with GA through Patch 1 builds), ERwin immediately scans the model to detect and correct instances of the problem. However, ERwin Service Pack 1 cannot correct situations in which multiple role-named attributes/columns are migrated from the same key. For these unresolved instances, ERwin will generate a report to identify the affected attributes/columns. The report is a text file named for your model, and will be automatically saved in the directory from which your model was opened. Also for the unresolved instances, there may be a column order change in the affected table(s). ERwin 3.5.2 models opened in ERwin 4.0 Service Pack 1 do not have this problem.

* SQL Server Datatype Display

For a SQL Server database, when the Show Column Datatype option is selected in the Stored Display settings for a physical model, the domain name appears instead of the datatype name in the diagram. This occurs because when the model is forward engineered to the database, the user-defined domains are considered user-defined datatypes.

If a column is created by dragging a domain from the Model Explorer into the table, the new column inherits the user-defined datatype properties, including the domain name. As a result of the inheritance, the domain name appears as the datatype name in the diagram display.

To prevent domains from being created as user-defined datatypes:
-------------------------------------------------------------------
1. In the Domain Dictionary, in the Physical Edit Mode, click the General tab.
2. Select a domain from the Domain list and uncheck the User-Datatype check box, under the Domain Parent list.

Note: If the User Datatype box is NOT checked, the domain is not considered a user-defined datatype, which will cause the datatype of the domain to appear in the diagram as the datatype. If this box is checked, the domain is considered to be a user-defined datatype, which causes the domain name to display in the diagram as the datatype.

* ERwin 4.0 has been validated on: Microsoft Windows 95, Microsoft Windows 98 (first and second editions), Microsoft Windows 2000, Microsoft Windows Millennium Edition, and Microsoft Windows NT
4.0 (service packs 5 and 6) and Microsoft Windows XP.

* This version of ERwin 4.0 is NOT ModelMart enabled. ERwin will support ModelMart 4.0 when ModelMart 4.0 is Generally Available.

* Save As 3.5.2 is supported in ERwin 4.0. Several points to consider when you save an ERwin 4.0 data model in ERwin 3.5.2 format are:

- Any new ERwin 4.0 objects or properties, such as transformed objects, drawing objects, model and object history records, source model links, naming and data standards, summary tables, alternate keys, and report templates will not be preserved.

- Powerbuilder and Visual Basic will not be supported in ERwin 4.0; therefore, these properties will not be processed. (See the note about Powerbuilder and Visual Basic below.)

- ERwin 3.5.2 models saved in ERwin 4.0, and subsequently saved as 3.5.2 models, will have limited ModelMart 3.0.2 capability.

- You can use the Save As 3.5.2 feature only with an ERwin 4.0 logical/physical model. If you have an ERwin 4.0 logical-only or physical-only model, use the Derive New Model feature to create a logical/physical model first.

* Save as 3.5.2 Known Problems:
- Errors may occur if using Save as 3.5.2 with models imported from Oracle Designer 2000.

* ERwin 4.0 assigns a unique model identifier to each model that you create in ERwin 4.0. The model identifier is an internal tracking number that ERwin 4.0 uses to identify model objects and facilitates
Complete Compare, Sync with Model Source, and the updates to the History record. Use the Save as New Model feature to save an existing ERwin 4.0 model with a new model identifier as well as a new name.

* ERwin ERX output is replaced with a new XML format output file. This XML format provides access to all data within an ERwin model and is based on the ERwin 4.0 metamodel. New options have been added to the
File Save As and Open dialogs to support the reading and writing of files in XML format.

* When you Complete Compare two models of different target servers, the following message is displayed after the first step of the wizard: "The target DBMS for (file name) is different from that of the current
diagram. Do you want to change it to the current value before comparing?" If you choose NO, the target servers for both models will be switched temporarily to ODBC for the purpose of compare."

Then you have three options to choose from:

1) YES - will result in changing the target server of the target model to match the current model

2) NO - will temporarily change the target server for both models to ODBC (generic physical)

3) CANCEL - will cancel Complete Compare

* When you Complete Compare two models and the target model is not an ERwin 4.0 model (probably an ERwin 3.5.2 model) and has never been opened in ERwin 4.0, only the Update Current option is enabled in
the first step of the wizard. ERwin 4.0 cannot export changes to an ERwin 3.5.2 model.

* This version of ERwin 4.0 supports DB2 UDB 5.2 and DB2 UDB 6 summary tables. When DB2 is selected as the target server, an additional tool is added to the ERwin toolbox, which you can use to create a summary table. In addition, you can create a summary table using the Model Explorer. Refer to ERwin Online Help for more information about DB2 summary tables.

* Support for Power Builder and Visual Basic is stabilized at ERwin 3.5.2 and will not be provided in ERwin 4.0.

* Support for ERwin Data Dictionary is stabilized at ERwin 3.5.2 and will not be provided in ERwin 4.0.

* ERwin Online Tutorial
The ERwin 4.0 Tutorial is now available and automatically installed with ERwin 4.0 - Service Pack 1.

* ERwin Online Help
You can read about the new features in ERwin 4.0 by choosing "What's New" on the Help menu. Use the WinHelp Index and Find tabs to search for information.

--------------------------------------------------------------
2.C. Resolved Problems
--------------------------------------------------------------

The following list of solutions summaries the issues that have been addressed by Service Pack 2:

Solution Number / Problem Description

220-ONLY FIRST COLUMN CONSTRAINT IS CREATED ON FORWARD ENGINEER
221-SYBASE REVERSE ENGINEER ERROR ON RULE
222-PARSE ERRORS REVERSE ENGINEERING SQL SERVER 7.0 SCRIPT
223-PARSER NOT HANDLING NO ACTION CLAUSE IN DDL FOR SQL SERVER
224-FE DB/2 390 WITH INDEX PARTITIONING NOT GENERATING PROPERLY
225-RE DB2/UDB SCRIPT NOT RECOGNIZING STORAGE AMOUNT WITH SPACE
226-CC OF 2 LOGICAL MODELS NOT ALLOWING FOR REQUIRED FIELD
227-TEXT BOXES NOT DISPLAYED IN SA AFTER OPENING 3.5.2 MODEL
228-ENTITIES/RELATIONSHIP LINES MOVE AFTER DERIVE MODEL
229-REVERSE CAN NOT BE UNSELECTED FOR ORACLE INDEXES
230-PROBLEMS PRINTING CONVERTED 3.5.2 MODELS TO PLOTTER
231-ENTITY BOXES GROW LARGER WHEN SELECTING AND MOVING
232-INDEX PARTITIONS LOST AFTER REVERSE ENGINEER
233-TABLESPACE PARTITION INFORMATION NOT RETURNED BY RE
234-CC WITH DB2 NOT RETRIEVING ALL INFO FOR INDEX PARTITIONS
235-COLUMNS LOST ON CONVERSION OF 3.5.2 TO 4.0
236-PARSE ERROR ON DB2 390 SCRIPT FOR VIEW
237-TERADATA FORMAT INFORMATION FOR COLUMNS LOST ON SAVE
238-FOREIGN KEY ATTRIBUTES NOT RECOGNIZED WHEN ADDING WITH API
239-TROUBLE CREATING POLYGON SEGMENTS OPENING A 3.5.2 MODEL
240-UNABLE TO DELETE USER DEFINED DOMAIN IN DOMAIN DICTIONARY
241-IGNORE DUP KEY CHECKBOX SETTING NOT SAVED
242-OBJECTS DISAPPEAR FROM DISPLAY AFTER PRINTING
243-VIEW DEFINITION CORRUPTED BY REVERSE ENGINEERING FROM SCRIPT
244-CUSTOM COLORS NOT SAVED IN MODEL
245-DOMAIN NAME INHERITED BY COLUMN CHANGES ON COPY/PASTE
246-SLOW PERFORMANCE WORKING WITH CONVERTED 3.5.2 MODELS
247-COMPLETE COMPARE SHOWS WRONG DIFFERENCES FOR ORACLE PK INDEX
248-GPF OR HANG OPENING XML FILE
249-UNABLE TO DEFINE BIGINT AS IDENTITY COL IN SQL SERVER 2000
250-DIAGRAM INFORMATION FROM 3.5.2 MODEL NOT SAVED IN 4.0
251-DATA BROWSER REPORTS INCORRECT
252-INCORRECT PHYSICAL DATATYPE FOR LOGICAL DATATYPE
253-RE OF DB2 SUMMARY TABLE REFRESH SPECIFICATION INCORRECT
254-DB2 SUMMARY TABLES IMPORTS AS USER-DEFINED THEN DISAPPEARS
255-PERFORMANCE PROBLEMS ON DIMENSIONAL MODELS
256-DATA BROWSER FIND IN RESULT SET NOT WORKING CORRECTLY
257-FE FOR DB2 FAILS WHEN IN PHYSICAL ORDER VIEW
258-RE NOT GETTING SYBASE NONCLUSTERED PRIMARY KEY
259-DERIVE MODEL NOT COPYING ENTITY DEF TO TABLE COMMENT
260-MOVING GROUPED OBJECTS RESIZES THEM
261-PERFORMANCE ON ZOOM IN/OUT OF DIAGRAM
262-LOGICAL COL NAME INCORRECT AFTER IMPORT FROM CC PHYS LEVEL
263-FK NOT GENERATED ON IMPORT OF RELATIONSHIP
264-EXPORTING INDEX CHANGES AFTER CC NOT GENERATING DDL
265-EXPORT OF DELETION FAILS AFTER MODEL-MODEL COMPARE
266-CC MODEL/PHYSICAL LEVEL SHOWS LOGICAL NAMES
267-IMPORT OF DATATYPE INCORRECT AFTER MODEL LEVEL COMPARE
268-COLUMNS MISSING FROM DIAGRAM ON CONVERSION FROM 3.5.2
269-FK PROPERTY LOST ON DERIVE OF 3.5.2 MODEL WITH SUBTYPE REL
270-DIFFICULT TO CAPTURE RELATIONSHIP LINES
271-COPY/PASTE LOSING TABLES WHEN USING 3.5.2 MODEL
272-COLUMNS ASSOCIATED WITH ORACLE TRIGGER NOT RETURNED BY RE
273-PROGRESS ACTIVE INDEX SETTING DROPPED ON CONVERSION
274-PROGRESS COLUMN FORMAT INFO NOT SAVED
275-DATATYPE MAPPING NOT FUNCTIONING ON DERIVE MODEL
276-RE PARSING SCRIPT REJECTS LOB TABLESPACE FOR DB2
277-EXPORT TO EXCEL USING DDE WILL TRUNCATE DATA OVER 256 CHARS
278-RE FROM ORACLE ALTERS COLUMN ID IF >256 COLUMNS IN TABLE
279-GPF PERFORMING ROLLUP TRANSFORM IF CYCLIC REL ON CHILD
280-GPF OPENING 3.5.2 ORACLE MODEL CONTAINING PARTITIONS
281-SUPPORT FILE TYPE OF .DDL FOR REVERSE ENGINEERING
282-CLOSE YES NOT GENERATED FOR DB2 TABLESPACE WHEN CHECKED
283-PERFORMANCE ON REVERSE ENGINEERING FROM SCRIPT
284-PAGESIZE VALUES OF 16K, 32K NOT ALLOWED IN EDITORS FOR DB2
285-CC NOT DETECTING DIFFERENCE IN RI ACTIONS
286-POPUP REPORTS NOT GENERATED BY RTB
287-TABLE TRIGGER CODE DISAPPEARS FROM EDITOR
288-INVALID DIFFERENCES REPORTED BY COMPLETE COMPARE FOR DB2/390
289-TEXT IN TEXT BOXES GETS CLIPPED WHEN PRINTING
290-OWNER NOT ATTACHED TO INFORMIX PK OR FK CONSTRAINT
291-ORACLE TABLESPACE GENERATION FAILS WHEN NO LOGGING CHECKED
292-PRINTING HTML PICTURE REPORT TRUNCATES DIAGRAM ON RIGHT
293-RTB PICTURE REPOR TO HTML - MAIN SUBJECT AREA IS BLANK
294-GPF ON IMPORT OF CHANGES FOLLWING COMPLETE COMPARE
295-UNABLE TO RESIZE ENTITIES IN STORED DISPLAY
296-RTB/DATA BROWSER - DOUBLE BYTE CHARACTER PROBLEMS
297-EDITING RTF CREATED BY RTB WILL CORRUPT REPORT
298-UNABLE TO DRAW POLYLINES ON CONVERTED 3.5.2 MODELS
299-INVALID SQL SYNTAX FOR VIEW WHEN TABLE FILTER/SA USED
300-FE NOT GENERATING ALL TABLE PARTITION VALUES
301-CHANGING COL ORDER IN PHYS DISPLAY CHANGES COL ORDER DISPLAY
302-RI TRIGGER FAILS FOR FE FOR INSERT/UPDATE TRIGGERS
303-RELATIONSHIP LINES MOVE AFTER PRINT
304-NON-UNIQUE NAME DISALLOWED WHEN ACCEPTING DUPLICATE NAME
305-INDEX COLUMNS IN WRONG ORDER AFTER REVERSE ENGINEER/CC
306-SUBPAGE OPTION ALLOWED AND SET FOR DB2/390 TYPE 2 INDEX
307-DATASOURCE LOST ON SAVE AFTER CREATING NEW SOURCE
308-CC WITH DATABASE SHOWS INVALID DIFFERENCES
309-IMPORTING DATASOURCES FROM MODEL NOT WORKING
310-GPF IN RTB SELECTING PICTURE REPORT FOR SELECTED DATABASES
311-GPF IN TABLE EDITOR FOR DIMENSIONAL MODELS
312-DATA BROWSER SELECTION FOR DB NAME REPORTS TABLE NAME
313-DATA BROWSER PHYSICAL OBJECT REPORT SHOWS INCORRECT VALUES
314-FE FAILS WHEN OWNER ATTACHED TO INDEX NAME
315-CC DOES NOT USE DIAGRAM DISPLAY LEVEL FOR RESOLVE DIFFERENCE
316-ALL STORGROUPS IMPORTED WHEN RE OF ONLY TABLESPACES FOR DB2
317-ALIAS/SYNONYM INFORMATION NOT SAVED FROM EDITOR
318-BOGUS PRIMARY KEY INDEX SHOWN IN COMPLETE COMPARE
319-UNABLE TO CHANGE DATATYPE ON COL CREATED FROM USER DOMAIN
320-COLUMN ORDER REVERSED SWITCHING TO PHYSICAL ORDER DISPLAY
321-GPF CANCELLING CC WITH DB WHERE VALIDATION RULES ARE PRESENT
322-ON CHILD UPDATE RESTRICT TRIGGER SYNTAX INCORRECT
323-DEFER NO OPTION LOST ON RE FROM SCRIPT FOR DB2
324-INCORRECT COMMENTS IN DB2 DDL ON EXPORT FROM CC
325-PKS OMITTED FROM REVERSE ENGINEERING
326-CC NOT DETECTING CHANGE IN FOREIGN KEY CONSTRAINT NAME
327-IDENTITY START VALUE INCORRECT ON FE FOR DB2
328-INCONSISTENCIES WITH DOMAIN NAME PROCESSING
329-DB2 UDB DOMAIN/COLUMN NAMES TRUNCATED
330-SUPERTYPE/SUBTYPE REL NOT IMPORTED/EXPORTED BY CC
331-GPF ON DATATYPE STANDARDS SWITCHING FROM LOGICAL TO PHYSICAL
332-REVERSE AND LOGGING CAN NOT BE REMOVED FROM ORACLE DDL
333-GPF MOVING KEY GROUP EDITOR ON SCREEN
334-GPF CANCELLING COMPLETE COMPARE WITH DATABASE


The following list of solutions summaries the issues that have been addressed by Service Pack 1:

Solution Number / Problem Description

2 - MANY TO MANY RELATIONSHIP MISSING AFTER SAVE AS 3.5.2
3 - REVERSE ENGINEER NOT GETTING NAMES OF FOREIGN KEY INDEXES
31- HOTLINKS NOT EXPANDING FOR GROUPED OBJECTS
32- SELECTING SYNONYM LEAVES DATABASE/COMMENT FIELDS PROTECTED
33- FOREIGN KEYS NOT GENERATED AFTER REVERSE ENGINEER
32- HISTORY NOT DISPLAYED PROPERLY IN ATTRIBUTE EDITOR
35- SYNC OF MODEL NOT DETECTING CHANGE OF ATTRIBUTE DATATYPE
36- CC DB2 UDB CHANGE TO PRIMARY KEY GENERATED INCORRECT DDL
37- PERFORMANCE ISSUE WITH MANY DOMAINS
38- ADDING PREFIX ON DERIVE MODEL AFFECTS SOURCE MODEL
39- DB2/390 COMPLETE COMPARE SHOWING INCORRECT DIFFERENCES
40- SQL SERVER CREATE TABLE COLUMN DEFAULTS TAGGED AS BOUND
41- EXPORT OF COLUMN LEVEL CHK CONSTAINTS DOES NOT GENERATE SQL
43- ALLOW DB2 ALTERNATE CATALOG SELECTION
44- SQL SERVER 7 DEFAULT LIST INCORRECT
45- ERWIN HANGS ON MODEL CLOSE
46- DB2/UDB6 AUTH-IDS NOT QUALIFYING INDEXES PROPERLY
47- COPY/PASTE OF ENTITY LOSES UDP VALUES
48- DB2/UDB COMPLETE COMPARE OF OBJECTS SHOW INCORRECT VALUES
49- SUPPORT FOR REPLICATED DIMENSIONS
50- RTB SELECT ONLY FILTER NOT WORKING PROPERLY
51- DB2 ASCENDING INDEX COLUMNS NOT RECOGNIZED PROPERLY
53- CC DB/2 DIFFERENCES FOR INDEX CLUSTERING LISTED TWICE
54- SQL SERVER 7 CHANGE SCRIPT INCORRECT FOR CHANGE IN DEFAULT
55- UNABLE TO INVOKE COLUMN EDITOR IN PHYSICAL MODEL AFTER OPEN
56- INCORRECT COL ORDER EXPORTING CHANGES
57- COMPLETE COMPARE NOT MATCHING VALIDATION RULE NAME PROPERLY
58- UNABLE TO GENERATE DEFINE NO FOR DB2 TABLESPACE
59- UNABLE TO GENERATE LOG NO FOR DB2 TABLESPACE
60- UNABLE TO GENERATE TRACKMOD NO FOR DB2 TABLESPACE
61- FE FOR DB2 UDB GENERATES INCORRECT PAGE SIZE STATEMENT
62- CC REPORTS DIFFERENCE FOR DB2 SUBPAGE ON TYPE 2 INDEX
64- DB2/390 FE TO SCRIPT CREATES OBJECTS IN WRONG ORDER
65- CUSTOMIZED GLOBAL RI TRIGGER DISAPPEARS WHEN ATTACHED
66- %TABLENAME MACRO NOT EXPANDING IF NO SPACE BEFORE END QUOTE
67- MACROS NOT EXPANDING IN STORED PROCEDURES/TRIGGERS
68- %TABLEPROP MACRO NOT EXPANDING
69- DB2/UDB6 INCORRECT SYNTAX FOR CREATE NODEGROUP
70- RE PARSE ERROR ON CLOB/SBCS DATA OR FOR MIXED DATA PHRASE
71- %RELPHYSPROP MACRO NOT EXPANDING PROPERLY
72- PHYSICAL PROPERTIES LOST ON SPLIT MODEL
73- RE PARSE ERROR ON ERWIN 3.5.2 GENERATED SCRIPT
75- SQL SERVER 7 FE - DATATYPE SHOWN INSTEAD OF DOMAIN
76- IDENTITY VALUE MODIFIED ON CONVERSION FROM 3.5.2
77- COLUMN ORDER DIFFERS AFTER REVERSE ENGINEER
78- DOMAIN MIGRATION NOT WORKING PROPERLY
79- CC OF STORED PROCS FOR SQL SERVER 7 NOT RECOGNIZING ALL
80- CONVERTING 3.5.2 MODEL TO 4.0 CHANGES DATATYPES OF DOMAINS
81- PREFIX DUPLICATED ON DERIVE MODEL
82- UNABLE TO CHANGE COLUMN ORDER WHEN IN PHYSICAL ORDER DISPLAY
83- UNABLE TO DELETE COLUMN FROM DB AFTER COMPLETE COMPARE
84- COLUMN ORDER CHANGES CONVERTING 3.5.2 MODEL TO 4.0
85- COLUMN ORDER CHANGES CONVERTING 3.5.2 MODEL TO 4.0
86- SQL SERVER 7 STATISTICAL INDEXES SHOWN BY CC AND RE
87- RE FROM ORACLE 8 NOT RETURNING NUMBER DATA TYPE TABLE PARTS
88- SYNC W/MODEL SOURCE SHOWS DIFFERENCES WHEN NO CHANGES
89- COLUMN DEFAULTS NOT UNIQUELY NAMED ON FORWARD ENGINEERING
90- CC DIFFERENCES CHANGE WHEN GOING BACK AND RESTARTING
91- FUNCTION BASED INDEXES NOT REVERSE ENGINEERED FROM ORACLE
92- INFER RELATIONSHIPS ON RE FROM SCRIPT NOT WORKING
93- GPF SAVING AS 3.5.2 FILE
94- GPF OPENING 3.5.2 MODEL FOR ORACLE DATABASE
95- INFER PRIMARY KEYS NOT GENERATING KEY FOR DB2/390
97- CC REPORTS INVALID DIFFERENCE IN SQL SERVER STORED PROCS
98- BITMAP INDEX NOT GENERATED FOR ORACLE DATABASE
99- SAVE AS XML HANGS ON LARGE MODELS
100-CC NOT RETRIEVING DB2 TABLES BASED ON SPECIFIED OWNERS
101-DDL NOT CREATED TO GENERATE FK CONSTRAINTS ON FE
102-SYNC WITH MODEL SOURCE NOT SHOWING COLUMN ORDER DIFFERENCES
103-FK INDEX NAMES CHANGED TO DEFAULT NAME OPENING 3.5.2 MODEL
104-INCORRECT DIFFERENCES SHOWN BY CC FOR ORACLE 8.1.X
105-CC WITH DB NOT DETECTING COL RENAME IN MODEL FROM RE
107-EXPORT OF COLUMN NAME CHANGE NOT GENERATING DDL
109-RELATIONSHIP NAME LOST ON DERIVE/ADD MODEL SOURCE
111-GPF SAVING MODEL AS 3.5.2 USING ODBC/GENERIC DB
112-FE FOR ORACLE GENERATING CACHE OPTION WHEN NOT SELECTED
113-ORACLE 8I PHYSICAL PROPERTY VALUES NOT RETRIEVED BY CC
114-UNABLE TO CHANGE KEYGROUP TO INDEX NAME MAPPING
115-PARSE ERROR ON DB2 SCRIPT FOR PIECESIZE PARAMETER
116-CC SHOWS DIFFERENCE ON USER DEFINED COLUMN DEFAULTS
117-DIAGRAM DISPLAY CHANGES AFTER SELECTING PRINT
118-GPF GENERATING SCHEMA FOR DB2/390
119-EXPORTING COL ORDER CHANGE TO ORACLE DOES NOT GENERATE DDL
123-GPF ON SAVE AS ERX USING SYBASE MODEL FROM ERWIN 4.0
124-SUBTYPE KEYS LOST ON SAVE AS 3.5.2 OPENING 3.5.2 MODEL
125-POOR PERFORMANCE ON DRAG & DROP OF COLUMNS BETWEEN TABLES
126-CC OF MODEL SAVED AS 3.5.2 GIVES PROPERTY NOT DEFINED ERROR
127-GPF REOPENING MODEL AFTER SAVE AS 3.5.2
128-UNABLE TO SAVE ENTITY/TABLE COMMENT CHANGES FROM DATA BROWSE
129-GPF OPENING LARGE 3.5.2 MODELS CREATED FROM RE ON AS/400
130-CC MODEL TO MODEL NOT DETECTING DIFFERENCES
131-CARDINALITY DISPLAYS FOR SUBTYPE RELATIONSHIP IN IDEF1X
132-GPF IN MODEL EXPLORER SELECTING PHYS PROPERTIES FOR TABLE
134-NOT ALL TABLES RETURNED FROM DB ON COMPLETE COMPARE
135-RELATIONSHIP LINES NOT ATTACHED TO ENTITIES
136-SUBTYPE RELATIONSHIP MODIFIED ON OPEN OF 3.5.2 MODEL
137-EXPORTING CHANGES AFTER COMPLETE COMPARE NOT GENERATING DDL
138-FE FOR DB2 VIEW NOT CLOSING SQL STATEMENT WITH ;
139-REVERSE ENGINEER NOT RETRIEVING ORACLE SEQUENCES
140-%TABLENAME MACRO NOT EXPANDING FOR INDEX NAME
141-INDEXES DISAPPEAR AFTER SAVING MODEL CONVERTED FROM 3.5.2
142-RI ACTIONS LOST AFTER SPLIT OF 3.5.2 MODEL
143-COMPLETE COMPARE COMPARING OBJECT NOT SELECTED FOR COMPARE
145-FK CONSTRAINT NAME LOST ON SPLIT OF 3.5.2 MODEL
146-COPY/PASTE OF ENTITY FROM MODEL CHANGES DATATYPE OF COLUMNS
147-PERFORMANCE ON SAVE FROM WIN2000 TO NT NETWORK DRIVE
148-REVERSE ENGINEER NOT DETECTING ORACLE BITMAP INDEX
149-GPF ON SPLIT OF 3.5.2 MODEL
150-GPF IN DATA BROWSER LISTING DATASOURCE NAMES
151-LINK WITH MODEL SOURCE LOST AFTER SYNCHRONIZE UPDATE SOURCE
152-FK LOGICAL ONLY ATTRIBUTE REMOVED WHEN PARENT ATT CHANGED
153-RI TRIGGER FOR SQL SERVER 2000 FAILS ON FE
154-GPF ON DERIVE LOGICAL MODEL FROM ERWIN 3.5.2 MODEL
156-USER DEFINED DATATYPES NOT USED FOR COLUMNS BY FE
157-POSSIBLE FILE ERROR OPENING MODEL SAVED AS 3.5.2 IN 3.5.2
158-SYNC MODEL SOURCE NOT MATCHING TRANSFORMS
159-COMPLETE COMPARE REPORTS DIFFERENCES AFTER IMPORTING CHANGES
160-GPF ON RE OF SYBASE SCRIPT CONTAINING GRANT CLAUSE
161-ROLENAMES AND PK LOST ON TABLE WITH CYCLIC RELATIONSHIP
162-GPF ON OPEN OF 3.5.2 MODEL CREATED FROM SUBJECT AREA
163-DEFAULT VALUES NOT SEEN BY COMPLETE COMPARE
164-RE OF SQL SERVER NOT RETRIEVING INDEX FILEGROUP INFO
165-LOOP THEN GPF ON RE OF SQL SERVER SCRIPT WITH VIEWS
167-NULL OPTION NOT SHOWN PROPERLY BY COMPLETE COMPARE
168-UNABLE TO IMPORT ERX FILE INTO 3.5.2
169-REL NOT GENERATED IN DDL WHEN THERE IS LOGICAL ONLY ATT
170-SET IDENTITY NOT GENERATING EXPORTING FROM CC
171-COMPLETE COMPARE SHOWING INVALID DIFFERENCES FOR SQL SERVER
172-GPF SELECTING NAMING STANDARDS FILE
173-OPTION SET NOT SAVED FOR COMPLETE COMPARE
174-INVALID DDL GENERATED FOR EXPORT AFTER COMPLETE COMPARE
175-ATTRIBUTE EDITOR NOT REFLECTING CASE OPTION
176-ORACLE PHYS STOR PARMS NOT GENERATED BY FE FOR NON-PK INDEX
178-MISSING GO STATEMENT ON FE FOR SQL SERVER MODELS
179-ATT NAMES 'UNKNOWN' IMPORTING ERX FILE
180-GENERATED SCRIPT FOR FORWARD ENGINEERING IS TRUNCATED
181-BUFFERPOOL OPTION GENERATED FOR ORACLE WHEN NOT SELECTED
182-GPF OPENING 3.5.2 DIMENSIONAL MODEL
183-ALTERNATE KEY NAME INCORRECT IN DISPLAY
184-DB2/390 DOMAIN BLOB DATATYPE GENERATED INCORRECTLY BY FE
185-ATTRIBUTE NOT REMOVED FROM DIAGRAM WHEN DELETED FROM ME
186-OWNER NOT DISPLAYED IN S/A EDITOR
187-COMPLETE COMPARE WITH DB - IMPORT NOT CREATING NEW COLUMNS
189-DEFAULT FONTS/COLORS ENTITY BOX FILL CHANGE NOT APPLYING
190-RENAME OF ATT AFTER COPY/PASTE DOES NOT CHANGE COL NAME
191-SYNC MODEL SOURCE NOT IMPORTING/EXPORTING ALL INFO
192-SYNC MODEL SOURCE NOT MATCHING OBJECTS PROPERLY
193-UNABLE TO DELETE ORACLE TABLE PARTITIONS FROM EXPLORER
194-DUPLICATE ATTRIBUTE CREATED IN GRANDCHILD TABLE
195-DBSYNC NOT INVOKING CC ON SQL SERVER FILEGROUP EDITOR
196-UNABLE TO REPLACE CA LOGO IN RTB GENERATED REPORT
197-WRAP TEXT OUTPUT IN RTB GENERATED HTML REPORTS
198-UDP VALUES LOST SAVING MODEL AS 3.5.2

To read the detail for any/all of the solutions, use one of the following methods:

* Review the SP2 Solutions.txt file which can be found in the \Doc folder or here.

* Go to the Computer Associates web site at [открыть ссылку]

* Go to STAR-TCC and choose Technical Information - Search STAR TCC Knowledge Base - simple. Select ERWIN as the product and use SP002 as the keyword to search, which will result in a list of all the solutions provided in this Service Pack.


---------------------------------------------------------------
2.D. ERwin API
---------------------------------------------------------------
The API provides support for the stand-alone mode in SP2 and is limited to 4.0 models only. The API continues to be enhanced.

Documentation for the ERwin API is provided in the Doc directory in the file ERwin ScriptClientAPI.pdf. Additional notes on the API can be found in the file ReadMeAPI.txt found in the same directory.

------------------------------------------------------------
3. Contacting Computer Associates Technical Support
------------------------------------------------------------

If you need technical support, you can visit the Computer Associates Technical Support web site at [открыть ссылку]

* For online support, select "Star TCC" from the "Support Resources" list.

* For telephone support, select "Calling CA for Support" from the "Support Services" list and find the telephone number for your calling area.

When you contact Computer Associates Technical Support, please have the following information ready for the support analyst:

* The version number and the build number of the product (available from the About menu option on the Help menu).

* The operating system or platform (for example, Windows NT 4.0), as well as any service pack applied.

* A description of the problem, the steps that led to the problem, and any error messages.

Thank you for using Computer Associates products.
Ответить на сообщение »
 

Добавить сообщение »

 Распечатать »
 Правила публикации »
   
 Рекомендовать »  
 

Магазин программного обеспечения   WWW.ITSHOP.RU
erwin Data Modeler Navigator Edition r9.7 - Product plus 1 Year Enterprise Maintenance Commercial
erwin Data Modeler Workgroup Edition r9.7 - Product plus 1 Year Enterprise Maintenance Commercial
erwin Data Modeler Standard Edition r9.7 - Product plus 1 Year Enterprise Maintenance Commercial
Kerio Connect - Server (incl 5 users, 1 yr SWM)
IBM Domino Messaging Server Processor Value Unit (PVU) License + SW Subscription & Support 12 Months
 
Другие предложения...
 
Курсы обучения   WWW.ITSHOP.RU
 
Другие предложения...
 
Магазин сертификационных экзаменов   WWW.ITSHOP.RU
 
Другие предложения...
 
3D Принтеры | 3D Печать   WWW.ITSHOP.RU
 
Другие предложения...
 
Новости по теме
 
Рассылки Subscribe.ru
Информационные технологии: CASE, RAD, ERP, OLAP
Безопасность компьютерных сетей и защита информации
Новости ITShop.ru - ПО, книги, документация, курсы обучения
CASE-технологии
Программирование на Microsoft Access
Мир OLAP и Business Intelligence: новости, статьи, обзоры
3D и виртуальная реальность. Все о Macromedia Flash MX.
 
Статьи по теме
 
Новинки каталога Download
 
Исходники
 
Документация
 
Обсуждения в форумах
Русификация рамки IDEF0 BPWin4 (41)
Возможно ли русифицировать рамку диаграмм в BPWin4?
 
Проектирование курсовой работы в BPWin (32)
Здравствуйте.Подскажите пожалуйста где можно найти примерное проектирование курсовой работы...
 
Русификация ERWin (29)
Здравствуйте! Используем версию ERwin 4.1 в сети,но при создании логической модели вместо...
 
применение CA Process Modeller (BPWin) и связь моделей BPWin и ErWin (1)
Не очень понятна связь прогр продуктов CA Process Modeller (BPWin) и CA Data Modeller...
 
Erwin 3.5.2 (6)
Где скачать или кто может поделиться прогой Erwin 3.5.2? И как открыть файл из 3.5.2 в Erwin...
 
 
 



    
rambler's top100 Rambler's Top100