IBM Support

JR46354: Records not found during execution of the stagingprop utility ar e left in the unprocessed state.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The stagingprop Utility attempts to match unprocessed
    (STGPROCESSED column value of 0) records logged in the STAGLOG
    table with physical data records in the table and with the
    primary-key indicated by the STGTABLE and STGOKEY1 through
    STGOKEY5 column values.
    
    Under certain (unexpected) scenarios, physical data records
    indicated by the primary-key values recorded in the STAGLOG
    table may not exist. The utility leaves such records as
    unprocessed, which may cause confusion upon subsequent
    invocations of the utility.
    

Local fix

  • Manually update the STAGLOG table to mark records not found on
    the Staging database with a value of -5. What follows is an
    example of an SQL UPDATE statement that will do this for a
    single-column primary-key table, i.e., CATENTRY:
    UPDATE STAGLOG S
    SET S.STGPROCESSED = -5
    WHERE S.STGTABLE = 'catentry'
    AND NOT EXISTS (SELECT 1 FROM CATENTRY T WHERE T.CATENTRY_ID =
    S.STGOKEY1);
    

Problem summary

  • USERS AFFECTED:
    WebSphere Commerce users on v7.0 who use the stagingprop utility
    and encounter errors pertaining to data not being found on the
    Staging database
    
    PROBLEM ABSTRACT:
    Records not found during execution of the stagingprop utility
    are left in the unprocessed state.
    
    BUSINESS IMPACT:
    Invocations of stagingprop may repeatedly and unnecssarily
    re-fetch data that cannot be found on the Staging database.
    
    RECOMMENDATION:
    

Problem conclusion

  • With this ifix, records not found on the Staging database during
     invocation of the stagingprop utility are no longer left as-is,
     but are instead marked with a value of -5 in the STGPROCESSED
    column of the STAGLOG table.  This fix will help facilitate
    problem determination, making the problematic records more
    obvious.
    
    -------------------------------------------------------------
    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

    JR46354

  • Reported component name

    WC BUS EDITION

  • Reported component ID

    5724I3800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Serviceability

  • Submitted date

    2013-04-15

  • Closed date

    2013-05-30

  • Last modified date

    2013-05-30

  • 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:
30 May 2013