You may start experiencing a situation where security updates are failing to be created after a differential hierarchy replication is completed. Upon investigation of the Symantec Management Platform (SMP) logs, you notice many red errors. The following is one example of an error you may witness:
Unable to generate policy XML for item:
Invalid object name 'Inv_Software_Update'.
Release: 8.x Hierarchy Environment
Dataclass on the parent SMP was at one point deleted, and while restored, is still in the hierarchysingulartask table. With the Data class being in the HierarchySingularTask as a Delete, every Replication cycle will cause it to be deleted as Replication tries to push changes down the hierarchy.
In this particular situation, there was no repair of the Patch Management Solution.
NOTE: Repairing Patch Management would replace the Import / Export steps below. Deleting rows from HierarchySingularTask needs to occur so that the replication cycle will not case the Inv_Software_Update table to be deleted on the child NSs.
To verify this issue
Run the following SQL query against the Parent SMP's database: select * from HierarchySingularTask where Guid = '78e7a87a-5d18-4ce5-8053-471ccb68130e'
Notice that the Task column shows Delete. If so, this is the problem.
To resolve this issue:
On the Parent SMP server:
delete hst from HierarchySingularTask hst
join vItem vi on vi.Guid = hst.Guid
where vi.Guid is not null
On the Child SMP server:
After following these steps, when the differential hierarchy runs again, the data class will no longer be deleted on the child SMP. It may be necessary to recreate some software update policies on the Parent.