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

Framework Manager datasource doesnt work on local machine

Started by Naven, 02 Sep 2010 12:58:11 PM

Previous topic - Next topic

Naven

Hi All,

I have created a datasource in Cognos Connection successfully but when I login to Framework Manager which is installed on my local machine and access tables through the datasource it is throwing an error which says

(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:
DS-HPSM

UDA-SQL-0031 Unable to access the "DS-HPSM" database.
UDA-SQL-0532 Data Source is not accessible: "hpsmprod".
ORA-12545: Connect failed because target host or object does not exist )

But the same works fine when tested in Cognos Connection.

Please help me on this issue.

Thanks,
Naven

Lynn

Do you have a database client installed on your local machine? When testing through Cognos Connection it would use the database client that is on the Cognos server for connectivity to the database.

With FM on your local machine you would get that message if there is no client installed.

MFGF

Quote from: Lynn on 02 Sep 2010 01:19:38 PM
Do you have a database client installed on your local machine? When testing through Cognos Connection it would use the database client that is on the Cognos server for connectivity to the database.

With FM on your local machine you would get that message if there is no client installed.

As Lynn says, the issue is that your local machine is not configured to talk to your database.  From the details in your posted error message, it looks like you are using an ODBC connection called DS-HPSM.  While this is obviously defined and working on your Cognos 8 server, I'd bet my favourite pair of slippers that it's not defined in the ODBC Administration console on your local machine, and this is where the problem lies.

Cheers!

MF.
Meep!

Naven

Lynn, MF

Thanks for your replies.

Host name in TNS entry was not proper, my bad.

It is working now.