AnsweredAssumed Answered

DB_TRIG jobs are not working as expecting in CA ESP

Question asked by Santhosh_Gollapudi on Oct 1, 2017
Latest reply on Oct 3, 2017 by powdo03

Hi Everyone,


We have around 12 DB_TRIG jobs out of which:


  1. 3 are continuous monitoring jobs and working fine when condition satisfied.
  2. 9 are scheduled to trigger on 1st day of each month out of which only 2 are working when condition met and others 7 are showing executing but not completing (Please note that 2 jobs that are working are not same every month). And when I tried to delete the trigger from ESP, it is showing "Delete failed" message.


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.


Database: Oracle


Can someone please suggest me to fix this issue.