Our DBA team has been identifying several very long running sessions in the Clarity database. The database sessions needed to be killed and it is a problem that keeps coming back. We are unable to identify a root cause.
This issue can be caused by one or more of the following:
1. Database issues/changes.
2. Load Balancer configuration
3. Environmental/migration changes
1. Check if the APP and BG logs to see if there is a message related to the database connection, e.g.
java.sql.SQLException: [CA Clarity][Oracle JDBC Driver]Object has been closed.
at com.ca.clarity.jdbc.oraclebase.ddcr.b(Unknown Source)
2. Please have the DBA team review and confirm that the required Oracle database parameters and settings are set in order for Clarity to perform at the most optimal performance.
Based on the v$parameters results and the AWR analysis, indexes will need to be rebuilt
Section: Configure a PPM Database with Oracle