|Applies To||RSA Product Set: Identity Governance & Lifecycle|
RSA Version/Condition: 7.0.2, 7.1.0, 7.1.1
|Issue||When RSA Identity Governance & Lifecycle is initially installed, the deployed aveksa.ear file is saved in /home/oracle/archive. Every time RSA Identity Governance & Lifecycle is patched or customized, the new aveksa.ear is saved in /home/oracle/archive and the older aveksa.ear files are also retained. The more patch installations and/or customizations, the more aveksa.ear files that are archived and retained in this directory. Over time, the accumulation of these files requires more and more disk space for storage. |
For example, the below directory listing was taken from a 7.1.1 system that had P01 installed and customized, and P03 installed and customized twice. That means six aveksa.ear files stored in /home/oracle/archive each over a gigabyte in size.
The name of the file DO_NOT_REMOVE_ARCHIVE_FILES.txt indicates none of these files can be removed. The contents of this file also indicate these files should not be removed.
This RSA Knowledge Base Article explains which files may be safely removed from this directory.
|Resolution||The purpose of preserving each aveksa.ear file is to provide the ability to go back to a previous ear file if necessary. However, the RSA Identity Governance & Lifecycle application only requires the currently deployed ear file and the initial ear file (if different from the currently deployed ear file) to be kept.|
To determine which aveksa*.ear files may safely be removed, check the contents of /home/oracle/archive/wildfly_deployment.properties. This files lists the currently deployed ear file and the intial ear file. For example,