The Enforce Server migration may fail for three-tier environments due to "DatabaseProcessCheck" action

Products

• Data Loss Prevention Enforce

Issue/Introduction

The Enforce Server migration may fail in a three-tier environment when you upgrade to Symantec Data Loss Prevention version 15.7 and up. 

Cause

The issue occurs because Symantec Data Loss Prevention database "DatabaseProcessCheck" action remains active during the migration.

Resolution

Stop all Symantec Data Loss Prevention database sessions:

1. Reboot the Enforce Server.
2. Access the database server.
3. Start SQL*Plus:
   sqlplus /nolog
4. Log on as the SYS user:
   SQL> connect sys/password@protect as sysdba
   Where password represents the SYS password.
5. Run the following query to identify processes running in the database:
   SELECT module, action, client_identifier FROM v$session
      WHERE (
               UPPER(module) LIKE 'VONTU%' OR
               UPPER(client_identifier) LIKE 'VONTU%' OR
               UPPER(module) = 'SYMANTEC DLP: INCIDENT DELETOR' OR
               UPPER(module) = 'DATAUSER_MERGE' OR
               UPPER(module) = 'DATA INSIGHT DATA REFRESH'
             ) AND
             module <> 'Vontu Refresh CBO Stats' AND
             UPPER(module) NOT LIKE '%SCHEMA UPGRADER%';
6.  If the query identifies running processes, run the following command to stop them:
   SET SERVEROUTPUT ON;

    

   DECLARE

       CURSOR inactive_process IS

   SELECT 'ALTER SYSTEM KILL SESSION ' || '''' || sid || ',' || 

   serial# || ''''

   AS kill_stmt, module, sid, serial#

             FROM v$session

            WHERE (

                   UPPER(module) LIKE 'VONTU%' OR

                   UPPER(client_identifier) LIKE 'VONTU%' OR

                   UPPER(module) = 'SYMANTEC DLP: INCIDENT DELETOR' OR

                   UPPER(module) = 'DATAUSER_MERGE' OR

                   UPPER(module) = 'DATA INSIGHT DATA REFRESH'

                  ) AND

                  module <> 'Vontu Refresh CBO Stats' AND

                  UPPER(module) NOT LIKE '%SCHEMA UPGRADER%';

   BEGIN

       FOR x IN inactive_process LOOP

   DBMS_OUTPUT.put_line(x.kill_stmt);

   EXECUTE IMMEDIATE x.kill_stmt;

   END LOOP;

   END;

   /
7. Restart the migration process.

Additional Information

Sometimes, after restarting the Enforce server, the processes still remain active in spite of running the query to kill the processes. In that case, you may also have to bounce the Oracle DB to kill the running processes.