An error occurred while the 'DIM Incident File Name' attribute of the 'DIM Incident File' dimension from the 'RiskFabric' database was being processed

book

Article ID: 198648

calendar_today

Updated On:

Products

Information Centric Analytics Data Loss Prevention Core Package

Issue/Introduction

Cube processing fails during the nightly RiskFabric Processing job. The job history logs make reference to "Errors in the back-end database access module. The size specified for a binding was too small, resulting in one or more column values being truncated" and "[a]n error occurred while the 'DIM Incident File Name' attribute of the 'DIM Incident File' dimension from the 'RiskFabric' database was being processed".

Cause

The DIM Incident File dimension queries the view vLDW_FileDim, which in turn queries the table LDW_Files. This error indicates the existence of at least one record with a FileName length that exceeds the 255 character limit in this column's definition in the DIM Incident File Name attribute in the DIM Incident File dimension.

Environment

Release : 6.5.x

Component : RiskFabric Processing

Resolution

Alter the view vLDW_FileDim using the following script:

ALTER VIEW dbo.vLDW_FileDim
AS
 SELECT     FileID, 
      CASE WHEN COALESCE((SELECT CAST(Value AS BIT) FROM dbo.PortalSettings WHERE Name = 'EnablePIIDataMaskingInAnalyzer'), 0) = 1 THEN 'File-' + CAST(FileID AS NVARCHAR) ELSE CAST(FileName AS NVARCHAR(255)) END FileName,
      CASE WHEN COALESCE((SELECT CAST(Value AS BIT) FROM dbo.PortalSettings WHERE Name = 'EnablePIIDataMaskingInAnalyzer'), 0) = 1 THEN 'File-' + CAST(FileID AS NVARCHAR) ELSE CAST(NormalizedFileName AS NVARCHAR(255)) END NormalizedFileName,
      DocumentType
 FROM       dbo.LDW_Files WITH (NOLOCK)