Project and Portfolio Management Practitioners Forum
cancel

Database IDLE_TIME requirement

Highlighted
eps414
Super Contributor.

Database IDLE_TIME requirement

Due to security requirements all databases in the infrastructure are required to have the oracle database setting of IDLE_TIME set to 15 minutes. This obviously is causing an issue with PPM loosing connections to the database if it is not constantly being used. What I would like to know is if there is anything within PPM, a service or anything that can be scheduled to help alleviate this issue?

Thanks,
Eric
4 REPLIES
Jim Esler
Acclaimed Contributor.

Re: Database IDLE_TIME requirement

Use the server.conf parameter MAX_DB_CONNECTION_IDLE_TIME to release idle connections before 15 minutes. Default value is 60 minutes.
Sascha Mohr
Acclaimed Contributor.

Re: Database IDLE_TIME requirement

Hello Eric,
you should not need to change any setting in PPM (Jim pointed to the right one of course) because if a DB session has been idle for 15 min and the DB terminates that connection PPM should create a new connection the next time it needs on. Maybe there is a negletible error in the server.log. The connection pooling should manage this for itself.
Or did you want to achive that connections stay active by faking activity from the PPM side every x minutes?
eps414
Super Contributor.

Re: Database IDLE_TIME requirement

I want to achieve that PPM always keep a live connection. I thought DB pooling would handle this also. But when working through this we keep getting errors inside the application. For example, if the system has sat idle for a while and then a user clicks a transition button to process a workflow instead of the workflow processing we get a oracle error that max idle time has been exceeded.

So will Jim's response for the server.conf parameter alleviate this issue?

thanks.
Sascha Mohr
Acclaimed Contributor.

Re: Database IDLE_TIME requirement

You could give it a try, maybe it would suppress the error message.
You should also have a look at the admin report "Broker Performance"; it shows how many connections are in use and how many are "Total Available". The pool size should be 60 if you did not change it.
After migrating our system to release 8 we had an issue with connections that were no longer usable. At the end of the day there were more connections in use than users logged on to the system. The report helped monitoring that.