Author Topic: Cognos 10.2.2 CQM FM Model to Cognos 11 Upgrade  (Read 363 times)

Offline Cognos91

  • Senior Member
  • ****
  • Join Date: Oct 2007
  • Posts: 57
  • Forum Citizenship: +0/-0
Cognos 10.2.2 CQM FM Model to Cognos 11 Upgrade
« on: 20 Sep 2017 08:18:50 pm »
I am trying to understand the upgrade and usage of a Cognos 10.2.2 CQM FM Model in Dashboard.
We recently upgraded to COgnos 11.0.6. This means that the content store was migrated from 10.2.2 TO 11.0.6.
This will imply that the underlying packages and reports will all be upgraded to the 11 version.

Now, the report studio based reports work fine.
However, when we drag and drop query items onto the Dashboard, it throws Query internal service error.

The DSN connection is not defined with JDBC. Also,the published package is based of 10.2.2 CQM FM Model.

Question:
1) Will I need to change the DSN connection to include JDBC so that the package can be used in Dashboard
2) Since this is a CQM model, willl I need to convert it into DQM to be able to be used in Dashboard? Does Dashboard support CQM FM Models?

Offline Kiran P

  • Community Leader
  • *****
  • Join Date: Oct 2013
  • Posts: 77
  • Forum Citizenship: +0/-0
Re: Cognos 10.2.2 CQM FM Model to Cognos 11 Upgrade
« Reply #1 on: 20 Sep 2017 09:50:04 pm »
Hi, you need the models to be in DQM to
 use with the new Dashboard interface. And in order for DQM package to work you need to define JDBC connections for your data sources.

Thanks
Kiran

Sent from my ZUK Z2132 using Tapatalk

Offline Cognos91

  • Senior Member
  • ****
  • Join Date: Oct 2007
  • Posts: 57
  • Forum Citizenship: +0/-0
Re: Cognos 10.2.2 CQM FM Model to Cognos 11 Upgrade
« Reply #2 on: 30 Oct 2017 02:54:58 pm »
Kiran,

I am not sure if this is entirely true. I ran a test on the sample model, Go Sales, with the following conditions.
Model was in Compatible mode all along.

When package was published as compatible or even in dynamic query mode (keep in mind this is the package only), but the DSN connection was only kept as Native, the Dashboard threw an JDBC connection error.

When package was published as compatible, and DSN connection included JDBC, the dashboard did not throw any error. The package in compatible model could be used. (This package included both query (relational) as well as analysis - DMR).

When package was published in dynamic query mode and DSN connection included JDBC, the dashboard worked fine for both the packages.

This test confirms that it may not be necessary to convert a CQM model to DQM version.
1. You can add a JDBC DSN connection (even if the model is CQM and if the package is published as is), Dashboard will still work.
2. Add JDBC DSN connection, (model is CQM, but package is published in dynamic query mode), Dashboard will still work.

Has anyone else tried the same while upgrading to Cognos 11?>

 


       
Twittear