If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Import complete content store [10.2.2 FP5]

Started by RubenvdLinden, 10 Jun 2016 11:07:20 AM

Previous topic - Next topic

RubenvdLinden

I'm running 10.2.2 FP5 in a test environment and tried to import the content store of our production environment (still running 10.2.1).
The Public Folders content import as expected, however the My Folders content doesn't seem to import.

The export of the production environment is a full export including user account information.

Anyone run into this problem?

Thanks, Ruben

bdbits

I do not have a definitive source on this, but in my experience, My Folders content is never included in exports.

prikala

#2
Do you use the same authentication source in both environments?

My folders content is identified by CAMID and if CAMID:s are different (different namespace id, different AD:s, different path at LDAP etc), no folder can be seen even if it is imported.

I think you can check if this is the case by running Content Maintenance task "Consistency Check" (not sure what it does if namespace id:s are different).
If camid:s are different, task will probably find accounts that no longer exist in the authentication provider.

cognoslearner1


So by above discussion it means. My folder contents will be imported but however not visible (mapped) because CAMID are different.
If we are using the same authentication source to both environment then we can see my folder contents ?

MFGF

Quote from: cognoslearner1 on 13 Jun 2016 03:13:15 AM
So by above discussion it means. My folder contents will be imported but however not visible (mapped) because CAMID are different.
If we are using the same authentication source to both environment then we can see my folder contents ?

Correct! :)

MF.
Meep!

DaBaker

http://www.bspsoftware.com/knowledgebase/how-to-migrate-my-folders-for-all-users-in-bulk/

This can be done in bulk with MetaManager's Deploy Module Or by using the Backup/Restore modules.  If you are having trouble with the CAMID's you can easily provide a mapping file in MetaManager.

bdbits

I always wondered why My Folders content was problematic. Now I know why. Thanks prikala.

RubenvdLinden

Quote from: MFGF on 13 Jun 2016 03:27:19 AM
Correct! :)

MF.
That's strange, because the authentication source of both environments is the same.

Maybe I need to start over? Drop the content store of the test environment (in the database), allow anonymous login, then re-import the production content store?

AnalyticsWithJay

This is usually exclusively a CAM ID issue. Have you verified that the CAM ID for your account is the same in both environments?

Also, when you selected an entire content store backup, did you select "Include user account information"? It might be worth exporting again in case this was missed by accident.

MFGF

Quote from: RubenvdLinden on 24 Jun 2016 09:45:46 AM
That's strange, because the authentication source of both environments is the same.

Maybe I need to start over? Drop the content store of the test environment (in the database), allow anonymous login, then re-import the production content store?

You need to make sure that the authentication provider information is configured in exactly the same way in each of your two Cognos BI instances - ie the namespace has the same name etc. If you are using the same provider configured in the same way, the CAMIDs should be exactly the same...

MF.
Meep!

RubenvdLinden

As far as I can tell, the namespace of the authentication provider is identical in both environments.

I retried with a fresh content store database and a new import. Still doesn't work.
It must be a problem with the CAMIDs, because the imported scheduled tasks are scheduled by user 'Unavailable'.
Strangely, all the user rights are imported correctly.

I just checked the import parameters again, might this be the problem?

Store IDs
Assign new IDs during import


RubenvdLinden

#11
I checked again and the namespace of the authentication provider is identical in both environments.

I tried another import (clean databaseschema for content store database), without assigning new IDs during the import.
It still doesn't work.

EDIT: the user rights are also not imported correctly, all users seem to have all the rights.

Kiran P

Quote from: RubenvdLinden on 25 Jul 2016 07:44:24 AM
I checked again and the namespace of the authentication provider is identical in both environments.

I tried another import (clean databaseschema for content store database), without assigning new IDs during the import.
It still doesn't work.

EDIT: the user rights are also not imported correctly, all users seem to have all the rights.

Hi

Instead of configuring manually in the new environment, replace cogstartup.xml (after taking a backup) with the one from your earlier environment. This will make sure namespace IDs, binding credentials etc are exactly same.

Also is there a custom service provider you are using for authentication? If so make sure you login as an admin user into that namespace while exporting content.

And, in case you have multiple namespaces for authentication you need to export content once per namespace by logging in as an administrator.

Thanks
Kiran

RubenvdLinden

Thanks Kiran,

Just minutes before your post I tried another approach. I created a database export of the production environment (Oracle EXP) and imported the file into the test environment.
Next, I ran the NC_DROP script (<c10_64>\configuration\schemas\delivery\).

The last step was simply running Cognos Configuration to start the server and upgrade the content store. I did not change anything to my configuration or security namespace, but this time I did have all the personal settings and the correct file rights!

One word of warning: after using this method, make sure you check the dispatchers in Cognos Administration. Both my production and test environment were registered as dispatchers. I unregistered the production environment to prevent any problems.