IBM Support

JR50138: Ensures that relevant records in STAGLOG correctly have their STGPROCESSED columns updated after propagation completes

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 fix is to ensure that relevant records in STAGLOG correctly
    have their STGPROCESSED columns updated after propagation
    completes.
    

Local fix

Problem summary

  • USERS AFFECTED:
    WebSphere Commerce users on v7.0 who have installed APAR
    JR42158. Note that this APAR is included in FixPack 6.
    
    PROBLEM ABSTRACT:
    StagingProp may not mark some propagated STAGLOG records as
    processed due to database timestamp discrepancies
    
    BUSINESS IMPACT:
    StagingProp utility may not mark all propagated STAGLOG records
    as processed. Subsequent invocations of the StagingProp utility
    may attempt propagation of records that have already been
    propagated, which could potentially cause unique (primary) key
    or foreign key violations.
    
    RECOMMENDATION:
    Follow the local fix specified in the "Workaround" section or
    contact WebSphere Commerce Support for assistance
    

Problem conclusion

  • Logic in the StagingProp utility assumed that values in both the
     STGRFNBR and STGSTMP would be increasing and uses values from
    these columns (among others) to select the set of records to
    mark as processed.
    
    In some databases, long-running transactions use timestamps from
    when query execution first begins. This can cause concurrent
    transactions that start later, to potentially insert records in
    the STAGLOG table that have lower STGRFNBR values but higher
    STGSTMP values, which violates the assumption previously stated.
    As a result, no records are selected which can then be marked as
    processed.
    
    To rectify, the utility no longer makes assumptions about
    monotonicity between the two columns.
    
    -------------------------------------------------------------
    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

    JR50138

  • Reported component name

    WC BUS DEV ED W

  • Reported component ID

    5724I3900

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-05

  • Closed date

    2014-06-04

  • Last modified date

    2015-05-01

  • 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 DEV ED W

  • Fixed component ID

    5724I3900

Applicable component levels

  • R700 PSY

       UP

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

Document Information

Modified date:
01 May 2015