JR43248: TRANSFORMING TO A PHYSICAL MODEL MAY RESULT IN RELATIONSHIP NAMES NOT BEING TRANSFORMED CORRECTLY

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

  • This issue can occur when transforming a logical model to a
    physical model. Selecting "Use name source" on the
    transformation wizard options screen may result in relationship
    names not being transformed to valid physical model names.
    <br/><br/>For example, if the LDM contains a relationship named
    &quot;ORGANIZATION INDUSTRY&quot;, transforming to a PDM with
    this option set will result in a constraint with the same name,
    including the spaces. Having spaces as part of the constraint
    name can cause errors when generating and running DDL.
    

Local fix

  • As an alternative to &quot;Use name source&quot;, select
    &quot;Use naming standards&quot; on the transformation wizard
    screen.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users.                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * InfoSphere Data Architect relationship physical name not     *
    * valid after Transform LDM->PDM.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please upgrade to InfoSphere Data Architect v8.5.0           *
    ****************************************************************
    

Problem conclusion

  • This issue was fixed in InfoSphere Data Architect v8.5.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR43248

  • Reported component name

    INFO DATA ARCHI

  • Reported component ID

    5724V1500

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-26

  • Closed date

    2012-12-18

  • Last modified date

    2012-12-18

  • 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

  • R760 PSN

       UP

  • R810 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere Data Architect

Software version:

810

Reference #:

JR43248

Modified date:

2012-12-18

Translate my page

Machine Translation

Content navigation