On RSA Via Lifecycle and Governance the aveksa_server start returns message: Cannot connect to the database, but the DB is up
Originally Published: 2016-05-24
Article Number
Applies To
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.0 and higher
Issue
$ service aveksa_server start
Cannot connect to the database. The watchdog will start the server when it can connect to the database.
However, the database can be successfully connected to from SQL*Plus and is showing as up with the aveksa_server statusdb option:
$ service aveksa_server statusdb 15817 Database is running.
Cause
Resolution
Related Articles
Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201… 294Number of Views AFX Server stuck in 'Not running' State, with error 'timed out waiting for AFX applications to start' 3.63KNumber of Views On database startup for RSA Identity Governance and Lifecycle the following error is seen: CRS-2501: Resource 'ora.avdb.d… 518Number of Views 'The request could not be handled' error on the UI after updating Table Options in RSA Governance & Lifecycle 166Number of Views RSA Authentication Manager 8.8 upgrade fails with ERROR: auth_manager.rest_service.old_access_key is not found 2.25KNumber of Views
Trending Articles
RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide How to Upgrade Internal SHA-1 Certificates to SHA-256 in Authentication Manager Using rsautil RSA Release Notes for RSA Authentication Manager 8.8 RSA SecurID Desktop Token 5.0.3 for Windows Administrator's Guide
Don't see what you're looking for?