Current Limits And Conditions; Rollout Of Dynamic Npartitions Functionality In Hp-Ux 11I V3; Dynamic Npartitions, Virtual Partitions, And Integrity Virtual Machines; Requirement To Reset Workload Manager - HP Integrity rx7620 Configuration

sessions, or similar measures. Various capacity planning tools are available to match workloads to
hardware resource levels.
These considerations apply particularly to the Oracle Database products. If the memory allocated to
the Oracle Database is based on the full complement of cells in the partition, then the system will not
perform well if cells were to be deactivated. Instead, it would be appropriate to use the Oracle
tuning mechanisms, for example, the sga_target parameter, to make the memory footprint of the
database consistent with the size of the memory that will remain after cells are deactivated.

Current limits and conditions

Rollout of Dynamic nPartitions functionality in HP-UX 11i v3

Dynamic nPartitions operations will be available with HP-UX 11i v3 Update 1. HP-UX 11i v3 will run
successfully on servers that predate the release of the update. However, the new Dynamic nPartitions
operations will not be functional unless the firmware on the server is upgraded to the firmware that
supports the new features. The minimum firmware version for each platform that supports Dynamic
nPartitions is shown in the

Dynamic nPartitions, virtual partitions, and Integrity Virtual Machines

HP-UX 11i v3 Virtual Partitions enable dynamic operation through processor and memory migration
among vPars. However, Dynamic nPartitions operations cannot be performed to an nPartition that is
running vPars.
Integrity Virtual Machines also enable dynamic operation through processor and memory migration
among guest instances. However, the Integrity Virtual Machines Platform Manager as of September
2007 is based on HP-UX 11i v2. Therefore, Dynamic nPartitions operations cannot be performed to
an nPartition that is running Integrity Virtual Machines.

Requirement to reset Workload Manager

Workload Manager (WLM) exercises control over the hardware resources in a partition or a set of
partitions. WLM uses its own algorithms to adjust hardware resources to meet the stipulated service
levels. Those algorithms are perturbed if the system administrator uses Dynamic nPartitions to change
the composition of partitions being managed by WLM. Therefore, in cases where WLM is being
used, it is necessary to shut down the tool before a Dynamic nPartitions operation and restart the tool
after the operation completes.
The situation is similar with the global Workload Manager (gWLM). gWLM expects to have complete
control of the CPUs, or cores, available on a system. However, when you must make manual
adjustments to system resources, you can do so as follows:
1. Undeploy the SRD containing the systems that you want to adjust
2. Perform the Dynamic nPartitions operations
3. Re-create and re-deploy the SRD

Integration with instant capacity

Dynamic nPartitions is fully integrated with instant capacity functionality. Any processor licensing
restrictions imposed by instant capacity are respected by Dynamic nPartitions. For that reason, a cell
online activation operation is possible only if there is at least one processor license available in the
cellular complex.
Firmware Matrix.
9