000032828 - RSA Via Lifecycle and Governance installation fails with the following error:  <install directory path>/staging/deploy/create_avdb/../../database/cliAveksa.sh: Permission denied

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

Article Content

Article Number000032828
Applies ToRSA Product Set: RSA Via Lifecycle and Governance 7.0
RSA Version/Condition: 7.0, 6.9.1
Platform: RSA Software Appliance
O/S Version: SuSE 11 SP3, Red Hat
IssueWhen trying to install RSA Via Lifecycle and Governance 7.0 or Identity Management and Governance 6.9.1 the following error displays:
 
Starting Oracle...
=============================================================================
Customizing AVDB memory settings . . .

--------------------------------------------------------------------------
Creating AVDB Instance...
sh: /tmp/aveksa/staging/deploy/create_avdb/../../database/cliAveksa.sh: Permission denied
sh: /tmp/aveksa/staging/deploy/create_avdb/../../database/cliAveksa.sh: Permission denied

--------------------------------------------------------------------------
Checking database connections...
Checking database...
Failed to connect to the database
ERROR: Unable to connect to the database; aborting installation
Use "sudo /tmp/aveksa/staging/deploy/configure.sh" to repeat the configuration questions.
Use "sudo /tmp/aveksa/staging/deploy/install.sh" to retry the installation
CauseThis issue occurs on RSA Via Lifecycle and Governanace software appliances where the Oracle UserID and oinstall group are being created by the installer with a numeric ID other than 500.
 
WorkaroundACM-58287 has been filed to have this rectified in a future release.
For now the workaround for this issue is to create the oracle user and oinstall group prior to executing install.sh:
groupadd -g 500 oinstall
useradd -u 500 -g 500 -d /home/oracle -s /bin/bash oracle

NOTE: If a previous installation was attempted and failed these are the cleanup steps that must be run prior to re-running the installation.  This cleanup purges all files created with the undesired Oracle ID:
  1. Run the uninstaller:
cd /tmp/aveksa/staging/deploy
./uninstall.sh

  1.   Change the user and group to the expected IDs:
usermod -u 500 oracle
groupmod -g 500 oinstall

  1.   Remove all the spawned files under /tmp without deleting the installation media:
cd /tmp
mv aveksa ..
rm -rf /tmp/*
mv ../aveksa /tmp/
cd aveksa
rm -rf /tmp/aveksa/staging/*

  1.   Unpack a fresh copy of the files for staging:
cd staging
tar -jxvf ../packages/aveksa-7.0.0.tar.bz2

  1.   Delete the other files and directories that did not live under /tmp that were not removed by the uninstaller:
rm -rf /u01
rm -rf /home/oracle
rm -rf /home/admin
rm /usr/local/bin/coraenv
rm /usr/local/bin/dbhome
rm /usr/local/bin/oraenv

  1. Delete the admin user and his home directory (which will be created on next installation attempt)
userdel -r admin

Attachments

    Outcomes