EDM: Data file for exact data profile "<EDM Name>" version <Version Number> could not be found

Products

• Data Loss Prevention Endpoint Prevent
• Data Loss Prevention
• Data Loss Prevention API Detection for Developer Apps Virtual Appliance
• Data Loss Prevention API Detection Virtual Appliance
• Data Loss Prevention Cloud Detection Service
• Data Loss Prevention Cloud Detection Service for ICAP
• Data Loss Prevention Cloud Detection Service for REST
• Data Loss Prevention Cloud Package
• Data Loss Prevention Cloud Prevent for Microsoft Office 365
• Data Loss Prevention Cloud Service for Discovery/Connector
• Data Loss Prevention Cloud Service for Email
• Data Loss Prevention Cloud Storage
• Data Loss Prevention Core Package
• Data Loss Prevention Data Access Governance
• Data Loss Prevention Discover Suite
• Data Loss Prevention Endpoint Discover
• Data Loss Prevention Endpoint Suite
• Data Loss Prevention Enforce
• Data Loss Prevention Enterprise Suite
• Data Loss Prevention for Mobile
• Data Loss Prevention for Office 365 Email and Gmail with Email Safeguard
• Data Loss Prevention Form Recognition
• Data Loss Prevention Network Discover
• Data Loss Prevention Network Email
• Data Loss Prevention Network Monitor
• Data Loss Prevention Network Monitor and Prevent for Email
• Data Loss Prevention Network Monitor and Prevent for Email and Web
• Data Loss Prevention Network Monitor and Prevent for Web
• Data Loss Prevention Network Prevent for Email
• Data Loss Prevention Network Prevent for Email Virtual Appliance
• Data Loss Prevention Network Prevent for Web Virtual Appliance
• Data Loss Prevention Network Protect
• Data Loss Prevention Network Web
• Data Loss Prevention Oracle Standard Edition 2
• Data Loss Prevention Plus Suite
• Data Loss Prevention Sensitive Image Recognition
• Data Loss Protection Oracle Standard Edition

Issue/Introduction

Every time the EDM schedule runs on its scheduled time it logs the following error in the tomcat logs:

Indexing InfoSource Job begin executing

Data file for exact data profile "<EDM Name>" version <Version Number> could not be found

Environment

DLP Release : 15.8.x

Cause

Customer created EDM indexes in pre 15.5 version of DLP.

After upgrading to 15.5, due to a defect, older schedules were disconnected for use in 15.5 and 15.5 MP1 versions.
15.5 MP2 and later restored the correct scheduler and the older schedules were merged back together with any 15.5 schedules that were created since.
During the time these schedules where disconnected, a EDM index was deleted. Because the schedule for that index was disconnected at the time, it was not deleted with the rest of the index like it was supposed to be.

Every time the schedule runs on its scheduled time it logs the following error in the tomcat logs.

Data file for exact data profile "<EDM Name>" version <Version Number> could not be found

Resolution

This is a known concern resolved in the DLP 16.0 upgrade and above.