If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

FM connection to teradata with CQM

Started by ricky_ru, 18 Feb 2014 03:45:24 AM

Previous topic - Next topic

ricky_ru

Dears,

I have single cognos 10.2 installed on Linux and I also have installed and configured the Teradata client successfully in the same machine. In the Cognos admin page, the data source <testTD> can be tested OK to connect to the remote db server.

Well, in Windows FM, I can connect to the cognos server and select the datasource <testTD> . But the connection could not be made.

Could anyone be sure to tell me the following:
1) The Teredata client needs to be installed on the same machine as FM as well? (I do not think so because that would be stupid as it can let cognos server to do the db fetching).
2) Peoples say cognos uses 32 bit library to connect to database with CQM. Is this specific to all databases or particular database such as Oracle?
3) If I am wrong in step 1, I will install 32 bit TD client on FM machine since the 64 bit did not help me fix it.

The error from FM is as below:  I can not understand it. I have set the signon information and test it in admin page very well.
QE-DEF-0285 The logon failed.
QE-DEF-0323 The DSN(ODBC)/ServiceName is invalid. Either the DSN is missing or the host is inaccessible.
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
testTD

UDA-SQL-0031 Unable to access the "testTD" database. Check that the connection parameters to the database are configured correctly. For example, ensure that the data source connection contains the signon information, such as a password, to connect to the database.
UDA-SQL-0532 Data Source is not accessible: "testdsn".
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified


ODBCINI:
[testdsn]
Driver=/opt/teradata/client/13.10/odbc_32/lib/tdata.so
Description=Teradata running Teradata V1R5.2
DBCName=<server ip>
LastUser=
Username=qatst01
Password=qatst01
Database=qasample
DefaultDatabase=qasample



Thanks,
Ricky

sdf

#1
i think you need to set a DSN into your windows FM to connect to teradata.
check your ODBC drivers and test it.


just to add, please make sure that you have included the port number for the datasource connection in your cognos server.

MFGF

Quote from: ricky_ru on 18 Feb 2014 03:45:24 AM
Dears,

I have single cognos 10.2 installed on Linux and I also have installed and configured the Teradata client successfully in the same machine. In the Cognos admin page, the data source <testTD> can be tested OK to connect to the remote db server.

Well, in Windows FM, I can connect to the cognos server and select the datasource <testTD> . But the connection could not be made.

Could anyone be sure to tell me the following:
1) The Teredata client needs to be installed on the same machine as FM as well? (I do not think so because that would be stupid as it can let cognos server to do the db fetching).
2) Peoples say cognos uses 32 bit library to connect to database with CQM. Is this specific to all databases or particular database such as Oracle?
3) If I am wrong in step 1, I will install 32 bit TD client on FM machine since the 64 bit did not help me fix it.

The error from FM is as below:  I can not understand it. I have set the signon information and test it in admin page very well.
QE-DEF-0285 The logon failed.
QE-DEF-0323 The DSN(ODBC)/ServiceName is invalid. Either the DSN is missing or the host is inaccessible.
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
testTD

UDA-SQL-0031 Unable to access the "testTD" database. Check that the connection parameters to the database are configured correctly. For example, ensure that the data source connection contains the signon information, such as a password, to connect to the database.
UDA-SQL-0532 Data Source is not accessible: "testdsn".
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified


ODBCINI:
[testdsn]
Driver=/opt/teradata/client/13.10/odbc_32/lib/tdata.so
Description=Teradata running Teradata V1R5.2
DBCName=<server ip>
LastUser=
Username=qatst01
Password=qatst01
Database=qasample
DefaultDatabase=qasample



Thanks,
Ricky

Hi,

Sounds like you are connecting to Teradata via ODBC, which is CQM. For all CQM access, FM contains it's own query engine, which means you need the Teradata client on your FM machine, plus you need the same ODBC DSN defined as on your linux server.

To answer your questions:

1) Yes. It is not stupid - with CQM, FM uses local access while you are modelling. Once a package is published to the server, access from reports is via the connection on the server. The only time you do not need a local client and connection on your FM machine is when using DQM - FM uses the remote connection on the server. This means you can't do modelling when offline from the server, though.
2) Yes - CQM is entirely 32-bit. You need a 32-bit ODBC to connect to Teradata. All database access in CQM is 32-bit because the bibustkservermain.exe processes spawned by the Report Service are 32-bit. You can get 64-bit access by using DQM, and this utilises jdbc access not ODBC. DQM access is via the Query Service not the Report Service.
3) Yes - this is exactly what you need to do if you want to access Teradata via ODBC in FM. To access Teradata via JDBC in FM all you need is the connection defined on the server.

Cheers!

MF.
Meep!

ricky_ru

Quote from: feds on 18 Feb 2014 03:51:23 AM
i think you need to set a DSN into your windows FM to connect to teradata.
check your ODBC drivers and test it.


just to add, please make sure that you have included the port number for the datasource connection in your cognos server.

I am going to be crazy by installing the ODBC driver on windows.
1) I downloaded the version tdodbc__windows_i386.13.10.00.10.zip from here: http://downloads.teradata.com/download/connectivity/odbc-driver/windows
2) Installed to follow the right order. icu->gss->odbc
3) At the end of the software, I am able to have the chance to launch the odbc onfig ui and readme. And I could config a odbc DSN.
4) But the problem is that when I want to add new dsn, there is no teradata item in the list to be selected. And I could not remove/config the previous one in step 3 as there is no driver found issue shown.
5) It looks to me that in step 3, the driver information is in memory. But it could not write to the system register or other files.

I tried to use admin to install and modify the register table permission. But still got the problem. Also, it does not  have the port number field and no test button.

Do you have any idea?

Thanks,
Ricky

sdf

Hi,

what you need is the 32bit Teradata client for windows.
When you install this, this will include the drivers(odbc).
After the client instalaltion in your windows FM, the driver for teradata should be present in the odbc config.
Then you can create a DSN using this driver.

The one i'd like you to check (port) is your configuration of data sources in cognos configuration.
When indicating the dbserver, the port to that database must be included.
Im not sure what port is used for teradata.

bdbits

Just an FYI in case you are using 64-bit Windows on your client box and are not aware of it.

Win64 has two versions of ODBC setup, one 32 and 64. The standard one you get through the start menus is the 64-bit version. Try running C:\Windows\SysWOW64\odbcad32.exe and see if your Teradata data source is listed there.

The installer probably launched the 32-bit ODBC config, which is why it seemed functional there but not later when you went back and were running the 64-bit ODBC config.

ricky_ru

bdbits, thanks you for your help. You pointed it.
Thanks for everyone's help.