Implement high-availability solutions with HP Instant Capacity - easily and effectively

15
These usage rights are available to be migrated to other partitions, under control of the Group Manager, as shown
in figure 8.
Figure 8. HP GiCAP failover after rights seized (partial outage example)
To complete the failover operation, the administrator now needs to activate up to a maximum of 12 cores on server 2,
using the available usage rights associated with the Group Manager. To activate cores on Db2, log in to that system and
run the following command:
db2> icapmodify -a 12 [-t]
Or, run the following command on the OA:
OA> icapmodify –p <partition number> -a 12 [-t]
Use the –t option if you want to allow the use of TiCAP to activate cores in the event concurrent operations made the
just-released usage rights unavailable. For more information, see the “HP TiCAP and rights seizure” subsection.
Figure 9 shows the state after the core activations on server 2, when the failover from Db1 to Db2 is complete. Db1 is
left with 0 cores active and Db2 has all cores active.
Db1: 2 blades, 16
inactive cores
Server 1
A
Active core
Inactive (iCAP) core
Db3: 2 blades, 12
active, and 4 iCAP
cores
A A
A A
A
A
A A
A A
A A
Db2: 2 blades, 4
active, and 12 iCAP
cores
Server 2
A A
A A
Db4: 2 blades, 8
active, and 8 iCAP
cores
ap1: Group Manager
A A
A A
A A
A A
A A
A A
A A
A A
A A
A A
AAAA