The Enforce Server migration may fail in a three-tier environment when you upgrade to Symantec Data Loss Prevention version 15.7 and up.
The issue occurs because Symantec Data Loss Prevention database "DatabaseProcessCheck" action remains active during the migration.
Stop all Symantec Data Loss Prevention database sessions:
sqlplus /nolog
SQL> connect sys/password@protect as sysdba
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%';
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;
/
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.