JR45651: RELATIONSHIP CREATION EXCEPTION DURING THE RELLINKER PROCESS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Possible error during the RelLinker process when a single
    member has multiple active attributes used in relationship
    rules.
    Conditions:
    1. The relationship rule needs to involve the memidnum on one
    side
    2. The attribute on the other side of the rule must allow
    multiple active values (i.e. nsactive > 1)
    To Reproduce:
    1. Load configuration where the above conditions exist.
    2. Create 3 records. We'll assume the records are SOURCE:1,
    SOURCE:2 and SOURCE:3
    3. Retrieve SOURCE:3 in Inspector
    4. Add attribute value matching MemIdnum 1, save and save
    5. Wait for RelLinker to complete, you should see an Audit log
    entry similar to the following...
     AUDIT iatesystems.hub.logging.AuditLog: IXN=RELLINKER,
    USRRECNO=1, RELLINK created, RelLink recStat:A relLinkno:103
    relTypeno:5 relSeqno:0 entRecnoLeft:101 entRecnoRight:108
    ruleRecno:1 relFlag:Y.
    6. Add new attribute value matching MemIdnum 2, save and save
    7. Wait for RelLink to complete, you should see the error:
    ERROR tems.hub.engine.wrkmgr.RelWrkMgr: entType [org], error
    during relLinker execution
    com.initiatesystems.orm.exception.InvalidResourceUsageException
    

Local fix

  • Modify your Hub Configuration and data process to include a new
    MemAttr attribute to store the MemIdnum into.  Then, change the
    Relationship Rule to use the new MemAttr attribute instead of
    the MemIdnum.
    

Problem summary

  • ****************************************************************
    Possible error during the RelLinker process when a single
    member has multiple active attributes used in relationship
    rules.
    ****************************************************************
    

Problem conclusion

  • ****************************************************************
    This issue was fixed in MDS v10.1 September 2013 Fix Pack
    and it is  available on IBM Support Site
    ****************************************************************
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR45651

  • Reported component name

    INTMASTERDATA

  • Reported component ID

    5725B6300

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-06

  • Closed date

    2014-04-02

  • Last modified date

    2014-04-02

  • 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

    INTMASTERDATA

  • Fixed component ID

    5725B6300

Applicable component levels

  • R970 PSY

       UP



Document information


More support for:

Initiate Master Data Service

Software version:

9.7.0

Reference #:

JR45651

Modified date:

2014-04-02

Translate my page

Content navigation