RSA Identity Governance & Lifecycle fails to start with "Unable to get avdb connection" message
Originally Published: 2018-09-26
Last Modified: 2026-10-30
Article Number
000041129
Applies To
  • Product: RSA Identity Governance & Lifecycle
  • Versions: 7.x , 8.x
  • Component: Oracle Listener, Oracle Database, avdb Database Connection
  • Platform: Linux (Appliance or Software Install running JBoss)

 

Issue

RSA Identity Governance & Lifecycle fails to start after an application or Oracle restart, and users are unable to access the login page.

Observable symptoms include:

  • The application console displays the Initialization Status screen with the following message instead of completing startup:
    Unable to get avdb connection to check for data re-encryption.
    Verify that the database is available and a connection to the avdb database can be made with the avuser credentials.
  • The aveksaServer.log shows the following key errors:
    ERROR [com.aveksa.migration.jdbctool.CheckDatabase] Unable to get avdb connection
    ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
  • The server.log shows the following warning:
    WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolBySubject] IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
  • Running acm statusoracle confirms the database is running but the Oracle listener is not servicing any connections:
    Database is running.
    The listener supports no services.
Cause

The Oracle listener is running but has lost its connection to the Oracle database, preventing RSA Identity Governance & Lifecycle from establishing the avdb database connection it requires at startup.

This state occurs when the Oracle database service or Oracle High Availability Services are restarted — either manually or due to a system event such as a reboot or power interruption — without the Oracle listener being recycled as part of that restart. The listener process remains active and appears to be running normally, but it is no longer servicing any database connections. This commonly happens when the Oracle database is restarted independently while RSA Identity Governance & Lifecycle or the Oracle listener is left in its previous state.

Resolution

CAUTION: The following steps stop and restart Oracle High Availability Services, which will temporarily bring the Oracle database offline. Ensure you have planned a maintenance window and notified affected users before proceeding.

  1. Run the following command to stop the Oracle High Availability Services:
    acm stoporacle

    Expected output:

    CRS-4621: Oracle High Availability Services autostart is disabled.
    CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on '<hostname>'
    CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on '<hostname>'
    CRS-2677: Stop of 'ora.LISTENER.lsnr' on '<hostname>' succeeded
    CRS-2673: Attempting to stop 'ora.evmd' on '<hostname>'
    CRS-2677: Stop of 'ora.evmd' on '<hostname>' succeeded
    CRS-2793: Shutdown of Oracle High Availability Services-managed resources on '<hostname>' has completed
    CRS-4133: Oracle High Availability Services has been stopped.
    CRS-4639: Could not contact Oracle High Availability Services
  2. Run the following command to start the Oracle High Availability Services:
    acm startoracle

    Expected output:

    CRS-4622: Oracle High Availability Services autostart is enabled.
    CRS-4640: Oracle High Availability Services is already active
    CRS-4000: Command Start failed, or completed with errors.
    CRS-4638: Oracle High Availability Services is online
    Database is running.

    NOTE: The CRS-4000: Command Start failed, or completed with errors. message in the output above is expected and does not indicate a problem in this scenario. Confirm the output ends with both CRS-4638: Oracle High Availability Services is online and Database is running. before proceeding.

  3. Verification: Navigate to the RSA Identity Governance & Lifecycle login page. Confirm the Initialization Status screen is no longer displayed and the login page loads successfully. If the application does not recover automatically, restart RSA Identity Governance & Lifecycle and recheck the login page.