Failed to connect to the database error during upgrade to RSA Identity Governance & Lifecycle 7.0.1
Originally Published: 2017-04-06
Last Modified: 2022-06-20
Article Number
Applies To
RSA Version/Condition: 7.0.1
Issue
[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 databaseCause
- 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
- Add the following command as the first line in each file. This will print subsequent executed commands to the terminal.
set -x
- Save and close the files.
- Run the installation again.
- 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 ''
- 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 deniedResolution
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
Related Articles
How to connect to SQL in RSA Authentication Manager 8.x 339Number of Views Error: Failed to connect to Identity Router, RSA SecurID Access Authenticate app tokencodes fail with an RSA Authenticatio… 224Number of Views Manage the RSA Web-Tier Bootstrapper Server on Windows 69Number of Views Verify the LDAP Directory Identity Source 69Number of Views v7.0.0 installation fails during configuring wildfly Failed to set session cookie. Error message - Unable to connect to co… 60Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?