Went to the Schdeule and the report was enabled, so tryed to disable and got the following message :
ERROR: No such job exists in JRM. Query for the available HUM jobs.
I was able to re-enable without issue.
But still get the same error message when going to report management.
You may need to wait an hour (the default) before trying the Quick Report again. However, if you try disabling the report again, do you get the same error?
I have done a bit more tetsing with the Quick report Schedule.
When I disable the report and apply, I still get the JRM error message.
If I move away for the screen and come back the JOb is still showing as enabled although I did not re-enable.
Post the jobattribute.xml and jobattribs-mapping.xml files from NMSROOT/MDC/tomcat/webapps/upm/WEB-INF/classes/com/cisco/nm/upm/properties/common.
Shutdown the UPMProcess daemon, then clear out the upm_process.log, then restart UPMProcess. Now you'll need to wait. UPMProcess will start taking a lot of CPU as it runs through all the jobs on the system. When it becomes idle, post the new upm_process.log.
There was a problem adding all of the Quick Report jobs to JRM at the time of the upgrade. Now, HUM mistakenly thinks it doesn't need to add the missing job. If you reinitialize the upm database, restarting Daemon Manager should properly add all the Quick Reports. However, you will lose all of your HUM historical data. This may be fixable with some database surgery as well, but you will need to contact the TAC to get the steps.
To reinitialize the upm database run:
NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=upm dmprefix=UPM