Author Topic: CAMID's Changing Betweeen Old and New Environment Negating Scheduled Reports  (Read 359 times)

Offline Magdalina08

  • Full Member
  • ***
  • Join Date: Oct 2019
  • Posts: 33
  • Forum Citizenship: +0/-0
We are upgrading from 10.2.2 to 11.0.13. We are putting the new environment on a new server as well. The scheduled reports are not running because the new instance of Cognos is changing the CAMID's of all users. Is there a way to avoid the CAMID's changing or is there a way to overwrite all the new ID's with the older ID's en mass?

Online MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 11,202
  • Forum Citizenship: +662/-10
  • Cognos Software Muppet
We are upgrading from 10.2.2 to 11.0.13. We are putting the new environment on a new server as well. The scheduled reports are not running because the new instance of Cognos is changing the CAMID's of all users. Is there a way to avoid the CAMID's changing or is there a way to overwrite all the new ID's with the older ID's en mass?

Hi,

If you use the same authentication provider, configured in exactly the same way using the same name, your CAMIDs should stay the same. If this isn't an option, BSP has a security migration tool that allows you to easily map your old security to your new. I'm sure one of the Admins will be along shortly to offer guidance :)

Cheers!

MF.
Meep!

Offline Magdalina08

  • Full Member
  • ***
  • Join Date: Oct 2019
  • Posts: 33
  • Forum Citizenship: +0/-0
Thanks MFGF.  We actually do have the same authentication provider, configured in exactly the same way using the same name. I spoke to IBM Support and they said because the server/vm/OS was changed, its causing it to populate new CAMID's.  Not sure why this is the case. I think this should be a pretty seemless process.

Offline Eric.Pleiss

  • Administrator
  • Full Member
  • ******
  • Join Date: Jun 2016
  • Posts: 31
  • Forum Citizenship: +2/-1
Hi,
BSP Software has a tool specifically designed to tackle this use case, even with mismatched CAMIDs, and will allow you to easily move users in Cognos to the new Authentication Provider, map the users when appropriate, and gives you options on how to handle users that exist in only one of the namespaces.  You also get access to the full suite of BSP Cognos admin tools, so that you can clean up any security or content issues while you do the migration, so that when users log into the new provider, they're greeted with a more efficient and effective Cognos than they had before. 

And we can do all of this with minimal manual work, and you can complete a namespace migration within hours (once you're ready to press go).

Check it out http://www.bspsoftware.com/products/metamanager/smss/

I'm happy to answer any questions or set you up with a demo of the tool and help get you started.