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… Number of Views On database startup for RSA Identity Governance and Lifecycle the following error is seen: CRS-2501: Resource 'ora.avdb.d… Number of Views AFX Server stuck in 'Not running' State, with error 'timed out waiting for AFX applications to start' Number of Views 'The request could not be handled' error on the UI after updating Table Options in RSA Governance & Lifecycle Number of Views Role Stuck in 'Applied' or 'Applied New' State with 'Additional Changes Cannot Be Made' error in RSA Governance & Lifecycle Number of Views
Trending Articles
How to replace the RSA Authentication Manager self signed console certificate with a signed certificate from Microsoft Act… How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager Patch Updates
Don't see what you're looking for?
