Patch/upgrade fails with 'java: No such file or directory' error in RSA Identity Governance & Lifecycle
Originally Published: 2020-03-03
Article Number
Applies To
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.0
Issue
Preparing the ear file for deployment at Tue Dec 17 19:46:52 EST 2019
– Expanding the CURRENTLY deployed ear to filesystem for further checks to apply patch.
./customizeACM.sh: line 6: /usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/bin/java:
No such file or directory
An error occured in the customizeACM command : error code 127
Step failed! See /home/oracle/Aveksa_7.1.1_P03/logs/7.1.1_P03_2019-12-17-1946.log
for more information.Cause
This issue may occur if the Java update is applied before the patch or upgrade is performed. The patch fails because the JAVA_HOME variable is not updated immediately after the Java update.
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P06
- RSA Identity Governance & Lifecycle 7.2.0 P01
Workaround
- Log out of the application server (log out of root)
- Log in again as the root user.
- Run the patch or upgrade again.
Related Articles
AM 8.1 patch upgrade fails with error "Failed to finalize the update" Number of Views How to increase the max-pool-size for the Workpoint data source (WPDS) in RSA Identity Governance & Lifecycle Number of Views Invalid Request error accessing workflows after patching/upgrading RSA Identity Governance & Lifecycle Number of Views Patch/upgrade fails with 'Error deploying the ear file' error in RSA Identity Governance & Lifecycle Number of Views Service cannot start after Patch upgrade or reboot Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
