User's Manual

Engine marks the database as RESOURCE PENDING. In either case, user action is required to
recover from the issue.
Workaround
HP recommends a regular database backup which will help to recover easily from such a scenario.
Choose from the following options that best suits the situation after consulting the database vendor's
guidelines.
• Back up the log.
• Free disk space so that the log can automatically grow.
• Move the log file to a disk drive with sufficient space.
• Increase the Maximum Size of the log file.
• Add a new log file to the database on a different disk that has sufficient space.
• Complete or kill a long running transaction.
Documentation or minor issues
The following are minor issues for Global Workload Manager.
SRDs defined when system was non-iCAP are unable to use TiCAP later
When an SRD (Shared Resource Domain) is defined on a non-iCAP system, and the system is later
modified to be an iCAP system and TiCAP can be used manually, the SRD does not make use of
TiCAP even if the policy used has it enabled.
Suggested Action
Perform the following steps:
• If the SRD is deployed when the change from non-iCAP to iCAP occurred, click Modify SRD.
You can see TiCAP option in the Manage systems and workloads systems and workloads tab.
• Click OK.
Warning message displayed on non-partitionable machines
On non-partitionable machines, when the gWLM agent is started, stopped, or restarted, the
following warning message may be displayed:
Warning: gwlmagent cimserver error, icapd down, or icap out of
compliance. First restart cimserver. Make sure icapd is running. If
this error happens again, consult gwlmagent man page for steps to return
to compliance.
Workaround
There is no workaround. You can ignore this message since this message is not valid on
non-partitionable machines where iCAP is not supported.
Remove old configuration data from the gWLM database
You can remove the old configuration data from the gWLM database using one of the following
ways:
1. Manually remove the old configuration data from the gWLM database.
Changes to workloads are stored in the gWLM database as configuration changes. The gWLM
database grows over time when workloads are modified.
NOTE: If workloads are managed by gWLM, historical monitoring data is stored in the
database, and using the commands listed under the workaround, you can delete this data as
well.
Documentation or minor issues 63