We are using Pega v 7.1.7, with Pega MKT and Pega NBAA v 7.2

We have been observing that many DB connections remain active in DB side even after Pega App Server reboot, causing the DB resources to be occupied by old DB connection sessions that were pre-existing before server was shutdown.

I have seen exactly similar thread in PDN which is closed now, hence starting another thread for an answer, before I raise this as a Pega SR.

https://collaborate.pega.com/question/inactive-db-sessions

In the above thread, same situation is being discussed however, the suggestion provided doesnt apply for us, as in our case, these DB sessions even remain after Pega Server was bounced. Our DBA confirm that these DB sessions were establised prior to our App server shutdown, and now occupying DB resources, causing overall performance degradation in Production/Live environment. These DB sessions are more than 20 days old, and they switch from ACTIVE to INACTIVE state since then. 

Since these are sessions from prior to App Server shutdown, we need some inputs from Pega community forum what could be possibly the case here? Is it a Pega config issue, or a Product bug that we need to take up with Pega GCS or Oracle?

***Edited by Moderator Kayla to update Product and Version***