Upgrade of RSA Governance and Lifecycle from 7.0.0 to 7.0.1 fails with Checking database... Invalid Username/Password
Originally Published: 2016-10-31
Article Number
Applies To
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.0.1
Issue
Tue Oct 18 16:52:50 MDT 2016] Checking database connections...
Checking database...
Invalid Username/Password
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.
You have connected remotely from the ACM client node in a SQL*Plus connection, successfully, to the following Oracle remote database accounts:
- AVUSER
- ACMDB
- AVDWUSER
Resolution
We recommend you ensure you can connect with all four accounts to your remote database before the installation:
- AVUSER
- ACMDB
- AVDWUSER
- PERFSTAT
Related Articles
RSA Identity Governance and Lifecycle7.0.2 installation with remote database fails with "Invalid Username/Password" in the… 203Number of Views Oracle Database Collector fails with "ORA-01017:invalid username/password" in RSA Identity Governance & Lifecycle 210Number of Views RSA SecurID 3.0 Software Token Quick Start Guide (Italian) 10Number of Views Using a password dictionary file to control PIN criteria for RSA Authentication Manager 8.x 92Number of Views Upgrade of RSA Identity Governance and Lifecycle from earlier versions to 7.0.2 fails during WildFly configuration phase. 245Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?