HP Instant Capacity Version 10.x User Guide (762794-002, June 2014)

after a partition reboot, unassigned from partitions, or additional cell usage rights may be
purchased for permanent activation.
• More memory active than expected
'More memory active than expected' means that the amount of active memory across the
complex exceeds the available memory usage rights. To find out how much inactive memory
is expected on the complex, run icapstatus and look at the global amount of memory
without usage rights. Typically, this exception occurs when a newly added cell without usage
rights is activated, but it may also occur when a cell with a small amount of memory is
deactivated and replaced with a cell with a greater amount of memory. To correct this
exception, one or more cells will have to be deactivated to show the appropriate amount of
memory. This can be done by using parmodify to set the use_on_next_boot flag for an
assigned cell to “n”, followed by a partition reboot. Alternately, cells may be turned off after
a partition reboot, unassigned from partitions, or the appropriate amount of memory usage
rights may be purchased for permanent activation.
• Negative temporary capacity balance
'Negative temporary capacity balance' means that the authorized temporary capacity (TiCAP)
balance on the system has been depleted and continued use of core(s) without usage rights
has caused additional (unauthorized) temporary capacity to be consumed. To correct this
exception, first correct any 'More cores active than expected' exception so that the temporary
capacity balance does not continue to grow more negative. Then, purchase additional
temporary capacity and apply the temporary capacity codeword to the complex. Alternately,
purchase additional usage rights to match the number of core(s) consuming temporary capacity
and apply the Right to Use (RTU) codewords to the complex.
The following example shows an email exception report when more cores than expected get
activated and temporary capacity balance becomes negative.
Handling compliance exceptions 117