2016/10/08

OBIEE 12C - Migrating from 11g to 12c

Migrating the metadata from OBIEE 11g ( 11.1.1.7+) to 12c is an out-of-place process performed using the 12c Migration tool.  The existing 11g system is kept intact and operational while the migration to 12c is taking place.

The migration tool is a simple JAR file that is copied from 12c system to 11g system and used to create the OBI 11g export bundle.

This post is to detail the steps required for generating the 11g export Bundle ready for migration to 12c system.





In this post, I will only be discussing the steps required to create the export bundle from 11g system and import into 12c system.

Export Bundle Creation :

  1. Generate the bi-migration-tool.jar file on 12c System.

    • Navigate to $DOMAIN_HOME/bi/bitools/bin directory
    • Run the command as below -


  2. You should see the file "bi-migration-tools.jar" file created, as below:


  3. Now copy the file "bi-migration-tool.jar" to 11g system to the directory                 $MW Home/Oracle_BI1

  4. Run the migration tool, from 11g Oracle Home to produce the export bundle.  The command for this is as below:


  5. $JAVA_HOME/bin/java -jar bi-migration-tool.jar out $MW_HOME/Oracle_BI1 $DOMAIN_HOME   $tgt_dir/11g_12c_export.jar

    The parameters are:

    • out : Used to indicate that the Migration tool is run in export mode
    • <Oracle 11g Home > : Used to specify Oracle 11g Home directory
    • <Oracle 11g Domain Home > :  Used to specify the 11g Domain Home directory.
    • <Target Directory for Export Bundle > : Used to specify the directory to store the Export Bundle file.

    The below screen shot shows the execution of the migration tool command:


Importing the 11g Export into 12c:

To migrate 11g to 12c follow these steps:
  1. Shutdown OBI 12c system, by running "stop.sh" command.

  2. Run the utility "migration-tool.sh" to import the 11g bundle, as below:



  3. In the above command, the parameters are -   
    • migration-tool.sh :  Shell script for importing the bundle
    • in : Used to indicate that the Migration tool is run in import mode
    • config : Used to specify that the BI Migration tool to over write the configuration files during import process
    • <Target Directory for Export Bundle > : Used to specify the location of directory & export file.
    • <Service Instance > : Used to specify the name of Service Instance.  
  4. Enter the RPD Password when prompted and monitor the progress. 



  5.   Monitor the Progress of import.



  6. Once the import process is successful, the below message will be displayed -



5 comments:

  1. Good Post.but i know this process will migrate catalog,rpd and security files all together.Do you know the process if we wanted to migrate only rpd from 11g to 12C ?

    Thanks

    ReplyDelete
  2. How to migrate 11g on Windows to 12c on Linux
    Generated bi-migration-tool.jar file on 12c , not work properly on Windows with java -jar ...

    ReplyDelete

File Handling with Python

This little utility is for copying files from source to target directories.  On the way it checks whether a directory exists in the target, ...