Unable to add a custom table to the DWH schema without it being truncated
search cancel

Unable to add a custom table to the DWH schema without it being truncated

book

Article ID: 196980

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

Is there a naming convention or option to use to prevent the Load Data Warehouse job from truncating a table when the Full load is selected. We have some audit tables that we would not like truncated.

STEPS TO REPRODUCE:

  1. Add any custom table to DWH schema
  2. Add records in there
  3. Now run Load Data Warehouse - Full Load

Expected Results: The Load Data Warehouse not to truncate a custom table

Actual Results: The Load Data Warehouse truncates custom tables

Environment

CLARITY 16.0.1 and supported releases.

Cause

By design the full Data warehouse used to truncate all the tables in the Data warehouse schema. 

Resolution

This was fixed in 15.9.2 via enhancement linked to product defect DE57009 "Unable to add a custom table to the DWH schema"

Workaround:

Customers can name the custom tables with a prefix of "Z_" which also happens to be the best practice for naming custom content in Clarity. 

or

Tables can be names with a prefix of "DWH_TRD_"

Note: You could also change the store procedure DWH_CFG_PRECONFIG_SP to exclude your custom tables. Keep in mind that some trend jobs may also be deleting info. Do not run the cleanup procedure we have for trends (not available via UI). Any customizations and potential loss of information will be responsibility of the customer