RESULT_RETENTION_TIME does not affect the data in 'job_run_event' - that is the 'log' data as indicated in the picture in the doc you reference.
how did you attempt to apply the 396 value for the RESULT_RETENTION_TIME ?
1 of 1 people found this helpful
Let me add some recommendations to this.
Don't set the RESULTS_RETENTION_TIME at the Job class level. Expand the Job class and set the RESULTS_RETENTION_TIME on the Job sub-classes. There are some jobs (like the Patch Catalog Update Jobs) you may not want to ever delete.
In your Job Smart Group, try changing the condition from "greater than 0" to "does not equal null"
The default is to have no value (null or blank) so greater than 0 might not work.
Review the section called "Job Run, Job Result, Job Run Event ?"
Job Run, Job Result, Job Run Event ?
Job Run and Job Run Event (Job Run Log) data are two different things and can be retained differently as noted. The implication is that it's possible to delete Job Run Event (Job Run Log) data while still leaving the record of the Job Run in the GUI/database. The screenshot below shows where you see the various data in the GUI.
It's entirely acceptable to remove Job Run Event/Log data and leave the Job Run, it just depends on the requirements of your environment.
The job_run_event retention is global - it's not set per job/jobrun. when you run the cleanupHistoricalData on jobrunevent, jobschedule, audittrail - the default setting will be used - which is 14 days (in the HK_CLEANUP_PROCEDURE table) or whatever you pass to the blcli command.
the RESULT_RETENTION_TIME actually governs two things. it governs the job run showing up in the gui ( the datestamp w/ the red x or green check) and it also governs keeping the 'results' for jobs that have results - eg snapshot, compliance, audit. but since when you delete the job run that means you can't see the job run log or the result anymore that distinction is kind of moot.
so your problem is that when you ran the cleanupHistoricalData JobRunEvent, it picked up the default retention period of 14 days and cleaned out that table based on that. but the job runs will still be there as will the results. just no log info for those runs > 14 days old.
Thanks for the help and clarification, I appreciate it.