JR53251: Quick publish might fail for content managed tables with a composite primary key.

APAR status

• Closed as program error.

Error description

• Quick Publish might fail for content managed tables with a
  composite primary key. For example, the primary key of the table
   CATENTDESC is CATENTRY_ID + LANGUAGE_ID.
  

Local fix

• When Quick Publish failed,  use StagingProp to propagate the
  failed data but this will cause delay in the process.
  

Problem summary

• USERS AFFECTED:
  WebSphere Commerce business users leveraging Workspaces with
  Quick Publish setup.
  
  PROBLEM ABSTRACT:
  Quick publish might fail for content managed tables with a
  composite primary key.
  
  BUSINESS IMPACT:
  Business will not be able to use Quick Publish to send the
  committed workspace data from the the staging server to the
  production server.
  
  RECOMMENDATION:
  

Problem conclusion

• The problem is cause by the return order of the primary key
  columns not matching what is found in the database metadata and
  what is defined in the Commerce managed resource configuration
  file.
  
  The solution is to change the code to examine and align the
  order of these columns such that the correct parameters are set
  in the Quick Publish SQLs.
  

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