ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Load DWH "Invalid column name" on custom field (SQL Server)


Article ID: 111744


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


Running Load Data Warehouse - Full on Clarity with SQL server, it fails with error message:
2018/08/18 22:04:58 - User Defined Java Class.0 - 2018/08/18 22:04:58 - Oracle? - [CA Clarity][SQLServer JDBC Driver][SQLServer]Invalid column name 'TEST_FIELD'.  



Release: Any


This usually happens due to mismatch in PPM and DWH database on a custom field. If you check the object referenced by the bg-dwh log, you will be able to find a custom field "TEST_FIELD" in the object attributes

  1. Connect to Clarity - Objects - <OBJECT NAME> - Attributes and uncheck TEST_FIELD from being included in Data Warehouse.
  2. Run a Full Load of DWH job
  3. Unchecking the field forces the DWH_<OBJECT>_V to be rebuild and it should no longer throw this message
  4. Once it runs fine, we recommend to enable the field again out of peak hours and see if it goes through fine to the DWH database.