The evaluation of Software Policy (with Ad-hoc evaluation target enabled) do not generate a SD Job container for some computers. These computers appear in the Software Policy violator folder but no SD Job are created for them.
Client Automation - All versions
A possible cause is if some computers have the lock "Locked By Eval Update" set
This lock is set when a "Target Evaluation" task is created for a computer and is removes when the "Target Evaluation" task is executed.
But if a problem occurs (crash of process for example) the lock could remain and is never removed.
Following SQL Query returns the computer which have the lock "Locked By Eval Update" set but are not in a "Target Evaluation" task :
SELECT agent_name
FROM ca_agent
WHERE agent_type=1
and object_uuid in (SELECT objectid FROM usd_target WHERE locks & 64 = 64)
and object_uuid not in (SELECT comp FROM usd_link_grp_cmp WHERE grp in (SELECT objectid FROM usd_cmp_grp WHERE objectid in (SELECT referredentity FROM usd_task WHERE tasktype=13)))
ORDER BY 1
If the SQL Query above returns some rows, following SQL Query could be executed to remove the locks :
UPDATE usd_target set locks=locks-64 where locks & 64 = 64
and objectid not in
(SELECT comp FROM usd_link_grp_cmp WHERE grp in (SELECT objectid FROM usd_cmp_grp WHERE objectid in (SELECT referredentity FROM usd_task WHERE tasktype=13)))
Script check_sd_tables has been updated to include this correction.
So alternate solution is the execution of this script.
See this article for more information :
How to clean SD tables from lost rows or data inconsistency