JR49715: StagingProp error handling requires better identification of failed records in JDBC-batch for Oracle databases.

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

APAR status

• Closed as program error.

Error description

• For Oracle databases, StagingProp is not able to identify the
  failing record in a batch and would therefore mark the entire
  batch as 'failed' even though some records may have been
  propagated successfully to the production environment.
  

Local fix

Problem summary

• USERS AFFECTED:
   IT staff who run StagingProp to propagate data from staging
  database to production database who are unable to identify the
  source record of a failed batch during propagation.
  
   PROBLEM ABSTRACT:
  
   StagingProp error handling requires better identification of
  failed records in JDBC-batch for Oracle databases.
  
  
   BUSINESS IMPACT:
   The StagingProp utility (which propagates data from the staging
  database to the production database) can have failures during
  the propagation of data. If the utility is run in batch mode, it
  can be difficult for IT staff to identify the source record of
  the failed bach to remedy the issue. This can delay the
  propogation content to the database.
  

Problem conclusion

• With some improvements in the Oracle JDBC-batch error handling,
  StagingProp can now better identify the failing records in an
  executed JDBC-batch.
  
   StagingProp is updated to report a partial success message
  rather than full failure indication when a record in a batch has
  failed to be propagated. The STAGLOG table is used to track
  success or failure of a record being propagated from staging to
  production. If there is a failure in a batch, the records
  propagated successfully will be marked as processed (indicator
  value of 1) and all others will be marked as failed (indicator
  value of < 0).
   -------------------------------------------------------------
   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 EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R700 PSY

     UP