Direct links to fixes
Closed as program error.
StagingProp may fail due to an update of the primary columns of the attribute dictionary table, CATENTRYATTR. StagingProp does not support update of primary key but when one or more of primary key columns of the CATENTRYATTR table are updated, it will cause StagingProp to throw exceptions. The primary key columns of CATENTRYATTR are: CATENTRY_ID, ATTR_ID, and ATTRVAL_ID. This update can be caused by external tools that updates the table, or by the MERGE statement within the workspace commit.
The staging trigger for update against the CATENTRYATTR table is enhanced such that upon the case when the primary key columns are updated, the trigger action will record this as a Delete of old CATENTRYATTR record followed by an Insert of the new record. So when StagingProp is run, it will do exactly these actions in the production database, a delete of old CATENTRYATTR followed by an Insert of the new record. This solution is only applicable to database tables that have no children tables, as the cascade delete will have no effect to leaf tables. CATENTRYATTR is a leaf table.
USERS AFFECTED: WebSphere Commerce IT users that runs StagingProp PROBLEM ABSTRACT: Updating the attribute dictionary's attribute value of a product may cause StagingProp to fail. This update will result in an update to one of the primary columns of the table, specifically the CATENTRYATTR table ATTRVAL_ID column. However, StagingProp does not support update of primary key it will fail when this happen. This problem may occur when the update happens within the context of a workspace or through toolings or utilties that updates the CATENTRYATTR table's primary key columns. BUSINESS IMPACT: Attribute dictionary's attribute value of products updated by workspace commit and by utilities can not be successfully propagated to the production server through StagingProp. RECOMMENDATION: Customers who update product's attributes through workspaces or utilties into authoring server should consider applying this fix.
The solution is to enhance the staging trigger for update against the CATENTRYATTR. Upon an update of the primary column of CATENTRYATTR, the staging trigger will record it as a delet of old CATENTRYATTR record followed by an insert of the new record, otherwise the trigger will record this as an update of the existing record. The CATENTRYATTR is a leaf table so cascade delete has no impact. ------------------------------------------------------------- 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 / Pervasive
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
11 October 2012