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

Intermitent Data source connection

Started by sdf, 14 Jul 2014 08:02:08 PM

Previous topic - Next topic

sdf

Hi,

We are having problems with our datasource connection. There are times that reports run successfully then will fail most of the time.

WE have distributed instance, Cm on another server than the web app. Datasource connection test for both gateways fails on first test but succeeds on the subsequent tests.

The DSN we made from odbc connection to both servers succeeds the connection test. We are clueless where and what to check.

I have attached the serverlog, if ever someone is willing to give a hand.


Thanks!


Feds

Grim

What version of Cognos 10 (and FP level) are you using?

What version of the Vertica DB are you running on the DB server?
What version of the Vertica ODBC Driver are you using on the Cognos servers?

Have you checked that everything "Vertica" is supported by the version of Cognos you are running?
You can do that using the following link:
http://www-01.ibm.com/support/docview.wss?uid=swg27037784
"Honorary Master of IBM Links"- MFGF
Certified IBM C8 & C10 Admin, Gamer, Geek and all around nice guy.
<-Applaud if my rant helped! 8)

MFGF

Quote from: feds on 14 Jul 2014 08:02:08 PM
Hi,

We are having problems with our datasource connection. There are times that reports run successfully then will fail most of the time.

WE have distributed instance, Cm on another server than the web app. Datasource connection test for both gateways fails on first test but succeeds on the subsequent tests.

The DSN we made from odbc connection to both servers succeeds the connection test. We are clueless where and what to check.

I have attached the serverlog, if ever someone is willing to give a hand.


Thanks!


Feds

Hi,

Is it possible the ODBC is defined on one server in the 32-bit ODBC admin console and on the other server in the 64-bit ODBC admin console? This would account for the working-not working-working conundrum, as requests get sent to one or the other server for processing. Make sure the ODBC connection is defined using the 32-bit ODBC admin console.

Cheers!

MF.
Meep!

sdf

#3
QuoteHi,

Is it possible the ODBC is defined on one server in the 32-bit ODBC admin console and on the other server in the 64-bit ODBC admin console? This would account for the working-not working-working conundrum, as requests get sent to one or the other server for processing. Make sure the ODBC connection is defined using the 32-bit ODBC admin console.

Cheers!

MF.


That was the case before, but i have already uninstalled the 64bit drivers(7.0.1) from both servers and installed 32bit (7.0.0) and create ODBC connections to both servers.

Unfortunately, the problem still persist.

Cognos is on version 10.1.1, im not sure if any FP were installed.
Vertica server is on 7.0.1 but im using 32bit 7.0.0 client. (Im thinking that there are some bugs with the latest client.)
Are there any other reasons you can think that may have cause this?


Thanks for your replies!




Feds

sdf

I think we have solved the issue. Though i asked the authors to test the reports continuously.
What i have done :

After installing the 32bit 7.0.0 client to both servers, i checked the configuration of Content manager and web app tier.
I found that in the configuration of web app, there are URI's that are set to localhost. So i changed the uri to ip address.
And also put the content manager gateway on top of the web app gateway (order). Also, when i tried to save the configuration, i got error on the encryption keys (access denied). So i grant access to the service account that im using to the configuration and encryption key files. After that, i was able to save the configuration. I tested the datasource connection in cognos and it doesn't reflect any error. Also tested running the reports, and so far we haven't encountered any issue or error.

Thanks for your help!



feds