When installing RSA Identity Governance & Lifecycle on Red Hat Enterprise Linux (RHEL), the execution of
/tmp/aveksa/staging/install.sh fails with the following generic Oracle error:
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2020-07-07_01-26-13PM.
Please wait ...[WARNING] [INS-13001] Environment does not meet minimum requirements.
CAUSE: Minimum requirements were not met for this environment
ACTION: Either check the logs for more information
or check the supported configurations for this product.
[WARNING] [INS-41812] OSDBA and OSASM are the same OS group.
CAUSE: The chosen values for OSDBA group and the chosen value for OSASM group are the same.
ACTION: Select an OS group that is unique for ASM administrators.
The OSASM group should not be the same as the OS groups that grant privileges for Oracle ASM access,
or for database administration.
The
/tmp/aveksa/oracle.log file shows the following Oracle installation error.
Configure Oracle Networking...
Parsing command line arguments:
Parameter "silent" = true
Parameter "responsefile" = /u01/app/12.1.0/grid/assistants/netca/netca.rsp
Parameter "lisport" = 1555
Done parsing command line arguments.
Oracle Net Services Configuration:
Profile configuration complete.
Listener is using the port provided in the command line:1555
Oracle Net Listener Startup:
The information provided for this listener is currently in use by other software on this computer.
Listener start failed.
Check the trace file for details:
/u01/app/oracle/cfgtoollogs/netca/trace_Ora11g_gridinfrahome1-15100712PM3229.log
Oracle Net Services configuration failed. The exit code is 1
There is an underlying network configuration issue that is not immediately apparent because the commands that check for
hostname and
IP address succeed without error. Review of the
oracle.log file shows that an Oracle Network Configuration Assistant (NetCA) failure occurred preventing the Oracle Listener from starting.
ANALYSIS:Each of these commands complete without error:
$ hostname - this should return the FQDN for the system
$ nslookup <hostname> - this ensures that the host is recognized within the network
$ nslookup <ip-address> - this ensures that the IP address is recognized within the network
$ ping -c 5 <ip-address> - this should be done from another system to confirm accessibility within the network
$ ifconfig - this lists the network configuration for the physical network adapters
However, the IP address found in
/etc/hosts (which is returned as output from the
nslookup command) was NOT the same IP address value that was returned by the
ifconfig command (which outputs the information found in either
/etc/sysconfig/network-scripts/ifcfg-eth0 or if the ethernet hardware devices are bonded, found in
/etc/sysconfig/network-scripts/ifcfg-bond0.) Both addresses were valid, and could be found on the network but they did not match each other.
All the network files on the server should contain the same IP address.
In this case the reason for the failure was that the IP address in
/etc/hosts was not the same as the IP address found in /
etc/sysconfig/network-scripts/ifcfg-eth0 or
/etc/sysconfig/network-scripts/ifcfg-bond0. Make sure all networking files on the system refer to the same IP address for the RSA Identity Governances & Lifecycle server and retry the installation.
- Check /etc/hosts and all files in /etc/sysconfig/network-scripts to ensure that all network files on the RSA Identity Governance & Lifecycle server include the correct IP address.
- As root, uninstall the failed application:
cd /tmp/aveksa/staging
./uninstall.sh
- Re-run the installation:
cd /tmp/aveksa/staging
./install.sh
