We recently upgraded to 13.3 and updated all the db agents to 13.3. After the upgrade, this was not working, but I found the problem to be job_queue_processes that was set to 0 for the upgrade. After updating that to 50 rather than 0, this was working. At some point since then, it stopped working. I don't know the exact time because we rotate on call and I don't pay attention to this particular page when I'm not on call. The only items that should have changed since upgrade are quarterly db patches for the repository and operating system updates for the repository and oms hosts.
Things I've found online and checked:
job_queue_processes > 0 on repository; mine is set to 50
metrics not measured on database targets (throughput and wait bottlenecks); we only have one monitoring template and it's being checked through that and i've spot checked several databases and those metrics are being gathered
So far, I've had no luck with MOS or google or any other search facility. Before I open an SR, I thought I would bring it here as I can't imagine I'm the first to experience this and it not be one of the items already checked and dismissed. Oh, not sure if it matters or not, but right now the DB repository and all the DBs monitored are at version 12.1.0.2.x on windows (2012 R2) and the 13.3 OMS is on red hat linux (centos 6.10) .
Thanks in advance for any insight.
-Kelly