JR52690: Enable updatedb utility to run with close-to-zero downtime

7.0.0.8-WS-WCServer-IFJR52690
7.0.0.9-WS-WCServer-IFJR52690
7.0.0.8-WS-WCDeveloperExpress-IFJR52690
7.0.0.8-WS-WCDeveloperEnterprise-IFJR52690
7.0.0.8-WS-WCDeveloperProfessional-IFJR52690
7.0.0.9-WS-WCDeveloperProfessional-IFJR52690
7.0.0.9-WS-WCDeveloperExpress-IFJR52690
7.0.0.9-WS-WCDeveloperEnterprise-IFJR52690

APAR status

• Closed as new function.

Error description

• This enables execution of updatedb utility for close-to-zero
  downtime scenarios.
  
  Previously suggested method of execution was to perform a
  database backup prior to executing the utility. In case of
  failures, the backup would need to be restored and the utility
  run again.
  
  For close-to-zero downtime scenarios, performing a restore in
  case of failure is not feasible because the amount of time
  required to perform the restore and any associated IT tasks
  would necessarily lead to database downtime.
  

Local fix

Problem summary

• USERS AFFECTED:
  WebSphere Commerce IT administrators on version 7.0 fix pack 9
  or higher, who install fix packs and update the database schema.
  
  PROBLEM ABSTRACT:
  Enable updatedb utility to run with close-to-zero downtime
  
  BUSINESS IMPACT:
  There is a need for significant database downtime when
  performing fix pack upgrades on a WebSphere Commerce database.
  
  RECOMMENDATION:
  

Problem conclusion

• This fix introduces retry capability that allows the updatedb
  utility to resume execution from point of failure. This fix also
   removes the requirement to perform a backup and restore in the
  event of a failure during invocation of the utilty.
  
  For close-to-zero downtime and other scenarios, in case of a
  failure, all that is required is for the updatedb utility to be
  issued again.
  
  In the fixpack schema scripts, SQL comment hint blocks now
  enclose each DDL statement. The hints contain predicates that
  identify whether a schema change (DDL statement) should be
  executed by checking if the schema change already exists in the
  database due to a previous updatedb execution.
  
  An Ant task is used to read and parse the scripts for these
  conditional statements. If the conditional predicates evaluate
  to true (indicating the schema change doesn't exist in the
  database) then the DDL statements are executed. If they evaluate
   to false then execution of the DDL statement is skipped.
  

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