- A set of operating rules that can be used to control how your system allocates resources. A state is the intersection of a health condition and a planned environment.
- Health Condition
- The condition or health of the system. For example, system conditions include system performance and availability considerations, such as nodes down at system startup. Unplanned events such as system, workload, user-defined, and combination events activate the health conditions.
- Planned Environment
- The kind of work the system is expected to perform, usually representing time periods or workload windows when critical applications, such as a load or month end, are running. For example, if you have many system users on weekdays, but run batch jobs on the weekends, allocate system resources differently during the week than you do on weekends by creating two planned environments: Weekdays and Weekends. Planned events such as period, user-defined, and combination events activate the planned environment.
In Teradata Database 15.00 and later, the IWM systems have options for planned environments, but not for unplanned events or health conditions. In Teradata Database 14.10 and earlier, the IWM systems have no options for custom states, health conditions, planned environments, or state-specific values for query sessions, filters, and throttles.
In the state matrix, create planned events, unplanned events, health conditions, planned environments, and corresponding states specific to your business situation. Update the state matrix at any time to reflect business and system requirements, or trigger priority changes and other system changes.
The Normal health condition, Always planned environment, and Base state are defaults. The defaults apply unless planned or unplanned events occur, triggering other configured states. The defaults cannot be deleted or moved within the state matrix. Like any state, the Base state can be used in multiple cells of the matrix.
Following is an example of the States view on a SLES 10 TASM system.
Any states you create use the default settings. You can set new values on the state-specific settings tabs in workloads, filters, throttles, query sessions, and utility limits to override the default settings.
- Consistent, peak workload hours or days where priority management must be strictly assigned and enforced
- Load or query times where priority tasks must finish within a specific time frame
- Conditions where resources must be managed in a different way, such as giving higher priority to critical work when system health is degraded