Staging propagation does not propagate data from custom tables if the table is defined in uppercase *|* -355A6C2AD9B5E13A

StagingProp completes successfully without any exceptions however review of the stageprop log and the STAGLOG table shows that some of the data was never processed and are still in an unprocessed state.

Staging data that have table names defined in uppercase in the STAGLOG.STGTABLE field are ignored when using the staging propagation utility from WebSphere Commerce version 6.0.0.5 or higher.

This problem does not affect the propagation of default tables as they are defined in lowercase when the record is added to STAGLOG.

To resolve this problem contact IBM Support and request APAR LI74643. This APAR is targeted for inclusion in WebSphere Commerce version 6.0.0.9. Alternatively complete the following steps to update STAGLOG staging triggers and staging configuration tables so that table names are defined in lower case.

1. Identify tables that are not defined in lowercase in the staging configuration tables:
   
   select tabname from stgsitetab where tabname <> lower(tabname)
   select tabname from stgmertab ?where tabname <> lower(tabname)
   select tabname from stgmrsttab where tabname <> lower(tabname)
   
2. Update the tables STGSITETAB STGMERTAB STGMRSTTAB so that table names identified in step 1 are defined in lowercase as necessary.
   
   update <staging table> set tabname = 'MYTABLE' where tabname = 'mytable'
   
   where <staging table> is one of the stgsitetab stgmertab stgmrsttab as identified in step 1.
   
3. Identify tables that are not defined in lowercase in the custom filter xml.
   Note: This step is only required if you are using a custom filter xml to define the scope for staging propagation. Otherwise continue to step 4.
   
   Search for Table elements that have table names that are not in lowercase and update these references as necessary.
   
   For example the following entry <Table name="MYTABLE" /> will need to be changed to <Table name="mytable" />.
   
4. Identify tables that are not defined in lowercase in the STAGLOG table.
   
   select distinct stgtable from staglog where stgtable <> lower(stgtable)
   
5. Re-create staging triggers for the tables that have been identified in step 4 so that tables names are defined in lowercase.
   
6. Update the table references in STAGLOG so that they are defined in lowercase.
   
   update staglog set stgtable = lower(stgtable)
   
7. Rerun staging propagation.