HP Capacity Advisor 7.2 User Guide

Verify that the HP Capacity Advisor Data Service has computed which
collections the current user is authorized to view
The HP Capacity Advisor Data Service might not yet have determined a list of collections that can
be viewed by the user. If the user is authorized to view some systems, then the list of authorized
collections should be available within 20 minutes.
If the checks discussed in the previous items have green check marks indicating working status,
you probably just need to wait a short time (<20 minutes) for this readiness check to pass.
Verify that the user's authorization for Capacity Analysis been processed by
the HP Capacity Advisor Data Service
Each user must be authorized to view the managed systems included for analysis. Capacity Analysis
regularly polls for new user authorizations on licensed systems. If you find that you have waited
longer than 20 minutes to have your user name recognized for access to licensed systems by the
Analysis software, check with your system administrator to confirm that the software configuration
correctly authorizes your user name for interaction with the systems licensed for Matrix OE
Verify that analysis metrics are available for licensed systems
A red “X” can indicate possible problems in system configuration for discovery and licensing. In
this situation, data is not being collected from the managed systems, and therefore cannot be
provided for analysis. A system administrator will need to check the status of discovery and licensing
in Systems Insight Manager.
Out-of-memory errors in the Java heap
A few situations can cause the Java heap to run out of memory.
Editing a scenario containing a large number of systems and/or workloads
When using an "Edit Scenario" screen in Capacity Advisor, the number of workloads included in
the scenario and the selected data range to use for analysis will affect how much memory is used
in the server process to read and analyze the scenario. Initially editing the scenario will invoke
the action to read and analyze the utilization data of all systems and workloads defined in the
scenario. The greater the number of systems and the longer the date range, the more memory and
time is consumed to read and analyze the utilization data. Suggested action: Experiment with
different combinations of systems, workloads, and data ranges to arrive at a manageable, but still
useful scenario.
Multiple users running simultaneous automated “what-if” actions
Executing an automated “what-if” action will cause an increased use of memory and CPU time for
the length time required to provide a solution. With multiple users running automated “what-if”
actions simultaneously, the server process can reach its maximum configured memory allocation.
Suggested action: See the Matrix OE install guide specific to your OS platform for more information
on tuning configuration parameters.
Running reports with very large data sets or when CMS is busy
During the execution of Capacity Advisor reports, consumed memory is monitored. Should consumed
memory reach a given threshold (85% of total JVM memory) the report execution stops and informs
you that there is insufficient memory to complete the report(s ) Users trying to create more modest
or even small reports could see this message if the rest of the system is busy. Remedies: Increase
heap memory size allocated to the JVM and/or reduce memory pressure on the CMS. Try to
generate the report again.
Out-of-memory errors in the Java heap 167