RSA Via Lifecycle and Governance 7.0 installation looping when running Oracle Cluster Verification Utility (CVU) cluvfy/runfixup.sh scripts
3 years ago
Originally Published: 2016-03-28
Article Number
000064584
Applies To
RSA Product Set: RSA Via Lifecycle and Governance 7.0 (L&G)
RSA Version/Condition: 7.0, 6.9.1
Platform: RSA Software Appliance
O/S Version: SuSE 11 SP3, Red Hat
Issue
After executing the install.sh to install RSA Via Lifecycle and Governance 7.0 or Identity Manager and Governance 6.9.1, you are prompted to press Enter or Return to have Oracle attempt to rectify a "fixable" problem.

The screen loops continuously after this until terminated.

This is a screenshot of the behavior:
User-added image
The /tmp/aveksa/oracle.log contains entries similar to what is below:
  
Check: Package existence for "nfs-kernel-server" 
  Node Name     Available                 Required                  Status    
  ------------  ------------------------  ------------------------  ----------
  img7          missing                   nfs-kernel-server-1.2.1-2.24.1  failed    
Result: Package existence check failed for "nfs-kernel-server"


 
Cause
There is a defect opened for the looping behavior, however the underlying cause is that there is a requirement that is not satisfied and Oracle's runfixup.sh only partially satisfies the requirement.

At the time of this writing two occurrences are known to cause this behavior:
  1. Missing RPM dependencies required for Oracle.
  2. Oracle is attempting to modify a configuration file, however the change is not being applied.
Resolution
1. To resolve the Linux package dependency look within the /tmp/aveksa/oracle.log for the phrase "failed" and the required missing package will be identified.  To get a list of packages that are requires for Red Hat or SuSE please refer to the Oracle Grid package dependency list.  This is the same as Oracle's dependencies but has one or more additional.  Requirements for Oracle 12 can be found here.  After the prerequisites are met, the installation may ask to run the cluvfy runfixup.sh however it should proceed through the installation.

2. The second cause mentioned above would also be noticed in the /tmp/aveksa/oracle.log file and would repeatedly list the modification it was going to make and to which file.  One modification in particular that has been reported is an update to the sysctl.conf file.  To workaround this issue, apply the modification manually and in the sysctl.conf example, run sysctl -p to have the file reread by the operating system.

Related Articles

Trending Articles

Don't see what you're looking for?