JR42158: CMVC 217638 - IMPROVE THE PERFORMANCE ISSUES RELATED WITH STAGINGPROP UTILITY.
A fix is available
Closed as program error.
This APAR provides a better-performing StagingProp utility that will reduce the number of database connections, execute better optimized SQL and provide faster consolidation of records in the STAGLOG table. A new summary report is also added to indicate the number of records, by table, that were processed, with breakdowns by type of transaction (Insert/Update/Delete). This new report will help the IT staff to better understand the impact of the business user traffic on the staging processes.
USERS AFFECTED: IT staff who run StagingProp to propagate data from staging database to production database who are either unable to complete the staging propagation within their maintenance window or perform adequate problem determination using just the StagingProp log information. PROBLEM ABSTRACT: StagingProp requires some additional performance enhancements and better error handling. BUSINESS IMPACT: Staging propagation (copying from the staging database to the production database) operates on the STAGLOG table, which tracks the Create/Update/Delete activity against the database tables. This operation consists of consolidation of records to reduce volume of activity, and the propagation of those changes. When there are a large number of changes being made, leading to a large number of records in the STAGLOG table, the StagingProp utility takes a long time to complete each of theses phases. RECOMMENDATION:
This update is focused on 3 main areas within StagingProp. 1. Performance improvement - Reduced number of database I/O operations by increasing the number of records fetched at a time - Added a database index on the STAGLOG table to improve fetch performance 2. Better error toleration for consolidation with Action On Error support for operations on the same record: - Deletion followed by Update - Deletion followed by Deletion - Insertion followed by Insertion - Update followed by Insertion 3. Provide support for cyclic reuse of unique keys by adding support through additional column UPDATABLE_UK_COL in tables STGSITETAB and STGMERTAB. 4. Additionally, to ease problem determination, distinct-value exit codes from invocation of the utility are being made available. These exit codes may be used to categorize severity of error(s) in question and to determine the phase of the utility at which error(s) were encountered. An exit code of 0 indicates a successful execution. An exit code other than 0 is an indication of an error encountered by the utility. Refer to the log file generated by the utility for more diagnostic information if a non-zero exit code is issued by the utility. ------------------------------------------------------------- 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
Reported component name
WC BUS EDITION
Reported component ID
YesSpecatt / New Function
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
WC BUS EDITION
Fixed component ID
Applicable component levels
Translate this page: