![]() "ESX190817 Partition Expression is only valid on a non-unique primary index." Issues Fixed in this Release In CA ERwin Data Modeler release 7.3.11 and 8.0/8.1, when a Teradata 13 database was reverse engineered, the following error message was displayed: Problem No.: 11528 Issue No.: 20476854-1 TERADATA PARTITION ON UPI If the model size was greater than 63 MB, it could not be saved. In CA ERwin Data Modeler r8.2.5, when a model size was reduced to 63 MB, the model could be saved from ERwin r8 to r7.3.10. Views that included the '+' and '||' symbols were not created and no user-defined SQL was saved. In CA ERwin Data Modeler r7.3.10, when a Teradata view was reverse engineered, there was an error. Problem No.: 11306 Issue No.: 20255846-1 REVERSE ENG OF VIEW TERADATA In CA ERwin Data Modeler r8.2.5, relationship line was invisible on the Logical Side of the Model, but the relationship existed in the diagram. Problem No.: 11562 Issue No.: 21313647-1, LOG RELATIONSHIP LIN INVISIBLE The Diagram Editor had to be opened and the relationship had to be moved from Available to Included area and only then the relationship was displayed in the diagram. In CA ERwin Data Modeler r9, if a subtype entity relationship was right-clicked in the Model Explorer and Add to Diagram was clicked, the relationship was not added to the diagram. Problem No.: 11562 Issue No.: 21565108-1 SUBTYPE SYMBOL * LINES MISSING If the model was reopened, the model was displayed in a much smaller size. In CA ERwin Data Modeler r9, suppose a model was at its maximum zoom size while saving. Problem No.: 12738 Issue No.: 21087957-1 MAXIMISE IGNORED ON OPEN If a relationship was deleted from a diagram using the Delete option in the Subject Area menu option, the relationship was deleted only from the current diagram and not from all the diagrams in the same subject area. If a recursive relationship was added to an entity or a relationship was added between two entities while working on a diagram, the relationship lines did not appear anywhere else in the model across all diagrams and across all subject areas, despite selecting the Auto-populate check box for the subject area. Properties of Themes such as colors of existing attributes did not inherit across Subject Areas. In CA ERwin Data Modeler r8.2.05, foreign key attributes did not inherit color from the parent entity relationship line, if the parent entities were not present in the current subject area. In addition, sometimes when the entity was added, the inherited color appeared and when the entity was removed the color did not appear. The inherited color appeared if the entity was added temporarily. In CA ERwin Data Modeler release 8.0, when attributes inherited colors from entities, in some diagrams the parent entities were not present and the child attributes did not inherit the color. Problem No.: 12373 Issue No.: 21343241-1 IHHERT COLOR BROKEN ![]() The following issues are fixed in release ERwin Data Modeler r9.5.2 Storage Performance and Utilization Managementĭescription: What Problems/Issues are fixed in releases ERwin 9.5.2, 9.5.1, 9.5.0, (more to come).Information Archiving & Storage Management.Hybrid Active Directory Security and Governance.Starling Identity Analytics & Risk Intelligence.One Identity Safeguard for Privileged Passwords. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |