SE59015: Some STAGLOG entries remain unprocessed after quick publish

7.0.0.9 for Developer Express
7.0.0.9 for Developer Professional
7.0.0.9 for Developer Enterprise
7.0.0-WS-WCServer-FP009

APAR status

• Closed as program error.

Error description

• The commit timestamp used for the quick publish is calculated
  using the local system's timestamp instead of the timestamp from
   the database server. This may cause an issue when the database
  is on a remote machine and the time on 2 machines are out of
  synch. Some STAGLOG entries may remain marked as 'unprocessed'
  at the end of the Quick Publish run.
  
   The next invocation of Stagingprop may then lead to a primary
  key collision since the data from the quick publish would be
  propagated again to the production environment.
  

Local fix

Problem summary

• USERS AFFECTED:
   WebSphere Commerce users on v7.0.0.6 who use quick publish.
  
   PROBLEM ABSTRACT:
   Some STAGLOG entries remain unprocessed after quick publish
  
   BUSINESS IMPACT:
   Data may become out of sync between the staging and production
  systems, and may ultimately lead to data propagation errors
  during the maintenance window.
  
   RECOMMENDATION:
  

Problem conclusion

• The quick publish code is updated to initialize the commit
  timestamp with the timestamp value from the database, instead of
   from the local server.
  
  
   -------------------------------------------------------------
   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 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 EDIT AS4

• Fixed component ID

  5724I3803

Applicable component levels

• R701 PSY

     UP