Same FM model/Different Oracle schema's

[cogman8]

We need to point the same FM model to test and production database schema's in Oracle. I have read some of the KB's and spoken to Cognos support(which were no help!). The best solution that I came up with was creating 2 data sources(test,prod) in Cognos Connection, one data source and 2 packages(test,prod) in FM. When publishing packages in the future, I will need to make sure the FM data source property item "Content Manager Name" is set to the correct Cognos Connection data source.

Does anyone else have a better way of approaching this issue. Thx.

[MFGF]

How about having a single logical data source defined in Cognos Connection, with two physical connections within it - one to Test and one to Prod.  Each of the connections could then be secured to limit access to only the relevant audience.  Anyone with access to both (FM developer, for instance) should get prompted for which to use.

Just a thought...

MF.

[Cannondale23]

this solution is more for db changes, we use to tell the dba to change the tnsnames file, we had a single logical database name say 'cognosconnection' and that would be referenced in fm and tnsnames file and would not change, then the actual oracle sid would be altered based on which env had the best data