Load Data Warehouse job fails due to long Status report name
search cancel

Load Data Warehouse job fails due to long Status report name

book

Article ID: 407768

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

The Load Data Warehouse job Full and Incremental fails due to Status report names being long and therefore results in empty Jaspersoft Reports.

The following error is recorded in bg-dwh.log file.

Error for table 'DWH_INV_STATUS_REPORT' - Error Number 7347 'OLE DB provider 'MSSQL' for linked server 'PPMDBLINK' returned data that does not match expected data length for column '[PPMDBLINK].[niku].[DWH_COP_PRJ_STATUSRPT_V].status_report_name'. The (maximum) expected data length is 480, while the returned data length is 512,

This issue is supposed to have been resolved in earlier Clarity version 16.1.3

Environment

Clarity 16.2.3

Cause

From version Clarity 16.1.3 we increased attribute_code 'name' length in dwh_meta_columns where object_code is 'cop_prj_statusrpt' to 768 characters but Data Warehouse still
fails when Status report name has only 260 chararcters.

The reason for this behaviour is because the view 'DWH_COP_PRJ_STATUSRPT_V' did not get regenerated after the upgrade and still retained 240 characters for 'STATUS_REPORT_NAME' column.

Resolution

To resolve the issue create a custom attribute on the object 'Status Report'. This will cause the view 'DWH_COP_PRJ_STATUSRPT_V' to get regenerated and the length of column 'STATUS_REPORT_NAME' gets corrected to 768 characters.