IBM Support

JR49190: This fix is to avoid foreign key violation during workspace approval caused by processing tables in incorrect order.

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

  • After approving a workspace task group, the task group returns
    in the 'Commit Failed' state with a foreign key violation
    exception in the log during the approval process.  If all data
    that is referenced by the offending table in the exception
    exists in the workspace and task group being approved, then this
     may be caused by a problem with the order in which resources
    are processed during the workspace approval.
    For example, a child table such as FACET is processed before its
    parent table ATTR and thus the foreign key is committed to the
    production ready schema before its parent primary key table is
    inserted.
    

Local fix

Problem summary

  • USERS AFFECTED:
    WebSphere Commerce users who create custom tables that are
    workspace enabled in multiple configuration files or customers
    who apply APAR JR43818.
    
    PROBLEM ABSTRACT:
    After approving a workspace task group, the task group is in
    'commit failed' state as a result of an error such as a foreign
    key violation exception in the log.  The error is the result of
    a child table that is processed before the parent table for
    containers that have multiple configuration files.
    
    BUSINESS IMPACT:
    Business users are unable to approve any content if this problem
    is observed without removing the offending data.
    
    RECOMMENDATION:
    

Problem conclusion

  • This ifix will sequence all resources in the content-management
    directory in the proper order.
    
    Workspaces resource configuration files that are placed in the
    xml/content-management directory can be dynamically loaded by
    placing all the metadata within the resource file definition and
    includes the 'id' tag to indicate the order of the container.
    Prior to this ifix, dynamically loaded configuration files did
    not respect the order within this tag and essentially loaded in
    the order in which the operating system returned the files.  The
    order is important since child tables must be processed after
    their parent tables for any operation under workspaces.   This
    APAR ensures the configuration files are loaded and ordered from
    lowest to highest and will also merge into one configuration any
    resource defined in multiple configuration files with the same
    name and id.
    
    
    -------------------------------------------------------------
    The latest available maintenance information can be obtained
    from the Recommended Fixes for WebSphere Commerce technote:
    http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR49190

  • Reported component name

    WC BUS EDITION

  • Reported component ID

    5724I3800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-29

  • Closed date

    2014-05-03

  • Last modified date

    2014-05-03

  • 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

    WC BUS EDITION

  • Fixed component ID

    5724I3800

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSYL","label":"WebSphere Commerce Enterprise"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 May 2014