Installation fails with '[INS-13001] Environment does not meet minimum requirements' and 'Oracle Net Services configuration failed' in RSA Identity Governance & Lifecycle
Originally Published: 2015-11-23
Article Number
Applies To
RSA Version/Condition: All
Platform: Red Hat Enterprise Linux (RHEL)
Platform/Application Server: WildFly
Issue
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.
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
Cause
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
$ 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.Resolution
- 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
Related Articles
Oracle INS-41812 OSDBA and OSASM are the same OS group warning during RSA Identity Governance & Lifecycle installation Number of Views RSA Identity Governance and Lifecycle 7.0.x upgrade or installation fails with [FATAL] [INS-13013] and Oracle Installer Ex… Number of Views How to deploy custom plugins in RSA Identity Governance and Lifecycle Number of Views What are steps to use Microsoft CA with a SID800? Number of Views On-Demand Tokencode Delivery by Mobile Phone or E-Mail Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
