Skip to Content
avatar image
Former Member

Migration of CMS between MySQL and Oracle 10

Hi

I wonder if anyone can help with the problem I am experiencing.

I installed BO XI 3.1 SP2 onto a Windows 2003 server (no clustering - only one machine) using the default MySQL database for the CMS and Audit databases.

I now want to change the CMS database to be Oracle. I migrated the DB using SQL Developer which complained of two indexes SI_CUID and SI_GUID not being able to be created uniquely. The solution presented was to remove the unique statement from the script which I did and then ran the script successfully.

I'm now having difficulty in changing the configuration of the SIA properties.

There is a fix 'ADAPT01299996' in Service pack 3 which deals with the following:

"When Installing or re-initializing on a Unix or Linux system, the installation will sometimes fail because the Central Management

Server (CMS) displays an error message about duplicate Global Unique Identifiers (GUID), and then it terminates unexpectedly" Whilst the fix refers to Linux and Unix operating systems there are windows components on this fix?

I'm wondering if applying SP3 will resolve the issue?

Appreciate any comments?

Thanks

Karen

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jun 23, 2010 at 07:07 PM

    I would not recommend migrating from one db to another in this fashion.

    I would suggest that you create a BIAR file with the entire contents of the mySQL CMS, then drop and re-create your Oracle instance, then using the Central Configuration Manager, specify your CMS Data Source as the Oracle db and re-initialize it. Let BOBJ create the tables and indexes again as it needs to. Then use the Import Wizard and pull your content back in from the BIAR file.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      This is what i suggest,

      Use the concept of BO Copy the CMS from One data source to another, which will be there under the CCM --> CMS ( properties) because if you recreated everything will be vanished which is going to be real pain.

  • avatar image
    Former Member
    Jun 24, 2010 at 12:03 PM

    Thanks for the replies. I used the Copy CMS option within th SIA properties and specified the source (MySQL) db and target (Oracle) db and the migration appears to be successful. What I believe made it work this time was stopping the CMS before the SIA (as I had tried this method before and it didn't work).

    Regards

    Karen

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Karen!

      The last time I migrated from MySQL to Oracle we had issues with the VARCHAR setting in Oracle. Oracle was set to CHAR and BO XI could not deal with, so we set it in the session to BYTE.

      But beside that there were no other errors. So your Copy CMS should do the work.

      I would basically use the Export Tool to create a BIAR which holds Repository and Files. And you can install the BIAR on a new server without much hassle.

      ciao Hakan

      PS: Did you try this in your testenvironment? So do you need to change the unique constraint also when you have a new installation without any data in the repository?