we need to delete connections, but they still refer to jobs, that I can't find - but querying the database tells me that the jobs are "dirty".How do I delete these jobs ?
We are new to Tidal (6.1) and create jobs or jobgroup dependencies as:default is to use Match OccurrenceLast Occurrence is only used for specific jobs that are demanded adhocThis gives us some problems when we manipulate jobs - suddenly we have non-...
I sometimes end in a situation where a flow of jobs are "out of sync" - meaning that they normally run sequentally and therefore always have similar instance numbers. They have dependencies based on "Match Occurrence" - for many r...
I just had the same problem. Reason was a full transaction log (MSSQL). And this might have been caused by a transaction log backup running simultaniously with shift to new day.
I think you need to use SQL.
Note that all jobs by default has a max runtime of 1 (minute) - it apparently Means: don't check.
With a MSSQL DB SQL could be:
SELECT [jobdtl_id], [jobdtl_maxrun]
FROM [Admiral].[dbo].[jobdtl]
WHERE jobdtl_maxrun > 60...
We use an external event handler (CorreLog) to handle complex actions. From TES we create a job event, that sends a message to CorreLog including all necessay parameters to impose actions.Many of these actions are sacmd commands, SMS (text messages...
