Cost-Effective High-Availability Solutions with HP Instant Capacity on HP-UX

Figure 10 displays the state after the administrator has issued the two commands to seize usage rights
from each failed partition.
Figure 10: GiCAP failover after usage rights seized (complete outage example)
This time the rights seizure has resulted in ten available core usage rights being held by the Group
Manager (six seized from db1; four 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 six
additional cores for db2, and only two additional cores for db4, since that is all that is needed to run
each application. Those commands, run on db2 and db4, are:
db2> icapmodify -a 6 [-t]
db4> icapmodify -a 2 [-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 “Temporary
capacity and rights seizure” sub-section.
21