NetIQ AppManager 7.0.x
What changes take place when the AppManager Services are cold started?
The following changes take place when each of the AppManager services is cold-started:
NetIQ AppManager Management Service (NetIQms): When this service is cold-started, the local cache (Persistent IOC) in the Management Server is cleared. This cache contains data, events, and job status information waiting for insertion into the AppManager repository. Under normal operating conditions this cache is empty. It is only during periods of high traffic that the cache will contain some information. A cold-start may be necessary ONLY if the cache contains corrupt information that the management server is unable to process correctly.
NetIQ AppManager Client Resource Monitor (NetIQmc): When this service is cold started, the list of jobs that the agent has retained locally (within the MCJobTable of the Local Repository) is cleared. Any data or events that the agent may be retaining due to a failure to upload the information to the management server is NOT deleted. Cold-starting this service will NOT delete the jobs back in the AppManager Repository, but they may appear in an ERROR state, and events indicating "MC Can't locate job" will appear in the Operator Console. The jobs can simply be restarted from the Operator Console. A cold-start of this service is usually necessary ONLY when one or more jobs on the agent may be experiencing or causing problems with the agent. The agent will lose any resource dependency information that was previously set. It will be necessary to run the AMADMIN_SetResDependency on the agent following a cold-start in order to restore any desired resource dependencies.
-o - clears the following tables in the local repository: MCJobTable and MCRscTable
-oa - clears the following tables in the local repository: MCJobTable, MCRscTable, and MCSiteComm
NetIQ AppManager Client Communication Manager (NetIQccm): when this service is cold-started, any data and events collected by the agent but not yet sent to a management server are deleted from the local repository of the agent. By using the "-oa" switch, the CMComm table is ALSO cleared on the agent. This table contains a record for each management server communicating with this agent, and whether the agent is to use name resolution or a cached IP address when communicating with the management server.
-o - clears the following tables in the local repository: CMData and CMEvents
-oa - clears the following tables: CMData, CMEvents, and CMComm
For further details about cold starting the NetIQ AppManager Client Resource Monitor Service, refer to the following Article: