Cluster and instance states can change:
Manually, when you execute a state change using the online, offline, failover, and failback commands; and sometimes with the action command
Automatically, as a result of system changes
The initial state of the cluster or instance can dictate whether or not a state change is valid, and even the final state. Table 6-2 shows how different actions, executed manually, and states interact. States are described in rows; actions are described in columns. Each cell represents the new state when an action is applied to a logical cluster or instance in the initial state.
offline |
online |
time_wait |
failed |
inactive |
|
|---|---|---|---|---|---|
Online |
online |
online |
online |
||
Offline |
offline/time_wait |
offline |
offline |
||
Failback instance |
online |
online |
online |
||
Failback cluster |
online/time_wait |
offline |
offline |
||
Failover instance |
online |
online |
online |
||
Failover cluster |
online/time_wait |
offline |
offline |
||
Cancel action |
online |
||||
Modify wait |
time_wait |
||||
Deactivate |
inactive |
inactive/time_wait |
inactive |
States can also change as the result of system changes. Table 6-3 shows the effects of different system changes on the state of the cluster or instance.
offline |
online |
time_wait |
failed |
inactive |
|
|---|---|---|---|---|---|
Instance joins cluster |
online if automatic start-up is configured |
online if automatic start-up is enabled |
|||
Graceful shutdown |
time_wait |
||||
System failure |
failed |
failed |
|||
Shutdown with nowait |
failed |
failed |
|||
Failover selection |
online |
Logical cluster states are not retained following a
total cluster restart. For example, suppose you execute the offline command
for a logical cluster that is in automatic start-up mode. The cluster
is in the online state after you restart it.
