Unable to save an incident filter report. Error: Unexpected server error occurred. Please refer to log for details.
search cancel

Unable to save an incident filter report. Error: Unexpected server error occurred. Please refer to log for details.

book

Article ID: 277632

calendar_today

Updated On:

Products

Data Loss Prevention Data Loss Prevention Oracle Standard Edition 2

Issue/Introduction

You created an incident filter report and when you save it, you are getting the error: "Unexpected server error occurred. Please refer to log for details."

In the Localhost log, you will see the error:

File: Enforce\logs\tomcat\localhost.2024-01-03.log
Date: 1/3/2024 7:26:37 AM
Thread: 121
Level: ERROR
Source: org.hibernate.engine.jdbc.spi.SqlExceptionHelper
Message: ORA-00001: unique constraint (PROTECT.REPORTFILTER_PK) violated

And, in the manager_jdbc log, you will see the below error:

File: Enforce\logs\debug\manager_jdbc_0.log
Date: 1/3/2024 7:19:21 AM
Level: SEVERE
Thread: 17
Session: 1
EventType: Failed
Id: 74
Caller: com.vontu.manager.spring.ManagerContextLoaderListener.configureAndRefreshWebApplicationContext(48), query failed: ORA-00955: name is already used by an existing object
Time: 
Message: 
    create global temporary table HT_DocSource (infoSourceId number(19,0) not null) 
        on commit delete rows;

Environment

Symantec Data Loss Prevention 16.0.x

Cause

All incident filters must be uniquely named. Including names of filters that have been deprecated, as they are retained for reporting purposes.

Resolution

When creating an incident filter report, always use a name not used before with another report before saving.