Resolving a Broken Data base Connection in Framework?

[tkierzko]

Hello All!

This is my first post and I have to preface that I have about 2 months of Framework Manager experience and Data Modeling best practices. This project I'm having an issue with is also my first model I've made from scratch in Framework Manager!

I built the model originally from an ODBC Database connection that I set up through the Cognos Administration.

This database was migrated to a new server. I updated the ODBC database connection AND the Data Source Connection in Cognos Adminstration. I set it to use the signon credentials from the ODBC and the connection was successful. Furthermore, a coworker used a published package I made with my model and had no trouble querying the data and creating a report from the new database.

The issue I'm having is within Meta Data Wizard in Framework manager. I tried to test the Data Source Connection in Framework this morning from the model I was working on and I got this:

Code Select Expand

QE-DEF-0285 The logon failed.
QE-DEF-0325 The logon failed for the following reason:
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
<dbName>

UDA-SQL-0031 Unable to access the "<dbName>" database.
UDA-SQL-0107 A general exception has occurred during the operation "attach".
[MySQL][ODBC 5.1 Driver]Access denied for user '<myUserName>'@'<myComputerName>' (using password: YES)

I believe I accidently left Framework open when I updated the ODBC and Connection in Cognos Administration. I also saved the model, erroneously thinking I had opened it after the opdate I made because I got sidetracked by a meeting.  >:(

SO, How can I update to the new data source connection within Framework Manager with out having to redo the project and republish subsequent packages made from it.

TL;DR - A Data Source Connection I set up in Cognos Administration isn't working within Framework because I left Framework open while updating that same ODBC and Cognos Administration connections. Published Packages, Cognos Admin and the ODBC are all successfully connecting to the new server location EXCEPT the connection in Framework!    :(

[tkierzko]

Figured I'd follow up with this.

I found out through a colleague that Framework Manager relies on the local ODBC connection, the one I did not update but kept the same name as the Cognos Server's ODBC. I think that's why the UDA-SQL-0107 error was thrown/returned. That explained why the published package, the Report Studio reports, the Cognos Administration Data Source connections  AND the server's ODBC was working  :P

Chalk this up to a newbie error.  ;D

[blom0344]

Why ODBC in the first place, instead of native connectivity?

[tkierzko]

Sorry for the slow response blom0344!

I found out we were having multiple issues using a JDBC driver for a newer DBMS we just started using.  The ODBC connections have been in place until we fix that issue.  :-\