Исправления, внесенные в новую версию ERwin, доступную на нашем FTP:
Solution#: 216 PRINTING TO A PLOTTER WITH SP1
Problem: Individuals using Patch 1 (build 1338) or SP1 (build 1511) may have problems printing to HP 750C plotters. The symptoms are that the when you hit the Print button within ERwin, the diagram reformat's itself so the relationship lines and positioning of the entities/tables change drastically.
Solution: This problem is being examined for Service Pack 2, but for the time being a workaround is as follows:
Go to the Printers section in the Windows Control Panel. Right Mouse Click on the Printer Icon, and choose the Ports tab. Change the Port from the normally designated printer to File.
Go back to ERwin and Print your diagram. Instead of printing to your printer, you will be prompted for a file name which can be anything (e.g. c:\deleteme.prn). From a Command Prompt, run the following command using the file and the plotter path: C:\WINDOWS>copy c:\deleteme.prn \\usprde00\qaplotter 1 file(s) copied
Your diagram will printed with the correct object positioning.
Solution#: 220 ONLY FIRST COLUMN CONSTRAINT IS CREATED ON FORWARD ENGINEER
All of the column constraints are not forward generated.
Solution#: 221 SYBASE REVERSE ENGINEER ERROR ON RULE
When reverse engineering via script for a Sybase 11.x production script, the parser rejects a RULE containing a negative decimal constant. Name length is incorrectly flagged in excess of 30 characters because ERwin incorrectly includes owner name in length calculation.
Solution#: 222 PARSE ERRORS REVERSE ENGINEERING SQL SERVER 7.0 SCRIPT
Parse error on token 'NLL' when reverse engineering a SQL Server 7.0 script Parse error on token WITH NOCHECK on ALTER TABLE ADD PRIMARY KEY construct. There appears to be no place in Physical Properties for a table PK index for this item.
Solution#: 223 PARSER NOT HANDLING NO ACTION CLAUSE IN DDL FOR SQL SERVER
On reverse engineering, the parser accepts the NO ACTION clause, but the metadata is being generated establishing the default of RESTRICT.
Solution#: 224 FE DB/2 390 WITH INDEX PARTITIONING NOT GENERATING PROPERLY
When forward engineering a 390 design with index partitioning information, ERwin is not always generating the parameters with the required values properly.
Solution#: 225 RE DB2/UDB SCRIPT NOT RECOGNIZING STORAGE AMOUNT WITH SPACE
Reverse engineering from DB2 UDB6 script, bufferpool storage was not checked in the editor Also, bufferpool specified as <integer><space><K> is not recognized by the parser as a valid statement.
Any parameter that specifies a storage size will not parse if there is imbedded spaces between the size and measurement (eg. 2048 M)
Solution#: 226 CC OF 2 LOGICAL MODELS NOT ALLOWING FOR REQUIRED FIELD
Comparing 2 models at the logical level. The resolve differences dialog does not allow for required/not required field.
Solution#: 227 TEXT BOXES NOT DISPLAYED IN SA AFTER OPENING 3.5.2 MODEL
Text boxes are not showing up in every subject area when a model is converted from 3.5.2 to 4.0.
Solution#: 228 ENTITIES/RELATIONSHIP LINES MOVE AFTER DERIVE MODEL
Did derive of logical model to physical model, and entities/tables and relationship lines are completely rearranged in the new model.
Solution#: 229 REVERSE CAN NOT BE UNSELECTED FOR ORACLE INDEXES
For Oracle indexes, the NOSORT and REVERSE options are mutually exclusive, but neither needs to be specified. ERwin will insert the REVERSE parameter when forward engineering if NOSORT is not selected. There is no way to not have REVERSE specified.
Solution#: 230 PROBLEMS PRINTING CONVERTED 3.5.2 MODELS TO PLOTTER
Attempting to print converted 3.5.2 model to plotter with large paper size is not printing properly.
ALso, entity icons and relationship lines are not being printed.
Solution#: 231 ENTITY BOXES GROW LARGER WHEN SELECTING AND MOVING
Selecting all in a subject area and attempting to move the objects will not move the objects far if moving the mouse quickly and entity boxes also grow larger and move further apart.
Solution#: 232 INDEX PARTITIONS LOST AFTER REVERSE ENGINEER
Reverse engineering for DB2 where there exists indexes using partitions is losing all partition information after the 64th partition.
Solution#: 233 TABLESPACE PARTITION INFORMATION NOT RETURNED BY RE
Reverse engineer from a DB2 database, Tablespaces are returned as being a simple non-partitioned Tablespace even though it uses partitions.
Solution#: 234 CC WITH DB2 NOT RETRIEVING ALL INFO FOR INDEX PARTITIONS
Complete Compares of DB2 model to the database, the resulting database physical property values appear as missing in the Resolve Differences Dialog.
Solution#: 235 COLUMNS LOST ON CONVERSION OF 3.5.2 TO 4.0
On converting ERwin 3.5.2 model to ERwin 4.0, columns are lost if the 3.5.2 model had a table containing duplicate column names. The lost columns occur in tables that are child tables of the table with duplicate column names, where the columns were migrated by the relationship. The child table will show only 1 of the duplicate named columns.
Solution#: 236 PARSE ERROR ON DB2 390 SCRIPT FOR VIEW
Reverse engineer for DB2 390 V6 script rejects statement for VIEW definition where view definition contains an expression.
Solution#: 237 TERADATA FORMAT INFORMATION FOR COLUMNS LOST ON SAVE
When creating a new Teradata format in the column editor for a particular column and you save the model, close and reopen it, the format information is not restored.
Solution#: 238 FOREIGN KEY ATTRIBUTES NOT RECOGNIZED WHEN ADDING WITH API
Adding relationships and subsequently changing properties of foreign keys KEY GROUP, KEY GROUP MEMBER are not recognized.
The cause of behavior is a result of ERwin failing to set dirty bit flag that reflects presents of changes in model data during ERwin API session. setting of the DirtyBit property via IPersistenceUnit interface before closing a session forces migration of attributes and creating FKs.
Solution#: 239 TROUBLE CREATING POLYGON SEGMENTS OPENING A 3.5.2 MODEL
Sometimes there is a problem with creating a polygon segement when using a converted ERwin 3.5.2 model. Problems occur trying to create the first segment of the polygon. THis is an intermittent problem.
Solution#: 240 UNABLE TO DELETE USER DEFINED DOMAIN IN DOMAIN DICTIONARY
Unable to delete a user defined domain using the domain dictionary and selecting the Delete button. This occurs after saving and opening the model again.
The domain can be deleted from the model explorer.
Solution#: 241 IGNORE DUP KEY CHECKBOX SETTING NOT SAVED
With Sybase 11.x as the selected database, in the Index Editor for any table if you check the Ignore Dup Key checkbox and then switch to any other tab in the Editor, ERwin unchecks it. The only time it keeps it checked is when you click OK.
Solution#: 242 OBJECTS DISAPPEAR FROM DISPLAY AFTER PRINTING
One of the PKs goes away after sending the diagram to the printer. Closing the diagram and reopening restored the primary keys. Appears to be a display problem after printing.
Solution#: 243 VIEW DEFINITION CORRUPTED BY REVERSE ENGINEERING FROM SCRIPT
Reverse engineering a SYBASE 11.x design from script may corrupt user defined view definitions.
Solution#: 244 CUSTOM COLORS NOT SAVED IN MODEL
Able to create a custom color and apply the color to assigned entities and the model is saved, once the application is closed and the model is reopened, the custom color that was created is not there.
Solution#: 245 DOMAIN NAME INHERITED BY COLUMN CHANGES ON COPY/PASTE
In the Domain Dictionary(Physical) the macro for Name Inherited by Column is changed from %AttName to %ColDomain when copy/paste of an entity containing an attribute with the domain.
Solution#: 246 SLOW PERFORMANCE WORKING WITH CONVERTED 3.5.2 MODELS
Slow performance when switching between logical/physical model or between subject areas, when importing a 3.5.2 model to 4.0
Problems with performance also occur when opening the converted models on machines with 128MB and less memory.
Solution#: 247 COMPLETE COMPARE SHOWS WRONG DIFFERENCES FOR ORACLE PK INDEX
Problem with Complete Compare showing differences for Oracle PK indexes and PK constraints, having wrong information on db side.
Solution#: 248 GPF OR HANG OPENING XML FILE
ERwin either crashes or hangs when opening XML file.
Solution#: 249 UNABLE TO DEFINE BIGINT AS IDENTITY COL IN SQL SERVER 2000
Column datatype bigint can not be declared as an Identity column. SQL Server 2000 database can define bigint as Indentity.
Solution#: 250 DIAGRAM INFORMATION FROM 3.5.2 MODEL NOT SAVED IN 4.0
Opening a ERwin 3.5.2 model in ERwin 4.0 does not retain the diagram information from the 3.5.2 model such as Diagram Name, Author and Definition
DImensional property is also not carried over into ERwin 4.0 model.
Solution#: 251 DATA BROWSER REPORTS INCORRECT
Some standard Data Browser reports are not returning proper information based on the report. For example, the Table/Column report only returns the table names and not the column names within each table. The selection criteria for the report is missing the column name.
Solution#: 252 INCORRECT PHYSICAL DATATYPE FOR LOGICAL DATATYPE
In a Logical/Physical model, selecting CHAR as the logical datatype will result in the physical datatype to be an integer datatype, such as tinyint for SQL Server.
Importing column datatype changes can also cause this to occur.
Solution#: 253 RE OF DB2 SUMMARY TABLE REFRESH SPECIFICATION INCORRECT
For DB2 UDB v6 designs, reverse engineering seems to be altering Summary Table specifications of REFRESH IMMEDIATE to REFRESH DEFERRED.
Solution#: 254 DB2 SUMMARY TABLES IMPORTS AS USER-DEFINED THEN DISAPPEARS
For DB2 UDB v6 designs, reverse engineering seems to be altering a Summary Table specification of the form (Select * from <table>). The table shows as user-defined, then it appears to disappear when attempting to forward engineer the model.
Solution#: 255 PERFORMANCE PROBLEMS ON DIMENSIONAL MODELS
When properties of a model are changed to dimensional, performance of ERwin is impacted.
Solution#: 256 DATA BROWSER FIND IN RESULT SET NOT WORKING CORRECTLY
In the Data Browser for ERwin 4.0, if you do a search in the 'Find in Result Set' window. The instructions on how to do search on 'String expressions' does not work properly for ERwin 4.0. The instructions work for ERwin 3.5.2 properly.
Solution#: 257 FE FOR DB2 FAILS WHEN IN PHYSICAL ORDER VIEW
When forward engineering a model for DB2/390 5 the Index order and the alter table order do not match. Therefore it is rejected by the database. The order is switched around because of the view of the diagram is in, Physical Order view, and Column view.
Solution#: 258 RE NOT GETTING SYBASE NONCLUSTERED PRIMARY KEY
For a Sybase 11.9.2 design, reverse engineering is not picking up a nonclustered primary key definition.
Also, CLUSTERED is assigned to a primary key definition without an explicit clustering specification
Solution#: 259 DERIVE MODEL NOT COPYING ENTITY DEF TO TABLE COMMENT
Entity definition is not being copied to Table comment when deriving a physical model from a logical model. Attribute definitions are being copied to Column comments.
Solution#: 260 MOVING GROUPED OBJECTS RESIZES THEM
In a logical/physical model, grouping objects on the logical side, then switching to physical side and moving the group will distort the objects. They are resized and in some cases can not be seen.
Solution#: 261 PERFORMANCE ON ZOOM IN/OUT OF DIAGRAM
THe performance of the Zoom in/Zoom out function is very slow Takes about 10 to 20 seconds approx for the issue with a client model i.e. 11 094623 - but after reading comments fom issue seems took 1 to 2 minutes - thu s seems to have got better.
Solution#: 262 LOGICAL COL NAME INCORRECT AFTER IMPORT FROM CC PHYS LEVEL
Logical attribute name is set to the domain name after import from Complete compare. The compare is a model level compare between 2 models, using the physical compare.
Solution#: 263 FK NOT GENERATED ON IMPORT OF RELATIONSHIP
Import of child relationship after complete compare is not generating the foreign key in the child table.
Solution#: 264 EXPORTING INDEX CHANGES AFTER CC NOT GENERATING DDL
No DDL is generated when exporting changes to indexes after Complete Compare. An example is changing the order of an alternate key index.
Solution#: 265 EXPORT OF DELETION FAILS AFTER MODEL-MODEL COMPARE
Attempting to export deletions in a model after model to model compare is not updating the model exported to. Examples are deleting of domains and relationships.
Solution#: 266 CC MODEL/PHYSICAL LEVEL SHOWS LOGICAL NAMES
Complete compare or 2 models using model level/physical level compare will display logical names in the resolve differences dialog on the right side model.
Solution#: 267 IMPORT OF DATATYPE INCORRECT AFTER MODEL LEVEL COMPARE
Performing an import of columns after a model level complete compare will set the datatype of the column imported to the default datatype for the database.
Solution#: 268 COLUMNS MISSING FROM DIAGRAM ON CONVERSION FROM 3.5.2
On converting a diagram from ERwin 3.5.2 to ERwin 4.0, some columns may be lost from the diagram in the physical side of the model. This is due to the corresponding attribute on the logical side having the logical only property set.
Solution#: 269 FK PROPERTY LOST ON DERIVE OF 3.5.2 MODEL WITH SUBTYPE REL
Upon conversion of a ERwin 3.5.2 model to ERwin 4.0 containing subtype relationships, the 4.0 model looks fine. Deriving a new logical model from the converted model results in the FK attributes of the child tables of the subtype relationship to lose the FK designation and the attributes become owned attributes of the child tables.
Solution#: 270 DIFFICULT TO CAPTURE RELATIONSHIP LINES
Selecting relationship lines are not captured easily.
Solution#: 271 COPY/PASTE LOSING TABLES WHEN USING 3.5.2 MODEL
Copy/Paste of tables created in ERwin 3.5.2 are being dropped when when opened in 4.0 and attempting to copy/paste into a new model after selecting all objects.
Solution#: 272 COLUMNS ASSOCIATED WITH ORACLE TRIGGER NOT RETURNED BY RE
For Oracle 8 triggers, reverse engineering is not returning the column information for the trigger. That is, the columns of the table that the trigger is based on are not retrieved. So the trigger is not generated correctly on reverse engineer.
Solution#: 273 PROGRESS ACTIVE INDEX SETTING DROPPED ON CONVERSION
Progress indexes marked as Active in a 3.5.2 model are not set as active when opened in ERwin 4.0. The setting is being dropped.
Solution#: 274 PROGRESS COLUMN FORMAT INFO NOT SAVED
Display formats for Progress are missing when opening a 3.5.2 model in ERwin 4.0. Also, after setting formats in 4.0, the settings do not appear to be saved but forward engineer will create them.
Solution#: 275 DATATYPE MAPPING NOT FUNCTIONING ON DERIVE MODEL
Deriving physical model from logical with attached datatype standards model is not mapping the logical datatypes to the physical counterparts. The datatypes in the physical model is the logical datatype.
Solution#: 276 RE PARSING SCRIPT REJECTS LOB TABLESPACE FOR DB2
Reverse engineering a DB2/390 V6 script, the parser is rejecting a LOB tablespace .
Solution#: 277 EXPORT TO EXCEL USING DDE WILL TRUNCATE DATA OVER 256 CHARS
Exporting of data from the Data Browser or Report Template Builder using DDE to Microsoft Excel may truncate data. This is due to a limitation with Excel and DDE that will only export up to 256 characters of data per column into Excel.
This is not a restriction with Microsoft Word.
Solution#: 278 RE FROM ORACLE ALTERS COLUMN ID IF >256 COLUMNS IN TABLE
Reverse engineer of tables from Oracle that contain more than 256 columns will have incorrect column ids assigned. The columns after column 256 will be assigned column ids starting with 1 again. This will cause incorrect column order when forward engineering from the model.
Solution#: 279 GPF PERFORMING ROLLUP TRANSFORM IF CYCLIC REL ON CHILD
When using a transform to roll up a subtype relationship, ERwin crashes. This occurs when the child table contains a self referencing relationship.
Solution#: 280 GPF OPENING 3.5.2 ORACLE MODEL CONTAINING PARTITIONS
When opening an ERwin 3.5.2 file for an Oracle database containing Oracle partition information, ERwin will crash.
Crash does not occur with GA (1298) and Patch1 (1338)
Solution#: 281 SUPPORT FILE TYPE OF .DDL FOR REVERSE ENGINEERING
Allow ERwin to process files with a filetype of .DDL to be an SQL script file. Reverse Engineering/Complete Compare will only supports filetypes of .ERS and .SQL for script files.
Solution#: 282 CLOSE YES NOT GENERATED FOR DB2 TABLESPACE WHEN CHECKED
Tablespaces defined in DB2 model which have CLOSE box checked are generating CLOSE NO when forward engineering.
Solution#: 283 PERFORMANCE ON REVERSE ENGINEERING FROM SCRIPT
Performance for reverse engineering from a script file is slow for large scripts.
Solution#: 284 PAGESIZE VALUES OF 16K, 32K NOT ALLOWED IN EDITORS FOR DB2
Allow for values of 16K and 32K for Tablespace and Bufferpool Pagesize parameters for DB2.
Solution#: 285 CC NOT DETECTING DIFFERENCE IN RI ACTIONS
CHanges to RI actions are not detected by Complete Compare. This occurs with model to model compare, using both Model Level - Physical and Database Level compares. Model Level - Logical will detect the difference.
Solution#: 286 POPUP REPORTS NOT GENERATED BY RTB
Popup reports are not being generated by the Report Template Builder. This occurs when the report is generated when the model is displaying the opposite side from what the report was created under. For example, if the report was created when the physical side of the model is displayed, running the report while the logical side is displayed will not produce popup reports.
This problem only occurs when the physical table name does not match the logical entity name.
Identical reports need to be generated for both Logical and Physical side, selecting report based on which side of the model is displayed at the time.
Solution#: 287 TABLE TRIGGER CODE DISAPPEARS FROM EDITOR
Creating a table trigger, the code no longer shows in the editor when it is reopened. Forward engineering of the model will generate the trigger.
The trigger type (insert, update, delete) needs to be selected on the General tab for the trigger editor before selecting OK to generate the trigger. The trigger code will then be viewable each time the editor is opened.
Solution#: 288 INVALID DIFFERENCES REPORTED BY COMPLETE COMPARE FOR DB2/390
Complete COmpare for DB2/390 is reporting various differences in model to database which do not exist. 1. RE database seems to be ignoring or garbling the tablespace partitioning info. In the captured metadata, I see only simple tablespaces. If you inspect the FEed script, you will find some strange syntax - the 97s you see is the number of partitions in the tablespaces.
2. Table-column order shows different for every column in every table. It appears to me ERwin RE the database using the colno from the DB2 catalog. For a table containing <n> columns, these are numbered 1, 2, 3, ... <n>. ERwin seems to number columns from the compared script as 0, 1, 2, ... <(n-1)>. You can see this in the compare report.
3. Each RE database table has a bogus Rule attached to it. This was noted with issue #10558120, previously submitted. You can see this in the FE script.
4. Table column mismatch for Default when they both are NOT NULL WITH ЭsystemЁ DEFAULT. I've seen this before, but don't remember reporting it. I still don't know why ERwin doesn't name this particular Default as 'System_Generated' as it did with 352sp3. You can see this in the CC report - the RE database Default is named DEFAULT_172 and the script as DEFAULT_171 .
5. RE database seems to be ignoring index partition values. It seems to suc k up the partition number and using info properly, but it misses the values.
6. All view columns mis-match. RE of database seems to populate the Domain Parent with the column name and not populate the expression. Script import does the reverse.
Other invalid differences occur for storage groups, tables and blob domain. For storage groups and Tables differences appear when it appears that properties are not recognized as being in the model generated from the script file.
Solution#: 289 TEXT IN TEXT BOXES GETS CLIPPED WHEN PRINTING
Text contained in a text box object gets clipped when the model is printed or creating a PDF file from the model.
Solution#: 290 OWNER NOT ATTACHED TO INFORMIX PK OR FK CONSTRAINT
Owner is not attached to Informix primary key or foreign key constraint on forward engineering.
Solution#: 291 ORACLE TABLESPACE GENERATION FAILS WHEN NO LOGGING CHECKED
Selecting the NO LOGGING option for a Tablespace in Oracle will generate invalid DDL statements. The EXCLUSIVE parameter is added to the CREATE TABLESPACE statement, which is invalid and causes an error during the forward engineer.
Solution#: 292 PRINTING HTML PICTURE REPORT TRUNCATES DIAGRAM ON RIGHT
Printing out picture report generated by Report Template Builder, the report is truncated on the right side. This occurs printing in both landscape and portrait modes from Internet Explorer.
This is a limitation of the browser, which will only print a single page width. Anything wider than one page will be truncated.
Solution#: 293 RTB PICTURE REPOR TO HTML - MAIN SUBJECT AREA IS BLANK
When export to HTML, main subject area is blank. Other subject area will display fine.
Generating jpg images is a memory intensive process, large diagrams may not be able to generate an image. ERwin will display an error message if it is unable to generate the jpg file due to memory limitations.
Solution#: 294 GPF ON IMPORT OF CHANGES FOLLWING COMPLETE COMPARE
Importing changes from Complete Compare into the model may cause ERwin to crash.
Solution#: 295 UNABLE TO RESIZE ENTITIES IN STORED DISPLAY
Stored Display is not allowing entity to resize. Unable to get the resize box to show for entities.
Problem is that the allow manual resize option is not set. This can be set by going to the menu item Format/Preferences, Layout tab and select the Allow Manual Resize box for Entities.
Solution#: 296 RTB/DATA BROWSER - DOUBLE BYTE CHARACTER PROBLEMS
When choosing 'RTF' for export format, the report created by RTB in MS Word has broken Korean characters.
Need to use specific language fonts for the language used by the operating system.
Solution#: 297 EDITING RTF CREATED BY RTB WILL CORRUPT REPORT
Modifying an RTF file generated by an RTB report with contains a picture section and other sections will corrupt the file. As an example, stretch the picture in the picture section and save the file. Opening the file will alter the section and table headings.
Need to save file as a .doc file prior to editing.
Solution#: 298 UNABLE TO DRAW POLYLINES ON CONVERTED 3.5.2 MODELS
Unable to draw polylines on converted ERwin 3.5.2 models. Nothing happens when you click to set a line to try and create the next line.
Solution#: 299 INVALID SQL SYNTAX FOR VIEW WHEN TABLE FILTER/SA USED
When using table filtering on forward engineering, SQL statements for creating views may be invalid. If a table that the view is based on is filtered out for generation, then the FROM clause will not have the table name included for the CREATE VIEW statement and it will fail.
When creating a subject area and including a view but not the parent table(s), forward engineering from the subject area will create the view but the FROM statement will be missing the tables not included in the subject area.
Solution#: 300 FE NOT GENERATING ALL TABLE PARTITION VALUES
Storage value not generated in script for table partition on forward engineering.
Solution#: 301 CHANGING COL ORDER IN PHYS DISPLAY CHANGES COL ORDER DISPLAY
A change made to the column order in the Physical Order display is reflected in Column Order display although they should be independent.
Solution#: 302 RI TRIGGER FAILS FOR FE FOR INSERT/UPDATE TRIGGERS
Syntax error on forward engineer to database for an ERwin override RI Trigger on Child Table Insert or Child Table Update when SET NULL trigger is used for non-indentifying relationship.
ALso occurs with Parent Table Update trigger.
Solution#: 303 RELATIONSHIP LINES MOVE AFTER PRINT
Relationship lines move on diagram and in printed output after printing. Problem did not exist in GA build 1298 but started occurring with Patch1 build 1338. Print to Screen does not resolve problem. Problem reproduced only on Windows 95 machine.
Solution#: 304 NON-UNIQUE NAME DISALLOWED WHEN ACCEPTING DUPLICATE NAME
With the Duplicate Names option set to ASK, unable to add an attribute into an entity where the attribute name already exists in another entity. By selecting OK, it should allow the name to be used as long as that name is not already defined in the current entity. Selecting the ASK option will validate that the name is unique within the model and allows the choice of using a duplicate name.
The non-unique name disallowed also occurs when adding a duplicate entity name. You should be able to cancel out from the rename to accept the duplicate name when the ASK option is selected. Available in Service Pack 2
Solution#: 305 INDEX COLUMNS IN WRONG ORDER AFTER REVERSE ENGINEER/CC
For a DB2/390 design, reverse engineering from the catalog produces a faulty ordering of index columns. Reverse engineer seems to be using sysibm.syskeys.colno and not sysibm.syskeys.colseq to determine the column order. Colno gives the column's position in the table - not the index. ERwin 3.5.2 is retrieving the correct order.
Solution#: 306 SUBPAGE OPTION ALLOWED AND SET FOR DB2/390 TYPE 2 INDEX
Reverse engineer of DB2/390 script with type 2 indexes will set the subpages flag in the index editor. This is invalid for type 2 indexes. It is also not possible to uncheck this option from the index editor.
Also in the index editor for DB2, the subpage option is enabled for type 2 indexes when it is not valid.
Solution#: 307 DATASOURCE LOST ON SAVE AFTER CREATING NEW SOURCE
Data source mappings are lost on save of model. This occurs when adding a new data source to a column. When doing so, all previous data source mappings for other columns which were present at file open are lost on saving the model.
Solution#: 308 CC WITH DATABASE SHOWS INVALID DIFFERENCES
Complete compare of SQL Server model with database is yielding invalid differences. Also occurs with Oracle and Sybase.
Triggers show as difference as no trigger is displayed on model side. Null option for columns show as different with database side showing blank. Child relationships show as different with database side showing no rels. Domain datatype shows as different for the BLOB domain, image on model side, binary on database side. Valid values also show as difference when they are the same in model and on database. Also Not Nulls are not compared correctly even though the DB and the Model bo th have not null and it still shows up as a difference. Defaults show as difference as they are not displayed on database side.
These problems can occur also on SQL Server databases converted from 6.5 to 7.0.
Solution#: 309 IMPORTING DATASOURCES FROM MODEL NOT WORKING
After Importing data source from another model, looking at the datasources does not show any tables for source member.
Solution#: 310 GPF IN RTB SELECTING PICTURE REPORT FOR SELECTED DATABASES
Using RTB to select picture report will crash when the model is for a SAS or ODBC/Generic database. The crash occurs when creating the report from a physical model or physical side of logical/physical model.
Solution#: 311 GPF IN TABLE EDITOR FOR DIMENSIONAL MODELS
Crash occurs in the table editor for dimensional models after clicking OK to terminate the editor. Only occurs when entering into the table editor from the column editor.
Solution#: 312 DATA BROWSER SELECTION FOR DB NAME REPORTS TABLE NAME
Table DB Name is the same as Table Name in Data Browser's Table Reports. It should be showing the database name for the table in the report. THis is for DB2 database.
In ERwin 4.0, the property to be used in Data Browser for the database and tablespace names is IN_DATABASE and IN_TABLESPACE.
Solution#: 313 DATA BROWSER PHYSICAL OBJECT REPORT SHOWS INCORRECT VALUES
On physical object report the With Restrict On Drop Column will return a blank for NO and a 1 for YES, instead of No or YES as in ERwin 3.5.2 in the data browser report.
Solution#: 314 FE FAILS WHEN OWNER ATTACHED TO INDEX NAME
When forward engineer to SQL Server, if Owner is checked in the options and a table owner is specified, the CREATE INDEX statement generated has the owner name appended to the index name. This causes a syntax error when running the script.
Also occurs for SQL Anywhere and Sybase databases.
Solution#: 315 CC DOES NOT USE DIAGRAM DISPLAY LEVEL FOR RESOLVE DIFFERENCE
Column Order is being used in Complete Compare, even if Physical Order is checked. This results in the resolve differences dialog showing columns in an order different from what is expected.
Solution#: 316 ALL STORGROUPS IMPORTED WHEN RE OF ONLY TABLESPACES FOR DB2
All STORGROUPs are always imported when doing reverse engineer from DB2 and selecting only tablespaces to import.
Solution#: 317 ALIAS/SYNONYM INFORMATION NOT SAVED FROM EDITOR
For a DB2/390 V6 model, ERwin is not saving information entered in the Alias & Synonym Editor. The database name and comment information are not saved, as when you reopen the editor the information is no longer shown.
Also, the checkbox for Synonym lost if checked. THis will cause the database and comment edit boxes to not be grayed out on reopening the editor. Available in Service Pack 2
Solution#: 318 BOGUS PRIMARY KEY INDEX SHOWN IN COMPLETE COMPARE
When an existing ERwin 3.5.2 model for a ORACLE 8 database was converted to ERwin 4 and a complete compare was run then the first table displayed an index on the database side that did not exist in the database. It was given the name XPK<table_name>. This did not exist in either the model or the database
ALso occurs for Sybase model compare to database, where complete compare will match with this Primary Key index which does not exist in database, but also shows the actual named primary key index as not matching the one in the model.
Solution#: 319 UNABLE TO CHANGE DATATYPE ON COL CREATED FROM USER DOMAIN
Datatype can not be changed for column derived from a user defined domain. You can change the datatype after changing the column domain to a default ERwin domain.
Solution#: 320 COLUMN ORDER REVERSED SWITCHING TO PHYSICAL ORDER DISPLAY
Adding columns to a table using the column editor will cause the physical order to be the reverse of the logical order. THis will show on forward engineer when physical order is selected for columns. THis does not occur when using inplace edit on the diagram to add columns.
Solution#: 321 GPF CANCELLING CC WITH DB WHERE VALIDATION RULES ARE PRESENT
Running complete compare with database, a GPF will result when cancelling out of the resolve differences dialog followed by cancelling out of complete compare set options dialog. This occurs when there are validation rules present in the database.
Solution#: 322 ON CHILD UPDATE RESTRICT TRIGGER SYNTAX INCORRECT
ON CHILD UPDATE RESTRICT RI trigger syntax is not correct. It does not allow for a column to be null when inserted.
Solution#: 323 DEFER NO OPTION LOST ON RE FROM SCRIPT FOR DB2
The DEFER NO option on indexes is not generated when forward engineering a data model that was reverse engineered from a script with DEFER NO (DB2 OS390/6). To get DEFER NO, must go into DB2 Indexes screen for EACH index the model and then select and deselect the DEFER option check box.
Solution#: 324 INCORRECT COMMENTS IN DB2 DDL ON EXPORT FROM CC
The format of comments inserted into DDL script generated by Complete Compare are not in a DB2 acceptable format. They should start with a double dash on every line.
Solution#: 325 PKS OMITTED FROM REVERSE ENGINEERING
When reverse engineering under control of the client's DB2_UDB-6.1 template, PKs are not showing up in the resulting model. However, when L1 tried to reproduce the problem, primary keys were processed correctly. Failure to retain the DB2/UDB6.1 setting was suspected; the client believed this setting was silently reverting to DB2/OS390. However, further investigation showed that database version and logical/physical settings were being retained correctly.
Solution#: 326 CC NOT DETECTING CHANGE IN FOREIGN KEY CONSTRAINT NAME
Complete compare does not recognize a change in a foreign key constraint name when using database compare or physical level compare for model to model.
Solution#: 327 IDENTITY START VALUE INCORRECT ON FE FOR DB2
Using IDENTITY with DB2 390/6, when you enter a number for the START WITH command it will be produced incorrectly in the generated code i.e. If you enter 'START WITH 1', the code will produce 'START WITH 11' in the preview screen. Likewise if you enter '100' it will come out as '100100' in the preview screen. The number specified is duplicated in the generated DDL.
Solution#: 328 INCONSISTENCIES WITH DOMAIN NAME PROCESSING
There are some inconsistencies with domain processing between using the Model Explorer and the Domain Dictionary Editor.
- When creating a domain on the logical side and renaming on the physical side using the domain dictionary editor, the name inherited by a column when dragged into a table is the logical domain name instead of the physical domain name.
- Renaming a domain from Model Explorar will rename both the logical and physical name. Changing the name on the physical side should break the link between logical and physical but this is not the case.
- After a domain is dragged into a table it can not be renamed using the domain dictionary editor
DB2 UDB 6.1 domain names are being truncated at 18 characters, when 128 characters are allowed. Column names are truncated at 30 characters when 128 characters are allowed.
ERwin treats domains as user defined datatypes. DB2/UDB 6.1 supports a name length of 18 characters for datatypes.
For column names, DB2/UDB 6.1 supports a name length of 30 characters, 128 for data warehousing. ERwin will allow 128 character name when dimensional modeling is selected as a model property.
Solution#: 330 SUPERTYPE/SUBTYPE REL NOT IMPORTED/EXPORTED BY CC
When using Complete Compare or Sync with Model Source, selecting Supertype/Subtype relationships for import or export does not import/export the symbol or relationships associated with it.
Solution#: 331 GPF ON DATATYPE STANDARDS SWITCHING FROM LOGICAL TO PHYSICAL
Datatype standards editor GPfs when switiching from the logical tab to the physical tab using Oracle.
Solution#: 332 REVERSE AND LOGGING CAN NOT BE REMOVED FROM ORACLE DDL
REVERSE and LOGGING can not be removed from Oracle DDL for indexes.
The user interface has been modified to allow for selection of Redo log, which includes the radio buttons to select LOGGING or NOLOGGING, similar to the user interface for ERwin 3.5.2.
For any ERwin 4.0 models which previously had the NOLOGGING checkbox set then cleared, opening the model in ERwin 4.0 SP2 will show in the user interface with the LOGGING radio button set, with the REDO log checkbox unchecked. This is due to the way the property was stored in ERwin 4.0 SP1 and prior versions. Opening a new model will show the LOGGING and NOLOGGING radio buttons grayed out until the REDO checkbox is set.
Solution#: 333 GPF MOVING KEY GROUP EDITOR ON SCREEN
Opening the key group/index editor from the attribute/column editor and attempting to move the dialog box on the screen will cause ERwin to crash.
Solution#: 334 GPF CANCELLING COMPLETE COMPARE WITH DATABASE
GPF occurs when Complete Comparing against database, selecting owner. Cancel out of resolve differences dialog then cancel out of complete compare will cause ERwin to GPF.