Archives of the TeradataForum

Message Posted: Tue, 24 Apr 2007 @ 14:17:31 GMT

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

In looking at the manuel, there are a number of additional things that you should (could) do when you get such an error.

one of them would translate into walking throught the list of SQLExceptions with the getNextException () method. Since you don't have source code and most applications don't typically do this, you might be out of luck on this front. This is a shame, because it might provide some useful additional information.

Are you able to submit the query by its self (using JDBC) and see if it causes the problem? Maybe the problem is related to previous application activity on the connection. If you can get the problem with a standalone Java app and have demonstrated that the problem relates to the JDBC driver (because it works using ODBC) you can ask Teradata support a very specific question.

What did the application vendor say (other than the standard "it works on XYZ database" response)? Are they able to offer any support or have they even tested their application on Teradata? Maybe they are using features of the JDBC driver that requires a certain level - if they have tested against Teradata, which version of Teradata and which JDBC version did they use for certification?

Does this query (application function) always fail, or does it sometimes work? Is there another path in the application through which a similar query can be submitted? Does it work then? If so, this might point to a sequence of events the application is doing. More specifically, if you exit the application (so it logs off the database session), start the application and perform this function as the first thing, does it work then?

I know I haven't given you an answer, but maybe some of these things can help isolate the location of the problem.

Glenn Mc

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