Archives of the TeradataForum

Message Posted: Thu, 11 Oct 2007 @ 08:17:36 GMT

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

I don't see any entry in the stack trace that relates to the JDBC driver.

Have you tried a simpler program just to test the connectivity. For example something like this:

     ...
     driverName = "com.ncr.teradata.TeraDriver";
     Class.forName (driverName);
     String dbURL = "jdbc:teradata://dbc/";
     String uid = "userid";
     String pwd = "password";
     Connection conn = DriverManager.getConnection (dbURL, uid, pwd);
     System.out.println ("Connected: " + conn);
     ...

I would suggest trying something like the above in a command line utility to isolate any problems with the driver / Teradata interaction first. Then move into (what looks like) your application server environment.

Also, it is possible that you might have missed something when completing "every step according to the manual". Thus it may be helpful to include snippets of code containing things like your URL, the driver name (or screen snaps of the connection pool definition if you are using that), driver version and so on.

Also are you using V2R5.0 or V2R5.1? It was a long time ago, but I am uncertain as to whether or not V2R5.0 supported the JDBC Type 4 driver. I have a feeling (and that is all it is) that Type 4 driver support wasn't introduced until V2R5.1 (or at the very least a specific patch level in V2R5.0). Either way, if you use something like the above little test program, you should be able to determine pretty quickly whether or not your Teradata works with the Type 4 driver.

Good Luck

Glenn Mc

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