In this article we will look into all possible ways to migrate or copy the OTBI Analytics from one instance to other.
In the previous article we have looked into Migration of BI Reports. If you missed it, have a look at it to understand this further.
OTBI Analytics be migrated using the below three approaches:
We will look into these options in detail now.
Table of Contents
Migrate OTBI using Catalog files:
Like we did for BI Reports, this is the simple way out of all the other ways. Just click on Archive to download the catalog file and Unarchive this file in the target instance.
It will download the catalog file with naming convention as <OTBI Report Name>.catalog
Navigate to the required folder where the OTBI needs to be migrated and select the Unarchive option and browse for the catalog file from the above step.
Once we click OK, the OTBI will be migrated to target instance.
Migrate OTBI using XML code:
We can also migrate or copy the OTBI Analysis using XML file. Normally when the OTBI reports are shared on Cloud Customer Connect they share the XML file which can be used in any BI instance irrespective of the version of BI. The catalog files will work only if the BI version is same on both target and source instances. However this approach of migrating using XML works irrespective of versions.
First let’s look into where we can we find the XML for the OTBI.
Click on Edit for OTBI Analysis
Here we can find the Analysis XML section. We can copy the XML file and share it with others if you want to share the OTBI Anlaysis.
Similarly we can import the OTBI Analysis using the XML file by following below steps:
Create New Analysis
It will list all the subject areas for us to select the subject area to start with. As we are going to import the analysis from XML file, the subject area will be overridden by the XML. so choose any one of the subject area even if it is not the one that you intend to use.
Now we have to copy paste the XML that we want to use in the XML and click on the Apply XML.
Once we click Apply XML, the Analysis will be updated to reflect the OTBI that we are importing.. We can navigate to Criteria screen now to verify the changes.
Now we can save this analysis by clicking the save button.
This way we can Import/Migrate the analysis using XML option and this works irrespective of the source and target being on same/different BI versions.
Migrate OTBI using Logical SQL:
We can migrate the OTBI using Logical SQL option as well.
First we will see where we can find the Logical SQL for existing OTBI Analysis.
Similar to the above XML, we can find the Logical SQL on the advanced tab of the Analytics screen.
Now, let’s see how to create the OTBI analysis if we have the Logical SQL.
Create New Analysis.
Once we click OK the analysis will be imported and we can see the subject area, attributes and filters.
Note: If you create a new analysis using this Logical SQL, any hierarchical columns, member selection, groups or formatting will be stripped If the Analysis is using any of these then use other migration approaches.
Logical SQL is used to implement complex functionality that cannot be achieved using the seeded OTBI reporting.
Tip: Simplest of all is the migration using Catalog file. However most of the analytics are shared using XML or Logical SQL on Communities. So, knowing all approaches would help you to import those analytics.
Top 10 Popular Posts from our Knowledgebase
- DataFusing FREE Cloud based SQL Developer like tool for Oracle Cloud
- Core HR Entity Relationship Diagram (ERD) for HCM Cloud
- Most Frequently used Document IDs from Oracle Support
- FREE Oracle Training & Accreditation with Oracle Learning Explorer
- How HDL Transformation Formula works with ElementEntry Sample
- FREE Oracle Fusion Demo Instance (VISION) Access
- Top 10 FREE useful tools for Fusion Consultants
- Learning Fusion HCM Technical Skillset
- Sample HCM Data Loader (HDL) files for all Business Objects
- Most frequently used Tables list in Fusion HCM