I am supporting version 3.1 and version 4.1.3 of business objects. We are going to move the repositories from an Oracle 7.1 database to Oracle 7.3. Will this be as simple as changing the connection strings? Or, do I need to create a new dict.key and bomain.key file and redistribute them? I’m assuming the queries will be unaffected.
Julie,
If I understand this correctly, Oracle is being upgraded from v7.1 to 7.3 but the databases connections aren’t necessarily changing. If this is the case you will
not have to change a thing. However, if with the upgrade the connections to the repository database change, then you will have to redistribute both the dict.key and bomain.key.
I am supporting version 3.1 and version 4.1.3 of business objects. We are going to move the repositories from an Oracle 7.1 database to Oracle 7.3. Will this be as simple as changing the connection strings? Or, do I need to create a new dict.key and bomain.key file and redistribute them? I’m assuming the queries will be unaffected.
Good morning,
We are going to move the repositories from an Oracle 7.1 database to Oracle 7.3. Will this be as simple as changing the connection strings? Or, do I need to create a new dict.key and bomain.key file and redistribute them? I’m assuming the queries will be unaffected.
Thanks,
Julie
Hi Julie,
I too have supported both 3.1.1 and 4 versions…fun, isn’t it!
In answer to your question: If the database is simply being upgraded, you will be all set. However, if you are moving to a different physical box (i.e. new connection strings required), then you will indeed have to create new dict.key/bomain.key files and redistribute. Are you running a Master/Shared setup? If so, you would only need to place the new bomain.key onto the ShData folder on the server, and everyone would use this “centralized” key.
In the next couple of days I have to move the BO repository from one Unix
box to an other one. Does any of you have experience with this?
What is the best way to tackle this problem? I guess it is not only a
matter
of backup and restore it on an different machine and than edit all the
connections.
Thanks
Huub
The easiest method I have used is to
Backup and Restore the Repository - This will move the repository to the
new box.
Go in as the General Supervisor and recreate the BOMAIN.KEY using the
new repository location.
It really is not too difficult. The major things you have to do are:
1) Backup and restore d/b
2) Create new BOMAIN.KEY based on new connection using safe recovery.
3) Connect to new repository and modify connection to other domains
(document, universe)
4) Modify all other secured and personal connections.
Make sure you pay particular attention to step 3...failure to do this
correctly will result in a big mess, particularly if you use Doc
Agent. You should be aware that version 4.1.2 had a bug preventing
modification of these domains...make sure you are using a version
prior to 4.1.2 or after.
Jason Beard
----------------------------------------------------------------------
In the next couple of days I have to move the BO repository from one Unix
box to an other one. Does any of you have experience with this?
What is the best way to tackle this problem? I guess it is not only a matter
of backup and restore it on an different machine and than edit all the
connections.
We would like to move our repository which currently resides in Informix to SQL Server. Users will already have BusinessObjects (5.0.3) installed with both the Informix and SQL Server drivers. Here’s what I think I will need to do:
Create the new repository database from scratch using Supervisor. This will create a new BOMain.key
Copy all the data in the repository database, table by table, from the Informix tables to tables with the same name in SQL Server.
Do a “Scan and Repair” on the new repository.
Make sure users have the SQL Server driver (ODBC) installed on their PCs.
Have users use the new BOMain.key instead of the old one.
Are there any other steps that you would recommend? Will copying the data from like named tables work or do I need to re-build everything from scratch (e.g. re-define all the user names, groups and passwords, and export all the corporate documents to the repository again)?
Any tips are welcome.
====================================
Dennis Edgecombe
Washington State University
If you create a new BOMAIN.key without changing the file’s name you may have to delete the old BOMAIN.lsi file. This file is created the first time you log in and I once had a problem where the new BOMAIN.key was not compatible with the old BOMAIN.lsi file.
Hope this helps
We would like to move our repository which currently resides in Informix to SQL Server. Users will already have BusinessObjects (5.0.3) installed with both the Informix and SQL Server drivers. Here’s what I think I will need to do:
Have users use the new BOMain.key instead of the old one.
Are there any other steps that you would recommend? Will copying the data from like named tables work or do I need to re-build everything from scratch (e.g. re-define all the user names, groups and passwords, and export all the corporate documents to the repository again)?
make sure after the load into Informix, that you re-create the repository connections in the Supervisor for all universe/doc repositories in your system. This info is stored in the security domain as well and therefore still points to the “old” database…
hope this helps…
Walter
Dennis Edgecombe schrieb:
We would like to move our repository which currently resides in Informix to SQL Server. Users will already have BusinessObjects (5.0.3) installed with both the Informix and SQL Server drivers. Here’s what I think I will need to do:
Create the new repository database from scratch using Supervisor. This will create a new BOMain.key
Copy all the data in the repository database, table by table, from the Informix tables to tables with the same name in SQL Server.
Do a “Scan and Repair” on the new repository.
Make sure users have the SQL Server driver (ODBC) installed on their PCs.
Have users use the new BOMain.key instead of the old one.
Are there any other steps that you would recommend? Will copying the data from like named tables work or do I need to re-build everything from scratch (e.g. re-define all the user names, groups and passwords, and export all the corporate documents to the repository again)?
–
DI Walter Muellner
Leiter Bereich Consulting
Delphi Software GmbH, Vivenotgasse 48, A-1120 Vienna / Austria Tel: +43-1-8151456-12, Fax: +43-1-8151456-450 e-mail: w.muellner@delphi.at, WEB: http://www.delphi.at
I need to move my repository (security, universe & document domain) from one database to another database running on different box. Both the databases are Oracle with same version. I have exported all the objects of under the schema and imported it to the other database with same schema name. Now when I am trying to create the BOMain.key afresh it is not recognizing the security domain.
Is anyone come across this type of situation/error? Any suggestion to solve the problem will be a great help.
Thanks in advance.
Gouri
_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com
You probably haven’t done what you wanted to do. You need to backup and restore the OBJ_, UNV_, and DS_ tables. If you do this, you should be OK to build a new key file pointing to the other server.