ResourceTargetContainerChanges table has suddenly growth too large
Last Updated March 04, 2019
The customer ha snoticed that the "ResourceTargetContainerChanges" table has many millions rows. "ResourceTargetContainerChanges" table doesn't release used space and doesn't decrease amount of rows.
This table had many changes on recent SMP versions that added ways to keep it under control. With the release of SMP 7.6 HF7, the following core settings entries (under C:\Programdata\Symantec\SMP\Settings\CoreSettings.config) were set to a value of 5 in order to avoid this increase in rows size:
In this particular instance, the core settings "ResourceTargetDeltaUpdateMode" and "ResourceTargetCompleteUpdateMode" were set to 1.
Value of 1 means: 0x01 = Purge 'unused' from [ResourceTargetContainerChanges] before any action starts and put them into [ResourceTargetInvalidate]
Using a value of 5 will allow the following actions (Which means 1 + 4 below): 0x01 = purge 'unused' from [ResourceTargetContainerChanges] before any action starts and put them into [ResourceTargetInvalidate]. 0x04 = force 'Purge Excess' to be be done at the end of update.
When the Delta and Complete Membership updates run, these core settings are taken in consideration to clear out unnecessary entries in this "ResourceTargetContainerChanges" table.
Note: Truncating this table should be fine but it is better to identify what process has been adding these extra rows and address that part first.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe