The taraping command line utility tests TARA server health by testing TARA server connectivity interactively or in a script. Testing is performed externally from the TARA clients.
The taraping parameter indicators are case sensitive, therefore use the correct case when specifying parameters. Also, specify each parameter only once in the command-line.:
/opt/teradata/tara/nbubar/taraping [-s -p -v] -s <TARA servername> - (optional) -p <port> - (optional) -v <verbose level: 1|2|3> - (optional)
The following table describes taraping parameters.
Parameter | Description | Required |
---|---|---|
-s <TARA servername> | Specifies the TARA server host where the job to be launched is stored. The TARA servername value can be a host name (for example, taraserver1 or localhost) or an IP address of a host (for example, 153.64.14.142). Example -s localhost Example -s 153.64.14.142 TARA server name defaults are:
|
No |
-P <port> | Specifies the port number that the TARA server is running on. If the TARA Server port is changed to a different number, this option has to be specified with the correct TARA Server port number. The default is 54323. |
No |
-v <verbose level: 1|2|3> |
Specifies the level of debug information to display. There are three valid debug levels (1, 2, and 3), with higher values providing more extensive debug information. More extensive information is typically only useful for utility developers when gathering information about a reported problem. The verbose level default is 1, which generates no display unless the test fails. |
No |
The following table describes taraping return codes.
Return Code | Description |
---|---|
0 | Successful |
255 (-1) | Failed |