Load DWH Full - When to run to prevent failures
search cancel

Load DWH Full - When to run to prevent failures


Article ID: 224741


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


There are times the Load Data Warehouse (DWH) job Full Load needs to run versus Incremental to prevent job failures. This article covers the scenarios when the full load should be run


Run the full load DWH after any of the below:

1. Upgrade (release or patch)

2. Attribute changes

If any of the following occur, run the load DWH in full mode. 

  • Deletion of an attribute in Studio
  • Unselecting the Include in the Data Warehouse option for the attribute in Studio. You cannot re-enable the attribute for inclusion in the data warehouse unless at least this job has completed one run.
  • Attribute Data Type changes

3. Time Slice Date changes

  • Change to time slice dates to include a larger timeframe.

4. First Day of Work Week setting change

  • Change of the First Day of Work Week in Administration->Project Management->Settings

5. Data Warehouse Option changes in System Options

Change to any of the settings in General Settings -> System Options -> Data Warehouse Options including:

  1. Addition of a new language. Running an incremental load of this job does not update the data warehouse with the new language.
  2. Change to the Entity for fiscal periods.

6. Prior Incremental job failure

If you have run into an issue due to any of the above, you must run the full Load DWH job prior to running the incremental job again. See Load DWH incremental fails with duplicate key after a previous incremental failure for a known issue you can run into if the full is not run first. 

Additional Information

The job is not required to be run after changing a lookup. See After changing Lookup values - Load DWH full or incremental where this is referenced.

For other post-upgrade recommendations see: Upgrade best practices (pre / post upgrade) for Clarity