IBM Support

JR44666: LOGICAL TO PHYSICAL DATA MODEL TRANSFORMATION OF A ROLL UP/DOWNR ELATIONSHIP MAY PRODUCE INDEXES ON COLUMNS WITH NO DATA TYPE.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If a logical data model contains two entities connected with a
    relationship which transformation option is set to ?quot;roll
    up?quot; or ?quot;roll down?quot; and each of the entities has
    an alternate key on the same key attribute then the resulting
    physical model of a logical to physical data model
    transformation may contain a table with an index on a column
    which does not have a data type assigned.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * For a logical data model having two entities which have an   *
    * alternate key defined in each of them with "unique      *
    * index" as a transformation option and with a roll down  *
    * relationship defined between them transformation into a      *
    * physical data model leads to a duplication of unique         *
    * index/constraint with one of them having no data type.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please upgrade to Infosphere Data Architect v8.5.0           *
    ****************************************************************
    

Problem conclusion

  • This problem is fixed in Infosphere Data Architect v8.5.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR44666

  • Reported component name

    INFO DATA ARCHI

  • Reported component ID

    5724V1500

  • Reported release

    753

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-07

  • Closed date

    2013-01-21

  • Last modified date

    2013-01-21

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    INFO DATA ARCHI

  • Fixed component ID

    5724V1500

Applicable component levels

  • R753 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9UM9","label":"IBM InfoSphere Data Architect"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"753","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
21 January 2013