The event "job not ready by start time" will not be of any use in this case.
We have the same problem (we're on 6.1.384) , and we run the below query as an "OracleDB" job. It returns an integer, and rather than look at the exit code, we set up an output scan so that it simply fails if it returns anything other than '0'. That's when the events to trigger an alert as well as an email get fired. Then another event to mark itself as 'Completed Normally' so it can run again on its 20-minute cycle. It works well. We allow for 10 minutes in 'Launched' status, however, because we have seen some jobs go 'Active' after 5 minutes in launch status....but generally if it hasn't gone 'Active' after 10 minutes, it never will without manual intervention.
And (sysdate - jobrun_stachgtm)*24*60 > 10
We have a custom view that shows all jobs in 'Launched' status, for the operator to refer to for details. We also run the below query as part of a "status report", basically a group of queries, every hour around the clock. This is to help the scheduling team track the problem in more detail:
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...