000031902 - RSA Via L&G Oracle install fails with [INS-13001] due to subsequent Oracle Listener start failure

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000031902
Applies ToRSA Product Set: Via Lifecycle and Governance (L&G), Identity Management and Governance (IMG)
RSA Version/Condition: 7.0.0, 6.9.1
Platform: Red Hat Linux
Platform (Other): Software appliances with a local Oracle database (this may also be a problem with a remote database)
IssueDuring execution of /tmp/aveksa/staging/install.sh, the installation fails with a generic Oracle error, 
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2015-10-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 should be reviewed for specific details whenever there is an Oracle installation error.  
In this case, the end of the oracle.log shows an Oracle Netca failure and subsequently, the Oracle Listener could not start.
Successfully Setup Software.
Oracle Installer Exit Code: 0
Check /u01/app/oracle/product/11.2.0/db_1/install/root_rsagov-dev.nbme.org_2015-10-07_13-32-28.log for the output of root script
Configure Oracle Networking...
Parsing command line arguments:
    Parameter "silent" = true
    Parameter "responsefile" = /u01/app/11.2.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
CauseThere is an underlying network configuration issue which is not immediately obvious because the typical command checks for hostname and ip address succeeded without error.
Each of these commands completed without error: 
$ hostname  -  this should return the FQDN for the system
$ nslookup <hostname> - this ensures that the host is recognized within the customer network
$ nslookup <ip-address> - this ensures that the ip address is recognized within the customer 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

What was not immediately apparent is that 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' in the Customer network, but they did not match each other.  All the network files on the software appliance should contain the same ip-address.
ResolutionEnsure that all network files on the system include the correct ip-address.
Check:  /etc/hosts file
            all files in /etc/sysconfig/network-scripts as needed.
1) uninstall the failed application  (/tmp/aveksa/staging/uninstall.sh)  
2) re-run the installation  (/tmp/aveksa/staging/install.sh)