Archives of the TeradataForum

Message Posted: Thu, 29 Aug 2013 @ 10:29:13 GMT

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

Hi

I was wondering if anybody has experienced intermittent ODBC connection errors. I have a few users that are raising ODBC connection issues, is this network related, or is there something I can tune.

Different types of errors reported:

     [Teradata][ODBC Teradata Driver] Login timeout Expired [Teradata][ODBC Teradata Driver]
     Unable to get catalog string [Teradata][ODBC Teradata Driver] Driver does not support
     specified fInfoType

     [Teradata][ODBC Teradata Driver] Catalogs Not Supported

In relation to Excel: The following errors were observed [Teradata][ODBC Teradata Driver] Driver does not support specified fInfoType

     [Teradata][ODBC Teradata Driver] Catalogs Not Supported

I enabled the ODBC setting to "Log Error Events" on one of the users

The following was recorded in the windows event logs:

No 1

The description for Event ID 54940 from source EXCEL.EXE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

     [Teradata][ODBC Teradata Driver] Driver does not support specified fInfoType HY096

No 2

The description for Event ID 54940 from source EXCEL.EXE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

     [Teradata][ODBC Teradata Driver] Catalogs Not Supported HYC00

In relation to Informatica: The following error was observed

The workflow reports an error of the type: ?

However, Informatica/Teradata should provide a more useful error than this.

The Teradata ODBC driver is trying to post an error.

It should be able to find an error message if the catalog file that holds the errors is in the path :

I believe the catalog file is called something like: tdodbc.cat.

It should be somewhere in the /teradata/client/..... directory.

This may then give the actual error causing the problem.

I have set the time out period in the driver from default of 20 seconds to 120 seconds, but the errors are still reported. Users can still logon, may get the error first time, and can then logon after that.

We are running TD 13.10, ODBC 13.10.00.06, users are connecting via LDAP.

Any help would be appreciated, I done a bit of search in the manuals and google, nothing obvious at this stage.

Cheers

Steve

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