Install and Upgrade Issues 101 for Data Loss Prevention Enforce

Products

• Data Loss Prevention Enforce
• Data Loss Prevention

Issue/Introduction

Learn how to resolve many of the common issues or errors that may occur when you install or upgrade Symantec Data Loss Prevention (DLP) Enforce.

Resolution

Table of Contents

• Install
• General install
  • Certificates
  • Communications
  • Java Heap errors
  • Oracle database
  • Server configuration
  • Server hardening
  • Hosted Detection Servers (Private cloud infrastructure)
  • Red Hat Enterprise Linux (RHEL) detection servers
  • Windows Detection servers
• Upgrade
  • General upgrade
  • Certificates
  • Detection server upgrades
  • Oracle database upgrade
  • Update Readiness Tool

Install

General install

• DLP Install Guides for Windows
• DLP system event codes and severity levels

Certificates

• Error: "Certificate not imported, alias already exists" when importing root certificates
• Error: "keytool error: java.lang.Exception: Failed to establish chain from reply" when importing signed certificates for DLP Enforce

Communications

• Disable older TLS and SSL protocols (SSLv3, TLSv1.1, and TLSv1.0) for DLP communications

Java Heap errors

• Error: "Severe Error 2600 - Communication error" in system alerts
• Incident, message, and traffic data is not updating in DLP Enforce
• Data Loss Prevention 64-bit Server Migration and Tuning Guide
• DLP Enforce UI does not load and cannot log in after an upgrade

Oracle database

• Error: "ORA-12541: TNS:no listener" in DLP Enforce
• Receiving "ORA-12154: TNS:could not resolve the connect identifier specified" while trying to login to Enforce Server database
• Create the Oracle database on Windows for use with DLP
• Create the Oracle database on Linux for use with DLP

Server configuration

• Configure LDAP Active Directory connection for DLP 15.x and later versions
• Configure DLP Enforce to send reports and system alerts

Server hardening

• Create SSL certificate for DLP signed by a trusted Certificate Authority

Hosted Detection Servers (Private cloud infrastructure)

• Deploy DLP on the Microsoft Azure infrastructure

Red Hat Enterprise Linux (RHEL) detection servers

• For a list of the Required Linux RPMs, see Table 37, on p. 164 of the Symantec-Data-Loss-Prevention-Help-Center_15.8.pdf
• Error: "This system is not registered with RHN" when installing package on RHEL

Windows Detection servers

• Create response rule to perform automated tasks in DLP
• Set up and configure detection servers for Data Loss Prevention

Upgrade

General upgrade

• Upgrade guides for Symantec DLP
• Can Symantec DLP perform phased upgrades?
• How to upgrade JRE on DLP 15.5/15.7
• Move a DLP Endpoint server to a new server as part of a hardware refresh or operating system upgrade.

Certificates

• DLP upgrade overwrites the CACERTS keystore causing the secure LDAP connection to break.

Detection server upgrades

• DLP Detection servers show "Unknown" status

Oracle database upgrade

• Error: "SP2-0640: Not connected" when creating an Oracle user for DLP
• Oracle Critical Patch Update on Windows fails with error 74
• Error: "TNS-04610: NO LITERALS LEFT, REACHED END OF NV PAIR" when installing Oracle for use with DLP

Update Readiness Tool

• Checking the database update readiness
• Preparing to run the Update Readiness Tool
• URT fails with Error: UDE-00018: Data Pump client is incompatible with database version 12.1.0.2.0
• Error: "Data Foreign Key Constraint Validation...Data violations are detected on your schema" in the DLP Update Readiness Tool
• Error: "UpdateReadinessTool failed to run" on Red Hat Linux
• Error: "Unable to establish db connection for user protect - invalid connection identifier" when running DLP Update Readiness Tool