fixing Enforce Server migration fail for three-tier environments due to “DatabaseProcessCheck”

By November 20, 2020Symantec DLP Enforce
You are here:
< Back

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. Resart the migration process.
Was this article helpful?
0 out Of 5 Stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?