Symantec Data Loss Prevention (DLP) Enforce

If you are having performance issues and need the SQL queries to send to engineering for diagnosis, you can enable SQL Query (manager_jdbc.log) logging.

To enable SQL Query logging in the Manager (for DLP 15.0 and below):

1. Edit <DLP Home>\Protect\config\ManagerLogging.properties
2. Set com.vontu.jdbc.level to FINE
3. Set com.vontu.util.jdbc.JDBCLogHandler.level to FINE
4. Restart the VontuManager process.

Once JDBC logging is enabled, go into the UI and perform any task that is perceived as slow; i.e., run reports, select incidents -- whatever takes more time than it should.

Any SQL statement not executed through OJB will be logged to \Vontu\Protect\logs\debug\manager_jdbc_0.log along with the time it took to execute the statement.

After performing this test:

1. Reset com.vontu.jdbc.level to INFO
2. Reset com.vontu.util.jdbc.JDBCLogHandler.level to INFO
3. Restart the VontuManager process.

To enable SQL Query logging in the Manager (for DLP 15.1 and Above):

1. Edit \Program Files\Symantec\DataLossPrevention\EnforceServer\15.5\Protect\config\ManagerLogging.properties
2. Set com.vontu.jdbc.level to FINE
3. Set com.vontu.util.jdbc.JDBCLogHandler.level to FINE
4. Restart the SymantecDLPManager Service.

Once JDBC logging is enabled, go into the UI and perform any task that is perceived as slow; i.e., run reports, select incidents -- whatever takes more time than it should.

Any SQL statement not executed through OJB will be logged to \ProgramData\Symantec\DataLossPrevention\EnforceServer\15.5\logs\debug\manager_jdbc_0.log along with the time it took to execute the statement.

After performing this test:

1. Reset com.vontu.jdbc.level to INFO
2. Reset com.vontu.util.jdbc.JDBCLogHandler.level to INFO
3. Restart the SymantecDLPManager Service.