- In the Unity Setup portlet, click the Session Routing tab.
- Click the Routing Rules tab.
- Click .
- Next to Routing Rules, click .
In Rule Name, type the name for this rule.
Create a name that identifies the type of routing used for sessions that match this rule. For example, readonly-rpref indicates the routing rule is for Read-only Preferred routing.
- Select Managed.
For Read-only routing, use the Read Routing list to select Default or Preferred and check two or more Teradata systems under the Read column.
Option Description Default Unity selects the system with the shortest work queue and sends the Reads to that system. Preferred All Read requests are sent to the first system in the list. If that system is unavailable, the Read session fails over to the next system in the list. There is no load balancing.
To specify where new objects are created, use Create Routing.
All writes are always sent to all systems on which the object exists. If an object exists on a system that is not part of the Write list, an error message appears.
Option Description Preferred New objects are created on the first system in the list. If that system is unavailable, new objects are created on the next system in the list. There is no load balancing. Balanced New objects are created on one of the systems specified in the system list. The system is picked at logon and all new objects for a given session are always sent to the same system. Unity balances the systems for each logon session. All New objects are created on all systems. Default routing is applied.
Select the systems to use to send the reads and writes.
If a system is selected for Write, it must also be selected for Read.
- Using the Error Profile list, select the name of the error profile to associate with this routing rule.
The new routing rule is added to the summary table.