Purpose
For managed routing sessions, the command changes the designated Teradata system for the preferred session routing rule to the next available system in the ordered list.For passive routing sessions, the command causes the session to move from the current system to the next system, as per the ordered system list associated with the routing rule.
Syntax
SESSION FAILOVER sessionId | routing;Parameters
- sessionid
- Unique session identifier (ID).
- routing
- Unique routing rule identifier.
Usage Considerations
On sessions tagged for failover, the failover only occurs on the next request.
Example
At the bcmadmin prompt:
| Input | Description |
|---|---|
| SESSION FAILOVER 1001; | To force a failover of session 1001 |
| SESSION FAILOVER prefReadOnly; | To force a failover of all sessions using the prefReadOnly routing rule |