Failed to connect to the database error during upgrade to RSA Identity Governance & Lifecycle 7.0.1

[#1]

Article Number

000035013

Applies To

RSA Product Set:  RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.1

 

Issue

During the upgrade to RSA Identity Governance & Lifecycle 7.0.1, the aveksa-install.log displays the following error:

[Wed Mar 29 15:44:41 EDT 2017] Shutting down RSA Identity Governance and Lifecycle...
[Wed Mar 29 15:44:41 EDT 2017] Shutting down RSA Identity Governance and Lifecycle completed

--------------------------------------------------------------------------
[Wed Mar 29 15:44:41 EDT 2017] Configuring users...
[Wed Mar 29 15:44:41 EDT 2017] Configuring users completed

--------------------------------------------------------------------------
[Wed Mar 29 15:44:41 EDT 2017] Installing Oracle Client...
[Wed Mar 29 15:44:43 EDT 2017] Installing Oracle Client completed

--------------------------------------------------------------------------
[Wed Mar 29 15:44:43 EDT 2017] Checking database connections...
Checking database...
Failed to connect to the database[Wed Mar 29 15:44:43 EDT 2017] Checking database connections...
Checking database...
Failed to connect to the database

Cause

1. Open the following files in a text editor:

• /tmp/aveksa/staging/deploy/common.sh,
• /tmp/aveksa/staging/deploy/install.sh and
• /tmp/aveksa/staging/database/cliAveksa.sh

2. Add the following command as the first line in each file.  This will print subsequent executed commands to the terminal.

set -x

3. Save and close the files.
4. Run the installation again.
5. The last command run before the failure is:

. CHECK_SQLPLUS=Y
. su - oracle -c 'tmp/aveksa/staging/deply/../database/cliAveksa.sh -check dbtuning silent'
. "[' 126 -gt 0 ']'
. tee -a /tmp/aveksa-install.log
. echo 'Failed to connect to the database'
. failed to connect to the database
return 2
. '[' N = N ']' 
echo ''

6. When you execute the following command as root, the following permission denied error is seen:

su - oracle -c '/tmp/aveksa/staging/deploy../database/cliAveksa.sh -check dbrunning silent'
bash: /tmp/aveksa/staging/deploy../database/cliAveksa.sh: Permission denied

Resolution

In this particular case, we had multiple issues where the files in /tmp/aveksa/staging did not have the correct ownership and file protections.

Follow the instructions in the RSA Identity Governance and Lifecycle V7.0.1 Installation Guide to create /tmp/aveksa/staging and /tmp/aveksa/packages as root and untar the files to /tmp/aveksa/staging/ as root.  

The files need to be executable and we must be allowed to write logs to /tmp.  Run the following:

chmod +x /tmp/aveksa/staging/deploy/common.sh
chmod +x /tmp/aveksa/staging/deploy/install.sh
chmod +x /tmp/aveksa/staging/database/cliAveksa.sh