Exact data profile creation failed on enforce with event code 2905
search cancel

Exact data profile creation failed on enforce with event code 2905

book

Article ID: 272998

calendar_today

Updated On:

Products

Data Loss Prevention

Issue/Introduction

Customer encounters the following error on the Enforce server -

Code

2905

Summary

Exact data profile creation failed

Detail

Data file for exact data profile "xyz" was not created. Please look in the enforce server logs for more information.

 

 

 

 

Environment

DLP 15.8,16.0

Cause

This can be cause by multiple different problems:

1. Oracle database resource issue:

This can happen if customer is indexing large amounts of data and also if multiple indexing jobs are scheduled at same time. Resource issues on enforce/Oracle DB server during indexing could also cause this issue.

Tomcat logs show below entries -

SEVERE [com.vontu.profiles.manager.database.DataSourceIndexCreator] "Unexpected I/O error occurred while creating final index {0} from {1}."

Cause:

java.lang.Throwable: Unknown errorjava.lang.Throwable: Unknown error

Caused by: Unknown error

com.vontu.profileindex.database.jni.EDMAPIException: Unknown errorUnknown error

 

2. Problems with directory connections

 

Resolution

Oracle database issues

Customer need to schedule indexing jobs at different times to avoid this issue, particularly when they are indexing large amounts of data.

 

Directory connection issues

Check each of the directory connections (system > settings > directory connections) and make sure they are able to test connect successfully