I have Cognos 10.2.1 in windows 64 bit and installed 32 bit Teradata driver in server and my local machine.
Configured the required details in 32 bit ODBC driver of server and my local machine. Choose ODBC as type and gave the odbc name which i gave in odbc configuration. But it throws attached error.
Quote from: Cognos8 on 28 Apr 2015 09:09:20 AM
I have Cognos 10.2.1 in windows 64 bit and installed 32 bit Teradata driver in server and my local machine.
Configured the required details in 32 bit ODBC driver of server and my local machine. Choose ODBC as type and gave the odbc name which i gave in odbc configuration. But it throws attached error.
Hi,
When setting up the data source connection in Cognos, choose the Teradata connection type instead of the generic ODBC connection type. You can enter the name of the Teradata ODBC connection after pressing Next.
Cheers!
MF.
Same issue after changing that to teradata. attached error message.
Any specific option to choose in isolation level ? i choose read uncommitted.
Quote from: Cognos8 on 28 Apr 2015 09:21:59 AM
Same issue after changing that to teradata. attached error message.
Any specific option to choose in isolation level ? i choose read uncommitted.
The error message appears to be saying that E:\Program Files (x86)\Teradata\client\13.10\ODBC Driver for Teradata\Lib\tdata32.dll cannot be found. Is this where you installed the Teradata ODBC? Can you verify that the dll does actually exist there?
MF.
Yes i installed in same path. error thrown Dll is exist. attached the path reference.
Quote from: Cognos8 on 28 Apr 2015 10:00:54 AM
Yes i installed in same path. error thrown Dll is exist. attached the path reference.
Is this on the machine running FM?
I am creating cognos datasource connection from my local my machine. Cognos Server and my local machine has FM. Both machine has driver and Client.
I also tried connecting JDBC, placed the required drivers and restarted the service. Got the attached error
Hi,
It is really weird, after restarting my machine , ODBC connectivity issue is resolved. did not do any changes in configuration. let me know the solution for JDBC error which i attached. Thanks