JR53266: Dataload for OFFER related data fails the second time it is load ed if the IDENTIFIER in CSV has a leading 0

APAR status

• Closed as program error.

Error description

• if a client uses dataload to load OFFER related data with a 0
  leading Identifier column in the CSV (eg. 0123456789 instead of
  123456789), the second time it tries to load the files again, an
   unique index violation error will be thrown.
  

Local fix

• 1: Workround: let the customer disable the cache for these
  tables:
  
  Add/Modify the following lines to your wc-dataload-env.xml which
  will include the three OFFER related tables from being cached:
  
  <_config:IDResolver
  className="com.ibm.commerce.foundation.dataload.idresolve.IDReso
  lverImpl
  " cacheSize="10000000">
  <_config:ExcludeCache tableName="OFFER" />
  <_config:ExcludeCache tableName="OFFERPRICE" />
  <_config:ExcludeCache tableName="OFFERDESC" />
  </_config:IDResolver>
  
  
  
  2:Workround: Let the customer do not use the 0 leading
  identifier in the csv.
  

Problem summary

• USERS AFFECTED:
  shoppers may not be able to see the correct price for products
  and can create a negative shopping experiecne
  
  PROBLEM ABSTRACT:
  Dataload for OFFER related data fails the second time it is
  loaded if the IDENTIFIER in CSV has a leading 0
  
  BUSINESS IMPACT:
  business users will not be able to load the OFFER data into
  database which can affect the availability of catalog products
  on storefront
  
  RECOMMENDATION:
  

Problem conclusion

• add a simple logic in the OfferMediator to check if the
  identifier passed in from CSV is a big integer and remove the
  leading 0 before passed it into the ID resolver.
  

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 DEV PRO ED W

• Fixed component ID

  5724I4100

Applicable component levels

• R700 PSY

     UP