CA Data Protection 14.6 Infrastructure fails to start due to corrupt 'Database.properties' files.
Article ID: 7019
Updated On:
Products
Issue/Introduction
CA Data Protection (DataMinder) endpoint clients and servers encounter unexpected infrastructure failures because of corrupt 'Database.properties' files.
This is seen in activity log as an entry 'unable to read properties file'
Environment
Cause
The database.properties file contains the encrypted database credentials which allows CA Data protection (DataMinder) components to connect to the Data Protection (DataMinder) database. In some circumstances where the database.properties file becomes corrupt the recovery version of the file (ie database.properties.bak) also become corrupt and cannot be recovered.
Resolution
FIX:RO96314 (incorporating incorporating Client_14.6_HF0134.msp, Client_x64_14.6_HF0135.msp, Server_14.6_HF0132.msp, Server_x64_14.6_HF0133.msp) improves integrity checking on database.properties files before taking a backup to ensure recovery copies are not inadvertently corrupted. When the CA DataMinder infrastructure service is unable to retrieve data from the active database.properties file, data is retrieved from the backup file to ensure a successful recovery and normal start up of the infrastructure service.
Additional Information
FIX:RO96314 is available to download from the CA Support portal (http://support.ca.com).
Orchestria, CA DLP and DataMinder are previous brand names for the product now known as CA Data Protection.
Feedback
