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

18
This time the rights seizure has resulted in 27 available core usage rights being held by the Group Manager (15 seized
from Db1; 12 seized from Db3). As before, the failover is not complete until the administrator activates cores on
server 2. In this case, the administrator chooses to activate 12 additional cores for Db2, and only eight additional
cores for Db4, as that is all that is needed to run each application. Those commands, run on Db2 and Db4, are:
db2> icapmodify -a 12 [-t] OR OA> icapmodify –p 2 –a 12 [-t]
db4> icapmodify -a 8 [-t] OR OA> icapmodify –p 4 –a 8 [-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 11 shows this state when the failover from server 1 to server 2 is complete.
Figure 11. HP GiCAP failover after usage rights seized (complete outage example)
Note that the Group Manager still has seven available core usage rights. This is because the rights seizure from
OA1 made 27 core usage rights available, but only 20 additional usage rights were needed to run the applications on
partition Db2 and Db4 of OA2. These available core usage rights could be used by other members of the group (if the
group contained more members), or the administrator could choose to fully activate all cores on Db4.
Db1: 2 blades,
1 reserved core
Server 1
R
A
Active core
Inactive (iCAP) core
Db2: 2 blades, 4
active and 12 iCAP
cores
Server 2
A A
A A
C C
C C
C C
C C
C C
C C
Db4: 2 blades, 8
active and 8 iCAP
cores
Reserved core usage right
ap1: Group Manager
A A
A A
A A
A A
C C
C C
C C
C C
A
A
A
A
R
Db3: 2 blades,
0 active cores
C
Core usage right from seizure, with time expiration
A
A
A