We have around 12 DB_TRIG jobs out of which:
We thought issue was with db.connectionPool.maxSize parameter where we have default value as 5. We changed it to 0 and restarted the agents but still not working. Our DB can accept 30000 connections. During our work around we identified that agent is accepting only 5 active DB connections and though others are showing as executing they don't have any active DB monitor session.
Can someone please suggest me to fix this issue.
Have you verified that the database trigger is active in Oracle? Someone could have deleted it from Oracle. Any that are missing will need to be retriggered.
9 scheduled jobs are triggered at once and only 2 get succeeded when condition met. We have tried to update a row for one in other 7 but not worked. It is allowing max 5 active DB sessions only even we set the maxPool value to 0.
I don' t think the db.connectionPool.maxSize is related to this issue. I won't go into detail here...but the DB_TRIG is not creating a persistent connection. To verify this you could always try setting it to 20. I would set this back to the default.
I think it may be best to open a case. Someone will probably need to look at the agent logs.
Did someone look at Oracle database and see what triggers are getting set?
If you would like you can give me a call.
Thank you Don for assistance. We are in process of testing the case with setting the value to 20. I will give you a call if that didn't work and proceed further.