how often are you running complianceResult cleanup? is it successful ?
Assign operator will not solve this problem.
Table COMP_ENTRY_RESULT_DETAIL stores result of each condition, of each rule.
Assign operator assigns value to LOCAL Property of component template, which will not get stored in component template.
It runs Daily during the week as part of the Daily-CleanUp routine, with a retention of 90 days.
Info Fri, 20 Nov 2015 20:02:24 Started running the job 'Cleanup ComplianceResult' with priority 'NORMAL'
Info Fri, 20 Nov 2015 20:02:27 Executing work item NSH Script Job:Cleanup ComplianceResult;
Info Fri, 20 Nov 2015 20:02:28 Execution Starting: Cleanup - ComplianceResult
Info Fri, 20 Nov 2015 20:02:28 Command: Delete cleanupHistoricalData ComplianceResult 90 null null
Info Fri, 20 Nov 2015 20:02:36 [Fri Nov 20 20:02:36 CET 2015] Executing stored procedure: ComplianceResult
Info Fri, 20 Nov 2015 20:05:04 [Fri Nov 20 20:05:04 CET 2015] Finished Executing stored procedure: ComplianceResult
Info Fri, 20 Nov 2015 20:05:04 voidResults:
Info Fri, 20 Nov 2015 20:05:04 Execution complete: Cleanup - ComplianceResult
Info Fri, 20 Nov 2015 20:05:04 Exit Code 0
Info Fri, 20 Nov 2015 20:05:05 The job 'Cleanup ComplianceResult' has succeeded
is there any other way to get round this problem ?
what is the result_retention_time property set to on most of your compliance jobs. the cleanup should use the retention setting on the job, not what's passed to the blcli.
We have the 90 days also set for the result_retention_time on the "Job" level in the property dictionary.
Checking our "big" compliance Jobs, that's also set there, so not overwritten etc.