EDM profiles fail while using DLP Remote Indexing

Products

• Data Loss Prevention Core Package

Issue/Introduction

EDM output files are failing to complete and the EDM logs will show invalid rows.

Environment

Release : 15.8 16.0.x +

Component : Enforce

Cause

This issue is most commonly caused by "bad" or invalid data coming from EDM source file. Bad data includes blank rows, too many/few columns etc. If you have mandatory fields selected in your mapping, then any row that is missing this data is consider 1 failure. Too many failures can throw off the EDM schema and cause issues, so DLP prevents it from completing for this reason. 

Resolution

1. If you are using custom scrips, you can modify or clean up the source data to get rid of invalid characters. For any help on this, contact professional services.

 

2. For remote indexers, you can configure it to ignore bad rows. 

On remote indexer, edit the "indexer.properties" file. Locate the following setting and change it to "true". This will be false by default:

 

# Rows are considered bad if they have more columns than expected or a column data type is incorrect.

# Set to true if bad rows should be ignored.

drop_bad_rows = true