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
Last Modified: 2023-12-01
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
Oracle Database Collector fails with "ORA-01017:invalid username/password" in RSA Identity Governance & Lifecycle 221Number of Views RSA Identity Governance and Lifecycle7.0.2 installation with remote database fails with "Invalid Username/Password" in the… 210Number of Views ORA-01017: invalid username/password; logon denied . For details refer to "(:CLSN00107:)" when attempting to start the dat… 414Number of Views Upgrade of RSA Identity Governance and Lifecycle from earlier versions to 7.0.2 fails during WildFly configuration phase. 252Number of Views ORA-20005 error occurs after a patch or version upgrade of RSA Identity Governance & Lifecycle during migration 44Number of Views
Trending Articles
Don't see what you're looking for?