Environment
Novell ZENworks Configuration Management 11.2 Database
Novell ZENworks Configuration Management 11.2 Content
Novell ZENworks Configuration Management 11.3
Novell ZENworks Configuration Management 11.4
Novell ZENworks Configuration Management 11.2 Content
Novell ZENworks Configuration Management 11.3
Novell ZENworks Configuration Management 11.4
Situation
High utilisation (utilization) is seen on the database server, but not the primaries or satellites.
A query similar to the one below is seen using a high proportion of the database CPU, this indicates Batch Content from satellites:
(@P0 int,@P1 varbinary(8000),@P2 int,@P3 varbinary(8000),@P4 int)select distinct linkedcont0_.ContentUID as col_0_0_, content1_.AliasedContentUID as col_1_0_ from zLinkedObject linkedcont0_, zContent content1_, zAssignableContentObject assignable2_ inner join zZENObject assignable2_1_ on assignable2_.ZUID=assignable2_1_.ZUID where linkedcont0_.discriminator='Linked Content' and linkedcont0_.ContainingObjectUID=assignable2_.ZUID and linkedcont0_.ContentUID=content1_.ZUID and (assignable2_.SatelliteRep= @P0 and ( @P1 in (select satellites4_.SatelliteServers from zACOSatelliteServers satellites4_ where assignable2_.ZUID=satellites4_.id)) or assignable2_.SatelliteRep= @P2 and ( @P3 not in (select satellites7_.SatelliteServers from zACOSatelliteServers satellites7_ where assignable2_.ZUID=satellites7_.id)) or assignable2_.SatelliteRep= @P4 )
Once content replication is complete the content sync status needs to be updated for any changed content, by default this happens every 5 minutes. In large Zones or environments where content is rapidly changing (Bundles, Patches) the 5 minute cycle may be too intensive, meaning the previous cycle may not have finished before the next one starts.
Please note this content sync status (sync interval) is different from the content replication schedule.
A query similar to the one below is seen using a high proportion of the database CPU, this indicates Batch Content from satellites:
(@P0 int,@P1 varbinary(8000),@P2 int,@P3 varbinary(8000),@P4 int)select distinct linkedcont0_.ContentUID as col_0_0_, content1_.AliasedContentUID as col_1_0_ from zLinkedObject linkedcont0_, zContent content1_, zAssignableContentObject assignable2_ inner join zZENObject assignable2_1_ on assignable2_.ZUID=assignable2_1_.ZUID where linkedcont0_.discriminator='Linked Content' and linkedcont0_.ContainingObjectUID=assignable2_.ZUID and linkedcont0_.ContentUID=content1_.ZUID and (assignable2_.SatelliteRep= @P0 and ( @P1 in (select satellites4_.SatelliteServers from zACOSatelliteServers satellites4_ where assignable2_.ZUID=satellites4_.id)) or assignable2_.SatelliteRep= @P2 and ( @P3 not in (select satellites7_.SatelliteServers from zACOSatelliteServers satellites7_ where assignable2_.ZUID=satellites7_.id)) or assignable2_.SatelliteRep= @P4 )
Once content replication is complete the content sync status needs to be updated for any changed content, by default this happens every 5 minutes. In large Zones or environments where content is rapidly changing (Bundles, Patches) the 5 minute cycle may be too intensive, meaning the previous cycle may not have finished before the next one starts.
Please note this content sync status (sync interval) is different from the content replication schedule.
Resolution
On each satellite increase the default sync status time from 5 minute. The examples below use 60 minutes.
Linux Satellites
In this file: <agent_install>/conf/xplatzmd.properties
Add this string: UPDATE_SYNC_INTERVAL=60
Restart the agent service
Windows Satellites
Within this branch of the registry: HKEY_LOCAL_MACHINE\Software\Novell\ZCM
Create a String key called: UPDATE_SYNC_INTERVAL
With a value of: 60
Restart the agent service
Linux Satellites
In this file: <agent_install>/conf/xplatzmd.properties
Add this string: UPDATE_SYNC_INTERVAL=60
Restart the agent service
Windows Satellites
Within this branch of the registry: HKEY_LOCAL_MACHINE\Software\Novell\ZCM
Create a String key called: UPDATE_SYNC_INTERVAL
With a value of: 60
Restart the agent service
Additional Information
The loader-messages.log from the parent primary will show how often this is running:
[setContentSyncStateBatch complete, time: 349882ms, serverUID: ab10b6f7dc82674393dfee1328d2a6c0, size of contentIDs: 12428, thread: 256]
[setContentSyncStateBatch complete, time: 349882ms, serverUID: ab10b6f7dc82674393dfee1328d2a6c0, size of contentIDs: 12428, thread: 256]