JR45423: CMVC 224111 - ENABLE FILELOADER TO CORRECTLY RE-LOAD AND SET MANAGED-FILE STATUS FOR FILES THAT ALREADY EXIST IN THE DATABASE

APAR status

• Closed as program error.

Error description

• A managed file being uploaded to the database with FileLoader
  that has an existing entry in the CMFILE table which is set to
  file-system managed, i.e., has STORAGE_TYPE set to -1, but
  actually has entries in the child CMSMALLFILE and CMLARGEFILE
  tables, may cause FileLoader to terminate abnormally and
  silently.
  

Local fix

• If the symptoms described in the "Problem Description" section
  have manifested, update the CMFILE table by setting the
  STORAGE_TYPE column value to 0 if the existing CMFILE entry
  corresponds to a CMSMALLFILE child table entry or to 1 if the
  existing CMLARGEFILE entry corresponds to a CMLARGEFILE child
  table entry.
  

Problem summary

• USERS AFFECTED:
  WebSphere Commerce users on v7.0 who wish to re-upload managed
  file content into the database that may have incorrect
  storage-type and file content associations.
  
  PROBLEM ABSTRACT:
  Enable FileLoader to Correctly Re-load and Set Managed File
  Status for Files That Already Exist in the Database
  
  BUSINESS IMPACT:
  Managed files with existing entries in the database may fail on
  re-upload if the file's storage-type indicates file-system
  managed, i.e., STORAGE_TYPE column value of -1 in the existing
  CMFILE table record, but an entry exists in either child
  CMSMALLFILE or CMLARGEFILE table.
  
  RECOMMENDATION:
  Refer to the workaround provided or contact WebSphere Commerce
  Support for assistance
  

Problem conclusion

• A file loaded into CMFILE and its child tables that has a
  storage type of -1 (managed by file-system) causes FileLoader to
  assume that no child record exists in the either child table
  (CMSMALLFILE and CMLARGEFILE). Subsequently FileLoader attempts
  an INSERT rather than an UPDATE into the appropriate child table
  and terminates abnormally when the INSERT fails due to the
  already-existing child record. This causes the problematic file
  and any files in the queue remaining to be processed from being
  properly uploaded.
  
  The solution is to determine whether or not an entry exists in
  either child table and then performing an appropriate INSERT or
  UPDATE.
  
  Resolution is being made to appropriately detect such scenarios.
  This entails:
  - Repairing the incorrect STORAGE_TYPE value
  - Uploading the file content into CMSMALLFILE or CMLARGEFILE
  table as appropriate
  
  -------------------------------------------------------------
  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