Reports running against wrong database after import

[markryan]

Hi all,

I just realized last night that when I deployed my reports and their associated FM model package from Dev to QA, the reports are still hitting the Dev database.

I must be either missing a step or not familiar enough yet with Cognos to know how this is supposed to work.  My understanding was that if I have a clean/empty/new Cognos install on QA and wanted to deploy reports I had been working on in a Dev environment, I could simply create a deployment export that contained the report folder (Public Folders/Reports) and the package (Public Folders/The Package).  I then would create a deployment import on QA that uses the .zip from my Dev export.  and finally, I would create a data source connection on QA that points to the QA database for the package to use when running the reports.

When I run the reports on QA after all this, they are still running against the Dev DB. 

What am I missing here?

Do I have to open the FM model in FM Studio and change the data source in there and deploy it from FM to QA?  That doesn't seem right.  Seems to me it should be as simple as the steps I followed above.

Any suggestions?

[JGirl]

What options did you choose with your deployment?  If you selected to deploy & import the database connections with your package & reports, it is possible that you've also taken the database connection from the dev environment to the QA environment?

[markryan]

I just tried a clean deploy and removed any packages, reports and data source connections from QA first.  Just to make sure I hadn't inadvertently selected some of the deployment options.

So QA was empty again.  I then created a new deployment export containing the reports and the package they are associated with.  I made sure all options were not selected, so no data source connections included.  I then imported the package and the reports.  after this, I manually created the data source connection to the QA db.

Same problem.  My reports are still running against the Dev db.

Could this be caused by any settings in the FM Model, or in the reports?

could it have anything to do with the fact that we have both the Dev and QA dbs on the same server?

If anyone has specific steps that should work for this, I can try them to see if I'm not overlooking something.

Thanks

[blom0344]

It has been two weeks from your last response , but did you try getting rid of all the cache options Cognos provides? Possibly Cognos returns a dataset from the server cache without requerying the database. I would set your report queries to not use any cached results..