Cluster and instance states

A logical cluster and each instance in the cluster can have different states.

A logical cluster has an overall, or global, state that determines, for example, whether the cluster is offline or online.
A logical cluster also has an instance state that describes the state of a particular instance as it is perceived by a logical cluster. For example, an online logical cluster may be online on its base instances and offline on its failover instances. This state may be independent of the actual Adaptive Server state, as a logical cluster may be offline on an instance that is actually up and running.

There are five states that are visible to the user. These states apply to a logical cluster state as well as the instance state. Table 6-1 describes each state at the global and instance levels.

**Table 6-1: Logical cluster states**
State	At the global level	At the instance level
online	A logical cluster is online and running on one or more instances.	The online logical cluster is accepting and managing connections on the current instance.
offline	A logical cluster is not running on any instance.	A logical cluster is not running on the current instance, which cannot accept connections or consume resources.
inactive	Similarly to the offline state, a logical cluster is not running on any instance. Inactive logical clusters are not started automatically and do not participate in failover. The cluster achieves the inactive state only through the deactivate command. Once inactive, the cluster comes online only through the online command.	A logical cluster is not running on the current instance, which cannot accept connections or consume resources. In addition, the inactive instance cannot fail over and is not brought online after an automatic start-up. This state is achieved only via the deactivate command.
failed	Similarly to the offline state, a logical cluster is not running on any instance. A logical cluster moves to the failed state when its active instances are shutdown with nowait or encounter a system failure when no failure resources are available.	A logical cluster is not running on the current instance, which cannot accept connections or consume resources. The failed state is reached via a shutdown with nowait or system failure.
time_wait	A transition state between online and offline or inactive. An online logical cluster must enter the time_wait state before becoming offline or inactive. During this time, any new connections are routed according to the down-routing mode, and existing connections migrate or disconnect.	A transition state between online and offline or inactive. When a logical cluster is online for an instance, it must enter the time_wait state before becoming offline or inactive. In the time_wait state, no new connections can be routed to a logical cluster or instance, but existing connections continue to run until they migrate or disconnect.