IMAN job conf exists, but job unavailable & unscheduled in UI (3 replies)
Arline, it is likely that someone deleted it.
If there is no entry in the drop down then it has been removed.
Whilst not trying to don the tin cap, it is likely your customer has then attempted to re-add the integration by copying a really old integration back into the jobConf folder.
Does the file you found in the jobConf folder have anything in it? Or is it a tiny file?
Thanks
Thanks for the reply and for helping me understand this.
So the file in JobConf was perfect - it was the exact integration I needed. When I loaded it, it gave me the 'upgrade' notification, and then ran without any issue. So, does that answer your question?
So confusing. Thanks for the input.
Arline, it does to some extent....
- Someone deleted it (removing it from both the database and JobConf folder).
- They restored an older version of the file....this would have not updated the database.
You then re-imported.
IMAN v4.2
I've never seen this before and am just seeking to understand how this is possible.
I have a job that runs weekly without issue.
Last week, the users complained that the job did not run.
I checked IMAN and could not even locate the job within the UI in order to load it. Accordingly I also could not 'schedule' it .
I found the job conf file in the Conf folder.
When I uploaded the Job Conf file, I got the unexpected message that that version of the job had been upgraded to the latest version. But their upgrade was 6 months ago. How could it be that this job was running successfully for months, and then one day both stopped running, disappeared from the designer, and reverted back to the older version?
It seems to me that this isn't just an issue of a user inadvertently deleting the job from the UI.
But I'm not clear on possible root causes.
Can anyone share their thoughts?
Thank you.