HP Global Workload Manager 7.3 and 7.3 Update 1 User Guide

gwlm history --purge=30
2. Automatically remove the old configuration data from the gWLM database.
To remove data automatically, the following properties must be set in the gwlmcms.properties
file :
com.hp.gwlm.cms.db.history.keep
Valid values:
0 : Do not remove any historical data (default).
1 - 10000 : The number of days for which history will be retained.
Any historical data older than the specified number of days will be removed from the database.
This Property controls the number of days for which the historical data for configuration and
monitoring will be retained in the database. Data present beyond the specified number of days is
automatically purged from the database on a daily basis.
NOTE: Before setting the value of this property to any value other than zero, ensure that you
manually run the following command with specified conditions:
gwlm history --purge
This command must be executed at a time when the database is not heavily loaded. The value of
com.hp.gwlm.cms.db.history.keep must be used as the parameter to gwlm history
--purge command.
This ensures that the first run of the automatic purge does not affect database operations, even if
data needs to be removed for a long period of time. Since the automatic purge is performed on
a daily basis, purges after the initial one removes only a single day’s data. This reduces the load
on the database.
Cell-local processors and iCAP environment
Using cell-local processors with virtual partitions inside an nPartition that uses (iCAP) leads to failure
of the icod_modify command.
Workaround
Do not assign CPUs using cell specifications. Consider assigning CPUs to the virtual partitions
using a hardware path.
Alternatively, to use cell-local processors, update to vPars A.04.04 on HP-UX 11i v2 (B.11.23) or
to vPars A.05.01 on HP-UX 11i v3 (B.11.31).
CMS is slow to respond
The CMS is slow to respond.
Workaround
Time a gwlm list command on the CMS. If it takes more than 10 seconds, perform the following
steps:
1. In the file /etc/opt/gwlm/conf/gwlmcms.properties (HP-UX) or
install-path\VirtualServerEnvironment\conf\gwlmcms.properties
(Windows), increase the CMS database cache size by increasing the value of the
com.hp.gwlm.cms.cachesize property by 25%. (The cache is more memory efficient if
the size is near a power of 2. If your target cache size is close to a power of 2, round it up
to the next power. For example, if your target cache size is 60,000, round it up to 66,000.)
2. Stop and restart gwlmcmsd using the following commands.
NOTE: Stopping gwlmcmsd disables HP Matrix OE visualization and Capacity Advisor.
# gwlmcmsd --stop
# gwlmcmsd
Documentation or minor issues 63