- In the Unity Setup portlet, click the Session Routing tab.
- Click the Error Profiles tab.
- Click .
- Next to Error Profiles, click .
- In Error Profile, enter a new name or leave the default name in the box.
- Next to Error Codes, click add error codes.
In Add Error Code, complete the following:
Option Description Error Code Error identification code number. Description Description displays if the error code matches a Teradata error code.
If there is no match, this box is blank.
User Comments [Optional] Additional information about the error code.
Select an the action for Unity to perform if the specified errors occur:
Action Description Retry (same system) For both managed and passive session routing, the Retry Error Action retries the request on the same system where it was originally executed. The query is retried up to three times by default.
For managed sessions (sessions associated with a managed routing rule), only Read requests are retried, and only if it is an implicit transaction, or if the Read request is the very first request in an explicit transaction. For passive sessions, all Read/Write requests are retried (if the error code or action matches), and the type of transaction (implicit or explicit) does not affect the decision.
Resubmit (other system) Resubmit means trying the query on another system.
For managed sessions: if an error code indicates resubmit, the query is submitted to another system per the Read routing rule associated with the routing rule. For passive sessions, a resubmit closes the session on the current system, opens the session on the new system (chosen per routing rule), and then the query is attempted on the new system.
Retry then Resubmit Combination of Retry Error Action and Resubmit. Exit Terminates the session.
- Click Save.
- Verify the error code is added to the Error Profile list. You can now associate this error profile with a routing rule.
- Click Close.
The following steps describe how to create an error profile that you can associate with a routing rule.