The Full Load Data Warehouse Job Fails After Excluding a Custom Dynamic Attribute from the Data Warehouse

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

When a dynamic lookup attribute is excluded from the Data Warehouse, the Full Load Data Warehouse job fails.

This is the error found in the job output:

ERROR (version 5.0.2, build 1 from 2013-12-04_15-52-25 by buildguy) : Unexpected error
ERROR (version 5.0.2, build 1 from 2013-12-04_15-52-25 by buildguy) : java.lang.RuntimeException: ERROR: THERE WERE ERRORS DURING DIMENSION JOB EXECUTION FOR THE TABLE - DWH_INV_IDEA
at Processor.processRow(Processor.java:64)
at org.pentaho.di.trans.steps.userdefinedjavaclass.UserDefinedJavaClass.processRow(UserDefinedJavaClass.java:1181)
at org.pentaho.di.trans.step.RunThread.run(RunThread.java:60)
at java.lang.Thread.run(Thread.java:745)
dwh_etl_interface_dim - dwh_etl_interface_dim
dwh_etl_interface_dim - dwh_etl_interface_dim
dwh_etl_interface_dim - ERROR (version 5.0.2, build 1 from 2013-12-04_15-52-25 by buildguy) : Errors detected!
null

Cause

A possible cause for this is that the dynamic lookup has a query that has a schema name hardcoded (e.g.: using "niku.inv_investments" instead of "inv_investments").

The attribute that is being excluded may not be the one causing the issue, but it is an attribute of the same object containing the dynamic lookup using the schema name.

Resolution

Locate the query that contains a hard-coded schema name in the code and modify it so that it is no longer specified.

As this is a lookup in use by an attribute, please check this Clarity PPM Community entry on how to update the lookup:

Problem to change a dynamic lookup query

Once the query has been corrected, exclude the desired attribute and run the Full Load Data Warehouse job.