Archives of the TeradataForum

Message Posted: Tue, 15 Jul 2003 @ 13:31:29 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Based on our experience I think Type-4 doesnt resolve the DSN name dynamically to its corresponding cop entries unlike Type-3.

The below URL was working fine for a Type-3 architecture (abc.com is the middle tier where Gateway/JServer was running ).

jdbc:teradata://abc.com:7061/TDPID where TDPID was getting resolved dynamically to its cop entries in the DNS server.

Whereas for Type-4 by the below URL wasnt working. jdbc:teradata://TDPID

Type-4 doesnt add "copn" to the TDPID so we had to specify a specific DNS entry (eg TDPIDcop1 ).

I guess since Type-4 being a pure Java Driver, with no CLI interface and also being fairly new, the logic of dynamically adding COP entries might not have included in this release...

Regards,

Raj

	<Prev	Next>		<<First	<Prev	Next>	Last>>