Client Configuration Basics for Teradata
The client side configuration is wholly contained in the “hosts” file (/etc/hosts on Unix orwinnt\system32\drivers\etc\hosts on Win). Since INFA does not run on NCR Unix, one should notever have to deal with the server side. Teradata uses a naming nomenclature in the “hosts” file. The name of the Teradata instance (i.e. tdpid – Teradata Director Program Id) is indicated by theletters and numbers that precede the string “cop1” in a hosts file entry. For example:
127.0.0.1 localhost demo1099cop1192.168.80.113 curly pcop1
This tells Teradata that when a client tool references the instance “demo1099”, it should directrequests to “localhost” (or ip address 127.0.0.1), when a client tool references instance “p”, thislocated on the server “curly” (or ip address 192.168.80.113). There is no tie here to any kind of database server specific information (this is
similar to Oracle’s instance id. Tdpid <> Oracleinstance id!!!). That is, the tdpid is used strictly to define the name a client uses to connect to aserver. You can really call a server whatever you want. Teradata does not care. It simply takesthe name you specify, looks in the “host” file to map the <name>cop1 (or cop2, etc.) to an IPaddress, and then attempts to establish a connect with Teradata at the IP address.Sometimes you’ll see multiple entries in a hosts file with similar tdpids:
127.0.0.1 localhost demo1099cop1192.168.80.113 curly_1 pcop1192.168.80.114 curly_2 pcop2192.168.80.115 curly_3 pcop3192.168.80.116 curly_4pcop4
This setup allows load balancing of clients among multiple Teradata nodes. That is, most Teradatasystems have many nodes, and each node has its own IP address. Without the multiple hosts fileentries, every client will connect to one node and eventually this node will be doing more than its“fair share” of client processing. With multiple host file entries, if it takes too long for the nodespecified with the “cop1” suffix to respond (i.e. curly_1) to the client request to connect to “p”, thenthe client will automatically attempt to connect to the node with the “cop2” suffix (i.e. curly_2) andso forth.
Informatica / Teradata touch points
Informatica 7.1.2 accesses Teradatawith severalthroughvarious Teradata tools. Each will bedefinedand as tohow it is configured within PowerCenter.
Teradata provides 32-bit ODBC drivers for Windows and Unix platforms. If possible, use theODBC driver from Teradata’s TTU7 release (or above) of their client software because this versionsupports “array reads”. Tests have shown these “new” drivers (3.02) can be 20%-30% faster thanthe “old” drivers (3.01). This lastest release of Teradata’s TTU8.0 uses ODBC v3.0421. Teradata’sODBC is on a performance par with Teradata’s SQL CLI. In fact, ODBC is Teradata recommendedSQL interface for their partners.Do not use ODBC to write to Teradata unless you’re writing very small data sets (and even then,you should probably use Tpump
instead) because Teradata’s ODBC is optimized forquery access and, hence, is not optimized for writing data. ODBC is good for sourcing and lookups.PowerCenter Designer uses Teradata’s ODBC to import Source and Target table.
Informatica Confidential. Do not duplicate.3 of 23Revision: 12/2/2011