Cannot log into the DLP Enforce Console after database maintenance

Products

• Data Loss Prevention

Issue/Introduction

The Enforce Console login page fails to load after database maintenance.

The following error is seen in the IncidentPersister.log on the Enforce Server. A similar error is also observed in the localhost.<date>.log:

(SEVERE) Thread: 18 [com.vontu.incidenthandler.IncidentPersister.start] Unexpected error starting Incident Persister.
com.vontu.util.jdbc.UnknownSchemaVersionException: No record exists in ENFORCEVERSION table to identify the schema current version
    at com.vontu.util.jdbc.JDBCTestConnection.testDatabaseConnectionAndCheckSchemaVersion(JDBCTestConnection.java:76)
    at com.vontu.util.jdbc.JDBCTestConnection.testDatabaseConnectionAndCheckSchemaVersion(JDBCTestConnection.java:113)
    at com.vontu.util.jdbc.JDBCTestConnection.checkDatabaseConnection(JDBCTestConnection.java:138)
    at com.vontu.incidenthandler.IncidentPersister.start(IncidentPersister.java:125)
    at com.vontu.incidenthandler.IncidentPersister.main(IncidentPersister.java:240)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:325)
    at java.lang.Thread.run(Thread.java:750)

 

Running the following query against the database shows all versions are marked as 'N':
select * from ENFORCEVERSION;

Environment

Symantec Data Loss Prevention 16.x

Cause

The ENFORCEVERSION table requires one of the versions to be marked as the most recent.

Resolution

1. Revert the database to the backup taken before the database maintenance.
2. Checking the ENFORCEVERSION table after reverting the database should show one of the DLP versions marked as the most recent.