Previous Topic: Error While Creating a Profie Using Special Characters in Mart AdministratorNext Topic: Documentation


Fixed Issues

This section includes the list of issues that is fixed.

This section contains the following topics

Issues Fixed in this Release

Issues Fixed in this Release

The following issues have been fixed in this release:

  1. Problem No.: Issue No.:509333: - erwin Data Modeler crashes on offline saved model

    With Mart Server connected, save a modified model offline. Reopening this model causes erwin Data Modeler to crash immediately.

  2. Problem No.: Issue No.:475771: - Index Partition boundaries not converted from V7 Model

    When converting a DB2 model from V7.3 to R8 or R9 any boundaries set in the V7.x model for Index Partitions are lost.

  3. Problem No.: Issue No.:463359: - Physical only domains copied to table (as column) show up as attribute in Entity

    Physical only domain(s) copied to Table, become a column. When we switch to the logical side, they show up as attributes in the Entity.

  4. Problem No.: Issue No.:497738: - Reverse engineer IBM DB2/LUW 9.x, some columns default value “WITH DEFAULT” and datatypes like DECIMAL, INTEGER, DATE, TIMESTAMP reverse engineered as DEFAULT 0, DEFAULT 0.0

    Customer expects to see B2B_QT_ID INTEGER NOT NULL WITH DEFAULT. But erwin Data Modeler displays B2B_QT_ID INTEGER NOT NULL DEFAULT 0.

  5. Problem No.: Issue No.:487154: - Selection of columns hangs in a table with 300 to 400 columns

    Opening a customer's model with large table of more than 948 columns and performing any operations on columns causes erwin Data Modeler to freeze.

  6. Problem No.: Issue No.:487891: - Model gets stuck at the bottom of the screen and cannot be move to any position

    Model gets stuck at the bottom of the screen and cannot be move to any position.

  7. Problem No.: Issue No.:415928: - DB2 LUW 10.x data model, domain with default not retaining the value for a new column

    Domain with default does not retaining the value for a new column

  8. Problem No.: Issue No.:507209: - MIMB log application error

    MIMB log application error when export to Excel

  9. Problem No.: Issue No.:5803: - Alter script - table rename invalidates foreign key constraints

    Alter script - table rename invalidates foreign key constraints

  10. Problem No.: Issue No.:00515545: - OpenSSL patch for 9.6 and 9.64

    OpenSSL higher version is not supported with erwin Data Modeler

  11. Problem No.: Issue No.:00517494: - Teradata Varchar compression is not supported

    For Teradata, 13.10 and later 'Compress' is allowed for Variable data types e.g. VARCHAR(). erwin Data Modeler allows 'Compress' for other other data types but does not allow it for VARCHAR() with the error 'ESX-190833: The Compress property is not compatible with a UDT, LOB, or a variable length Datatype.'

  12. Problem No.: Issue No.:486910/00317985: - Previous Hotfixes not included in 9.64.02

    Hotfix-dll's for various issues were not included in 9.64.02.

  13. Problem No.: Issue No.:00593470: - Model stored in the mart cannot be opened

    A model stored in the mart cannot be opened and causes erwin Data Modeler to crash.

  14. Problem No.: Issue No.:00438788: - SQL Server "go" batch submission command in stored procedure source code error

    SQL Server "go" batch statement in a stored procedure returns errors.

  15. Problem No.: Issue No.:5911: - Model specific, switch from Physical to Logical 1-2x and erwin Data Modeler r9.6.4.2 crashes

    erwin Data Modeler 96.4.2 crashes due to null pointer access violation.

  16. Problem No.: Issue No.:5883: - Reverse Engineer the Index with Partition clause for DB2 z/OS 10.x fails

    Reverse Engineering the Index with Partition clause for DB2 z/OS 10.x fails.

  17. Problem No.: Issue No.:5316: - Bulk editor selection does not persist

    Multiple selections in the Bulk Editor do not persist.

  18. Problem No.: Issue No.:00458337: - Generic ODBC 3.0 Datatype Standards not mappings

    Changes made in the database standards are not applied to the logical to physical mapping due to improper ODBC version mappings.

  19. Problem No.: Issue No.:00515936: - DB2 z/OS Index Partitions lost on RE ­ need fix for 9.64.1 ­ 64­bit

    DB2 z/OS Index Partitions are lost on reverse engineering.

  20. Problem No.: Issue No.:00581722: - CCAC Administrative Campus #2 - Table Filter not working for RE. Target DBMS is SQL Server 2008-9.64.02

    Table Filter is not working for RE. Target DBMS is SQL Server 2008.