I want to be able to set up security so that only x number of users see certain universes and y number see another universe. Having tried so many things it seems the only way to configure this is to set up separate universe folders. Now this is fine with new universes built in XI. How do i move universes from one folder to another for universes that have been migrated using the wizard from V6?
nandos999 (BOB member since 2006-01-27)
In the Designer tool, you can import the (former v6) universe, and then when you export it, select the folder where you want it to go. Because the universe you’re exporting already exists in the system, you’ll be prompted if you want to move the universe to the new folder, or if you simiply want a copy stored there.
DJ
DJ06482 
(BOB member since 2002-11-22)
Hi DJ06482,
I was following your advice. But it gives me an error message saying that
“CMS Query Failed
Previous Error: Item 1 not found in the collection”
then when I hit OK I get another msg
“The connection associated with this universe has not been defined. You must create a secured connnection (UX0014)”
Even when I set the connection right I still get this error msg. Have you come across this? This is a universe which I have imported from 6.1. All I wanted to do was just move it to a different folder.
Any help will be greatly appreciated.
tfa_bo (BOB member since 2006-05-17)
Can you import the universe in designer and check if the connection is well defined and if it’s a secure connection?
Sometimes, function of the options you’ve checked, connections are not imported from 6.1.
In order to move a universe from a folder to another : import it in designer and reexport it to another folder. You should be prompted for answering if you want to copy or move the universe to the other destination.
jerryf 
(BOB member since 2006-02-13)
If you’re still having issues with the connection, I’d re-create the connection from scratch using the original parameters that you used in 6.1. Note that in order to export the universe, you’ll need a secured connection…
DJ
DJ06482 (BOB member since 2002-11-22)
Actually, I’ll amend what I wrote yesterday. Try simply testing the connection (In Designer, File → Parameters → Test) and then if the database is responding, save and then try to export the universe. That workflow worked for me this morning, after it gave me exact error you’ve been getting. If that still doesn’t work, then you’ll probably want to try rebuilding the connection.
Just for reference, the universe that I was using yesterday was just migrated to our Production server (an empty environment). My theory is that the first time you try to export a “new” universe, BO balks and throws up the error about the repository object and the secured connection (even though the connection is in fact secured). Once you test the connection and it comes back OK, then it will allow you to export the universe.
DJ
DJ06482 (BOB member since 2002-11-22)
Hi DJ06482,
Thanks for the response.
I agree with your theory. But the way I got it work was clean up my local folders where any version of the universe resided and then did the import again - tested the connection and then export it back to the CMC. Not convinced why it worked but as long as it works I am fine.
Now my other challenge is whenever I import any report from 6.1 to Xi it gets stored in a Number 2 folder - like Documents(2) and Universe(2). This happens after I check the “Automatcally rename objects if an object with that title already exists in the destination folder”. If I uncheck that option then the report doesnt get imported. In the View Detail log it says for that object “Parent Folder not found”. So I am doing the workaround - importing it to the document(2) folder and then move/copy to where I want.
Do you know of any better solution?
thanks,
tfa
tfa_bo (BOB member since 2006-05-17)
it also depends of the migration scenario option you’ve choosen : merge or update. I remember it’s well described in the migration doc.
jerryf (BOB member since 2006-02-13)
Two things:
On the topic of getting the connections to work, I actually had to use both of my methods yesterday. One time I was able to export the universe by simply testing the universe connection, saving, and then exporting. The other time I had to manually re-create the universe connection before it would allow me to export the universe. I’m not sure why it’s giving me all of these problems, but just wanted to pass along what worked.
Unfortunately, I’ve confirmed with BO tech support that you can’t overwrite an existing universe in an XIR2 environment through the import wizard, regardless of what options you choose. The “merge” vs. “use the source system as a reference” option in the Import Wizard really doesn’t make a big difference when it comes to migrating universes. In my experience, the Import Wizard will only let me migrate a universe into a copy of the folder that exists in my destination environment.
Unfortunately, I’ve found that to overwrite a universe I’ve had to:
1. Delete the existing copy of the universe
2. Move the new copy to the folder of the original universe (ie. to the "Sales" folder from the "Sales (2)" folder)
3. Delete the "Sales (2)" folderHere’s the problem: the new universe will have a different CUID than the older version which you just deleted. Luckily, reports look for their universe first by it’s CUID, and if they don’t find that, they look for a universe with a name matching the one they were originally associated with. This will work well, until you happen to have two universes with the same name in the same environment, and then you can’t guarantee which one the query tool (Web or Deski) will use.
You can always reassociate a universe with a report in either Webi or Deski, which is the best way of ensuring that the report will always be associated with the correct universe.
HTH -
DJ
DJ06482 (BOB member since 2002-11-22)
Ok thanks for the input.
That’s a bad news if we can’t use import wizard for the dev->test-prod tranfer process for the universes.
I’ll made some more tests when i’ll have two BO environments.
jerryf (BOB member since 2006-02-13)
You can use the import wizard to transfer universes, but you’ll have to do some cleanup in your destination environment if you wish to overwrite an existing universe. The Import Wizard works OK for moving from earlier versions of BO to XIR2, but it’s much less impressive at migrating content between different XIR2 environments.
DJ
DJ06482 (BOB member since 2002-11-22)
What i wanted to do is to use import wizard and its ‘update’ option to move contents from dev to test then prod server.
jerryf (BOB member since 2006-02-13)
That’s what my intent was, as well. Here’s some more detailed info on the topic:
DJ
DJ06482 (BOB member since 2002-11-22)
FYI, I’ve hit the UX0014 error today for the first time. I’m running XIR2 and used the import wizard to transfer from one server to another.
I was able to get around it twice today by[list]1) editing the connection by changing the user/pwd to another valid user/pwd
2) testing the connection
3) saving, then exporting the universe
[/list]I could then do the same thing to put it back to the user that I really wanted. If I just tested the connection without actually changing the user/pwd, I continued to receive the error.
Morgan
morgan (BOB member since 2006-04-12)
Here’s something interesting about moving universes using the Import Wizard:
Import Wizard does not import Universe - c2019718
DJ
DJ06482 
(BOB member since 2002-11-22)
I am also getting the message that the CMS query failed, Item 1 was not found in the collection when exporting a universe. I deleted the ODBC connection on my local computer, re-added it. Then was able to successfully test the connection using the file -> parameters -> test screen. But when I export the universe, the last message I get is:
The connection associated with the universe has not been defined. You must create a secured connection.
Does anybody know what else I can do so I can export the universe successfully?
bkaporch (BOB member since 2008-12-02)