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

Migrating DLIST from one environment to the other

Started by srajan, 09 Feb 2007 11:44:44 AM

Previous topic - Next topic

srajan

Is there a simple way we can migrate just a DLIST from one environment to another in the Cognos EP product. Any suggestions on this would really help. Thankyou in advance.

cbrandt

Is that between development and production?
You can copy Analyst items by copy the DOS file and then refresh/rebuild indexes. However this will only work if the library number is the same, like it would be if you copied all libraries from dev to prod. References to formats and DList formats will also point to the original library number.
You find the filename of a DList in the Summary tab or under 'File>Administration>File to Object'. You have to have Administration rights to see the DOS file.
Be careful. COGNOS is not recommending to move or copy the DOS files. I have seen libraries getting corrupt by playing around with the DOS files.
Do a backup of the library first and proper testing afterwards.

Considering the risk, would it be to much effort to recreate the DList?

andrewbho

Analyst libraries reside on a file server so find a way to make them to yourother environment just make sure to create a staging library since your libraries can't have the same # or name.  Use the copy wizard.

Or

you can go to your target environment, remove your library NOT delete it, add your source library to it, use the copy wizard and put it in a new library and use the copy wizard.

Or

Export your dlist or a cube and copy and paste it.

srajan

Thankyou for your responses. Yes, this is to move a DLIST from development to production. In order to keep the environments in sync we want to keep the analyst libraries only in development and test environments. I am new to Cognos EP and thereforfe the following questions may seem too basic but I would really appreciate a response.

We have DLISTs that needs new DLIST items. My question is  that, if we copy and paste the newly created DLIST to production, will the users risk losing data that they entered in production?
What are the best practices followed by many of you regarding migrations?




andrewbho

It will be fine, it's based on IID and not dlist name.  I am not sure if you are using Contributor but you should be okay.

d3h9

If you replace -dlist in analyst you loose all data when you synchronise with contributor. Try to use update d-list.