README VERSION: 1.1 DATE: 2019-08-14 FIXES APPLIED FOR PRODUCTS: --------------------------- 9.3.2 DLO_9.3.2 PACKAGES: PATCH NAME: DLO_9.3.2.1 SUPERSEDED PATCHES: NONE REQUIRED PATCHES: NONE PATCH CATEGORY: PATCH CRITICALITY : OPTIONAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED: NO OS: win INSTALL/UNINSTALL INSTRUCTIONS: ------------------------------- This package contains self-extracting files that are specific to the processor architecture and operating system version. Choose the appropriate file for your computer's configuration. ====================================================================================== Operating System Platform File Name ---------------------------------------------------------------------------------------- Download the appropriate hotfix executable to a temporary location on your system. You can install this hotfix using the GUI or from the command line. Instructions for both options are provided below.Complete details with screenshots is provided in the Read Me file, as well as Technote. 1. From the DLO Administration Console > Tools > Blackout Windows option, set the blackout window for the DLO Server. Note: This ensures there are no backups from the endpoints. 2. Click on the provided Hotfix Installer (Veritas_Desktop_and_Laptop_Option_9.3.2_32-bit_HF.msp) based on the bitness of the machine. 3. Proceed as per the instructions in wizard and click Finish It is recommended not to uninstall this hotfix SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:9.3.2.1 3982181 (3982180) Post upgrade to DLO 9.3.2 version, unable to access the Dedupe Server. SUMMARY OF KNOWN ISSUES: ----------------------------------------- 3982185 (3982180) Post upgrade to DLO 9.3.2 version, unable to access the Dedupe Server. FIXED INCIDENTS: ---------------- PATCH ID:9.3.2.1 * INCIDENT NO:3982181 TRACKING ID:3982180 SYMPTOM: Post upgrade to DLO 9.3.2 version, unable to access the Dedupe Server. DESCRIPTION: Post upgrade to DLO 9.3.2 version, DLO administrator is unable to initialize and manage the Dedupe Server, as the connection between the Dedupe Server and the database is down. RESOLUTION: The config.xml file parameters on the Dedupe Server and Edge Server have been updated. On the Dedupe Server path: \Dedupe\Tomcat\webapps\DedupeServer\META-INF On the IO Server path: \IOServer\Tomcat\webapps\DLOServer\META-INF Context.xml file parameters are updated as below maxActive - > maxTotal maxWait -> maxWaitMillis removeAbandoned -> removeAbandonedOnBorrow KNOWN INCIDENTS: ---------------- * INCIDENT NO:3982185 TRACKING ID:3982180 SYMPTOM: No Symptom Found WORKAROUND: No WorkAround Found INCIDENTS FROM OLD PATCHES: --------------------------- NONE NONE