ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Enable SQL Query (JDBC) logging in DLP

book

Article ID: 159781

calendar_today

Updated On:

Products

Data Loss Prevention Enforce

Issue/Introduction

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.

Resolution

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

  1. Edit
    1. Windows Path: \Program Files\Symantec\DataLossPrevention\EnforceServer\15.x\Protect\config\ManagerLogging.properties
      1. where x is the DLP version
    2. Linux Path: /opt/Symantec/DataLossPrevention/EnforceServer/15.x/Protect/config/ManagerLogging.properties
      1. where x is the DLP version
  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

Windows Path: \ProgramData\Symantec\DataLossPrevention\EnforceServer\15.x\logs\debug\manager_jdbc_y.log

Linux Path: /var/log/Symantec/DataLossPrevention/EnforceServer/15.x/debug/manager_jdbc_y.log

where x is the DLP version
and y is the log number

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.

 

 

Additional Information

Legacy Information:

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.
Powered by Wolken Software