Application of RSA Identity Governance & Lifecycle 7.0.2 patch 07 fails to start Aveksa Compliance Manager (ACM) for remote database installation
Originally Published: 2018-06-08
Article Number
Applies To
RSA Version/Condition: 7.0.2 P07
Issue
ACM cannot be started, as it fails with this message, on screen and in /tmp/aveksa-install.log:
Cannot connect to the database. The watchdog will start the server when it can connect to the database.
When you run the installation with an strace, you will find an Oracle network error in the output:
ORA-12154: TNS:could not resolve
When you run the installation with 'set -x' in patch.sh, you will see that we are using an incomplete
connect string:
+ su - oracle -c '/usr/bin/Check_Instance_Running.sh :/myconnectstring silent'
Cause
Resolution
Workaround
PLEASE MAKE SURE YOU TAKE A BACKUP OF EITHER FILE BEFORE MODIFYING THEM.
For example:cp <path/file> /tmp
If you are reading this before you start the P07 patch installation, please edit /tmp/aveksa/staging/deploy/init.d/aveksa_server before you start the P07 installation.
If you already did the P07 patch installation, and the ACM startup at the end failed,please edit /etc/init.d/aveksa_server and restart ACM after the change. Your installation will show that P07 was correctly applied.
Depending on the file above that needs to bed edited, add the two lines in red after line 40 as outlined below:export $(grep ^AVEKSA_OWNER= $AVEKSA_HOME/Aveksa_System.cfg)
export $(grep ^AVEKSA_WILDFLY_HOME= $AVEKSA_HOME/Aveksa_System.cfg)
export $(grep ^REMOTE_ORACLE= $AVEKSA_HOME/Aveksa_System.cfg)
export $(grep ^USE_ASM= $AVEKSA_HOME/Aveksa_System.cfg)
export $(grep ^REMOTE_ORACLE_IP= $AVEKSA_HOME/Aveksa_System.cfg)
export $(grep ^REMOTE_ORACLE_PORT= $AVEKSA_HOME/Aveksa_System.cfg)
No need to add the text in black as that already exists in the file.
Related Articles
What happens to Access Fulfillment Express (AFX) during an Aveksa Compliance Manager (ACM) patch installation on a RSA Ide… Number of Views Disable IPv6 on ethernet cards for audit compliance Number of Views Compliance: change default password for log-hybrid sftp/upload accounts Number of Views FIM - FIPS 140-2 compliance. TLS1 ciphers Number of Views Authentication Token is showing in plain text in the Metadata Export for Generic REST collector in RSA Governance & Lifecycle Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.9 Release Notes (January 2026) An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
