Hi All,
I have a requirement where we are migrating Business Objects Data base server form SQL server 2000 to SQL server 2008.So is the only solution here to recreate all the existing universes and reports in the new Server or is there any way to copy the universes/reports from the older server? Please help
Lucky002 (BOB member since 2012-08-28)
Keep in mind that the universes and reports are not stored in the database. So, no, you don’t need to copy, or move them. 8)
All you need to do is copy the BO system tables from the old database, to the new database, then re-point the CMS to the new database. You can do all of this in the CCM.
Obviously, you’ll want to have the system down during this whole process, so nothing is being modified in the system. So, open the CCM, on the server, and stop the SIA. Then click on the Specify System Database button. You’ll see an option there to copy the data to a new database.
MichaelWelter 
(BOB member since 2002-08-08)
Thank you Micheal. Can you tell me what do you mean by BO system tables?
Lucky002 (BOB member since 2012-08-28)
They are the database tables used for BusinessObjects in the CMS Database. There are 5 tables.
MichaelWelter (BOB member since 2002-08-08)
Hi Michael,
Thank you for your reply. Do you mean that the BO tables are: CMS_VersionInfo, CMS_InfoObjects6, CMS_Aliases6, CMS_IdNumbers6, CMS_Relationships6 and CMS_LOCKS6? I got this list of six tables from http://wiki.sdn.sap.com/wiki/display/BOBJ/How+to+browse+CMS+repository.
So we can just take the back up of these six tables along with File repository server in the old Database and copy to new Database and point CMS to the new one right? Please confirm it as I have to suggest this approach to my Manager as they think that we need to recreate everything in the new one and I want to make sure I don’t suggest something wrong.
Thank you
Lucky002 (BOB member since 2012-08-28)
You should be taking daily backups of the database and file store, but you don’t need that for this procedure. In order to migrate to a new database, it’s pretty simple:
Create the ODBC (Or TNSNames) connection to the new database, on your server
On the server, open the CCM
Stop the SIA
Click the Specify CMS Data Source button
choose the option to copy data to a new data source
Enter the details for the current and target databases
Click OK
The data, including those tables, are all copied to the new database. Then you can restart your SIA, and you’re good to go.
MichaelWelter (BOB member since 2002-08-08)
I remember that in XI3.1 when I was changing a repository database to SQL server from a default one my account required to be an owner of the schema in order to create tables in a new db. Do you know if this is the same case in BO4.0? Do I need an account with schema owner role in db?
Marfi 
(BOB member since 2006-12-18)
Marfi, yes, you need an account with full control over the database.
MichaelWelter (BOB member since 2002-08-08)
Hi Michael,
In my current project I need to repoint the current repository to the new 11g database. The same copy of the current repository will be avilable in the new database.I just need to repoint it in the CCM right the step 5 in above "choose the option to copy data to a new data source ".Will that be fine.
Question here is since I have already a copy will it overwrite the same data in the database or create all new details.
I have all my Universe and reports in this current repository.
will it be available in there ? if i try to open the IDT and try to import
Regards
prashants (BOB member since 2010-12-23)
prashants, I’m confused. :?
The “repository” consists of the system database and the file store. The repository doesn’t point to anything. So you can’t repoint the repository.
If you want to migrate the system database to new platform, then yes, use the option “copy data to a new data source”. This will migrate the data from your current system database to a new system database, and will update the CMS to point to the new database.
That’s all you need to do. The file store will remain the same, and will work as expected.
MichaelWelter (BOB member since 2002-08-08)
Hi Michael (long time )
I think he is confused between
change the repository database to another existing schema with the tables already populated
vs
create a copy via CCM
sfaridi 
(BOB member since 2002-08-29)
Hi Michael,
I have the current repository CMS & Audit schema pointing to one Database.
This database will no loger will be avaiable from next month.
Now the replica of the same database is ready in a higher version oracle 11 g.The name of the database server is different. The schema name and user name will remain the same.
I need to point my current CMS & Audit info to the new database server.
Let me know if I could make it clear 
.
If I do so will all my Universe, reports everything work as expected if i do the above step mentioned by you.In such case what would be the option
prashants (BOB member since 2010-12-23)
Yes, just follow the steps I provided, and everything will work as expected.
MichaelWelter (BOB member since 2002-08-08)
Michael,
I would like to clearify your statement and apply it to my sitution.
We are in a POC stage of a migtration from 3.1 to 4.1. DB is currently Oracle 11.1 and we will be building out the new system on Oracle 11.2 RAC. the plan is to run a new build of all then migrate using upgrade manager for all our existing content. I don’t believe I have any concerns to this point.
We are waiting on hardware but we do have access to a single developer instance of Oracle and my questions is related to our DEV build: If I goahead and build out my 4.1 cluster pointing to the test DB from what you are saying I can then copy/change via the process above the test DB instance to point to the RAC instance once that has been built out.
This will only be our DEV environment that is built out this way. I plan on scripting the cluster install from the dev build and using that script in all my upper environments.
Are there any drawbacks to this meathod or am I better off to wait till the DB hardware is in place and up for my install/migration?
amosgreg (BOB member since 2012-01-27)
amosgreg, your method sounds fine to me. Migrating the database from instance to another is quite simple with the CCM. You should have no problems with this.
MichaelWelter (BOB member since 2002-08-08)
Thanks very much for u guys input to migrating CMS db. I also have the same issue as below:
We currently have CMS on oracle 10g DB in machine (A). But we intend to put the CMS DB into another machine (B) which is also an oracle 10g. Tnsnames are set. And all tables have been replicated from original DB A to
destination DB B. However, when we choose copy datasource from to option, it asked us to provide cluster key of destination. that shud be the same cluster passcode as in A. But it said its incorrect.
One more info to share is that our original db A is non-unicode.
But the destnation DB B is a unicode db. Will this affect the cluster key ?
thanks
Clement.store
clement.store 
(BOB member since 2008-08-26)