Вы находитесь на странице: 1из 36

Migrating Oracle BI Discoverer Metadata

to Oracle BI Enterprise Edition

February 2013

Revision 10.1.3.4.1.34

Includes details of using the


Discoverer Metadata Migration Assistant (DOMA)
Contents
CONTENTS ................................................................................................................................................. 2
1. INTRODUCTION .............................................................................................................................. 4
1.1 ORACLE BI SERVER .......................................................................................................................... 4
1.2 ORACLE BI ADMINISTRATION TOOL ................................................................................................ 4
1.3 ORACLE BI INTERACTIVE DASHBOARDS ......................................................................................... 5
1.4 ORACLE BI ANSWERS....................................................................................................................... 5
1.5 ORACLE BI DELIVERS ...................................................................................................................... 5
1.6 ORACLE BI PUBLISHER..................................................................................................................... 5
1.7 ORACLE BI DISCONNECTED ANALYTICS ......................................................................................... 5
1.8 ORACLE BI APPLICATIONS ............................................................................................................... 6
2. DISCOVERER TO OBI EE MIGRATION ASSISTANT .............................................................. 7
2.1 SUITABILITY OF THE MIGRATION ASSISTANT .................................................................................. 7
2.2 PRE-REQUISITES ............................................................................................................................... 8
2.2.1 Windows XP .............................................................................................................8
2.2.2 Discoverer EUL .......................................................................................................8
2.2.3 Install Java ...............................................................................................................8
2.2.4 Tm-extractors-0.4.jar ...............................................................................................8
2.3 INSTALLING THE PACKAGE .............................................................................................................. 8
2.4 INSTRUCTIONS FOR USING DOMA ................................................................................................. 12
2.4.1 Export Discoverer metadata ...................................................................................12
2.4.2 Using the overall command line executable ..........................................................12
2.4.3 Usage Notes ...........................................................................................................13
2.4.3.1 Editing translateMyEul.bat ....................................................................................13
2.4.3.2 Running Migrate.bat ..............................................................................................13
2.4.3.3 Running WorkbookXMLGen.bat ..........................................................................14
2.4.3.4 Running MigrateWorkbooks.exe ...........................................................................14
2.4.4 Migration Log Files ...............................................................................................15
2.4.5 Migration exception log .........................................................................................18
2.4.6 Configuration options ............................................................................................19
3. PROBLEMS AND DETOURS .......................................................................................................... 20
3.1 CALC DECODE FOR CHARACTER DATA TYPES ................................................................................ 20
3.2 RPD WILL NOT CONNECT TO THE DATA SOURCE............................................................................ 20
3.1 PRESENTATION CATALOGS WITH EMPTY FOLDERS ........................................................................ 20
3.2 RPD MAY NOT RETURN ANSWERS RESULTS .................................................................................. 20
3.3 WORKSHEETS WITH AUTOGENERATE NAMES................................................................................ 20
3.4 DEPENDENCE ON VERSIONS OF DISCOVERER AND OBI EE ............................................................ 21
3.5 PRIVILEGE METADATA ................................................................................................................... 21
3.6 TITLE METADATA ........................................................................................................................... 21
3.7 TEXT FORMATTING ......................................................................................................................... 21
3.8 WORKBOOK METADATA ................................................................................................................ 21
3.9 CATALOG OBJECT SCHEMA VALIDATION FAILED ........................................................................... 21
3.10 JAPANESE WORKBOOK NAMES NOT TRANSLATED CORRECTLY ................................................. 22
4. DESCRIPTION OF RPD OUTPUT FROM DOMA .................................................................... 23
4.1.1 End User Layer ......................................................................................................23
4.1.2 Business Areas .......................................................................................................23
4.1.3 Simple Folders .......................................................................................................23

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 2 of 36
4.1.4 Complex Folders ....................................................................................................23
4.1.5 Custom Folders ......................................................................................................24
4.1.6 Items .......................................................................................................................25
4.1.7 Joins .......................................................................................................................26
4.1.7.1 Multiple Join Paths ................................................................................................27
4.1.7.2 Circular Joins .........................................................................................................29
4.1.7.3 Duplicate Joins .......................................................................................................30
4.1.7.4 Notes on Migrating Joins .......................................................................................30
4.1.8 Conditions ..............................................................................................................31
4.1.8.1 Mandatory Conditions ...........................................................................................31
4.1.8.2 Optional Conditions ...............................................................................................31
4.1.9 Aggregate Calculated Items ...................................................................................31
4.1.10 Item hierarchies ......................................................................................................32
4.1.11 Discoverer Date Hierarchies ..................................................................................33
4.1.12 Item Classes ...........................................................................................................33
4.1.13 Summary Folders ...................................................................................................33
4.2 DESCRIPTION OF CATALOG OUTPUT FROM DOMA........................................................................ 33
4.2.1 Workbooks .............................................................................................................33
5. HOW DOMA TRANSLATES RPD METADATA ....................................................................... 34
5.1.1 Measures ................................................................................................................34
5.1.2 Facts and Dimensions ............................................................................................34
5.1.3 Key Columns .........................................................................................................34
5.1.4 Migrating Folders without Joins ............................................................................34
5.1.5 Creation of Alias Objects .......................................................................................35
5.1.6 Aggregates and Calculations..................................................................................35
5.1.7 User Privileges .......................................................................................................35
5.2 EVALUATING THE OUTPUT FROM DOMA ...................................................................................... 35
5.2.1 Use of the EUL_DATE_TRUNC function ............................................................36
5.2.2 Joins Involving Different Data Types ....................................................................36

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 3 of 36
1. Introduction
This document provides a single source of information about translating the metadata
from an Oracle BI Discoverer system to that which can be used by Oracle BI
Enterprise Edition (Oracle BI EE).

Oracle BI EE is an innovative and comprehensive BI platform that delivers the full


range of BI capabilities on a next-generation architecture designed for true enterprise
deployment. It enables organizations to define a single, logical view of all enterprise
data, whether in a single data warehouse or across multiple operational and analytic
sources. Business users benefit from new levels of self-sufficiency to access, interact
with, and utilize this information to increase effectiveness.

1.1 Oracle BI Server


The Oracle BI Server sits at the heart of Oracle BI EE generating optimized queries
across multiple data sources and presenting end users with a single, easy to use,
logical model of their business. This can benefit end users in many ways such as
being able to present a single graph with order data, receivables data and forecast all
coming from different sources. In addition, the Oracle BI Server can act as an ODBC
data source, allowing querying of the metadata through tools such as Excel or other
third party applications.

The Oracle BI Server includes a multi-user data cache that provides high scalability
and improved query performance. Cache administration is carried out from the Oracle
BI Administration Tool where metadata objects can be flagged as being cacheable in
the physical layer. Other benefits of the Oracle BI Server include clustering capability
enabling high availability and ability to use a variety of enterprise security models.

1.2 Oracle BI Administration Tool


The metadata that is used by the Oracle BI Server is created using the Oracle BI
Administration Tool. This is comparable to Discoverer Administrator. The Oracle BI
EE metadata is contained within a file known as an .RPD file. This is the equivalent
of a Discoverer EUL. A Discoverer business areas is roughly equivalent to a
presentation layer catalog that are called subject areas within Oracle BI Answers.

There is a key difference between the metadata models of the two products whereby
BI EE metadata consists of three layers. A Physical Layer contains the mappings to
the objects that hold the data e.g. a database, MS Excel spreadsheet, XML file etc.
This layer also contains information about how the mappings relate to each other in
the form of primary/foreign keys. The Logical or Business Model Layer contains
mappings of how objects in the physical layer relate to each other. Key differences
with Discoverer are the creation of dimensions and facts leading to the ability to
define level based measures. The Presentation Layer contains the view of the
metadata that the end users see. It is possible to view a diagrammatic representation of
both the physical model (i.e. database model) and logical business model layers. The

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 4 of 36
benefit of this is a clear and quick understanding of how the metadata objects are
related.

The Oracle BI Administration tool provides support for multi-user BI metadata


administration (including a check in/out model) and multi-language metadata. The
Oracle BI EE metadata can span multiple heterogeneous data sources, share common
dimensions between multiple subject areas and therefore provides a common and
consistent reporting framework across all business functions.

1.3 Oracle BI Interactive Dashboards


Oracle BI Interactive Dashboards provide a fully interactive collection of analytic
content with a rich variety of visualizations in a pure thin client. Guided navigations
and alerts drive the user to greater insight to take the right actions at the right time for
their business. This is comparable to the Discoverer Portlet provider. The BI
Interactive dashboards are easier to use and offer a greater presentation and
visualization capabilities.

1.4 Oracle BI Answers


Oracle BI Answers is a pure thin client ad-hoc query and analysis tool with a simple
point and click interface for building queries. Users interact with a business friendly
view of their data. This is comparable to Discoverer Plus and Viewer. In Answers, a
query is known as a request. This is equivalent to a Discoverer worksheet. Answers
requests are stored in a catalog either in a user’s personal area or in a shared area.
There is full support in the catalog for organizing requests in folders and subfolders.

1.5 Oracle BI Delivers


Oracle BI Delivers enables pro-active notification, monitoring and alerting and report
distribution to multiple channels such as email, dashboard alerts and mobile devices.
It includes a web based interface for creation of alerts (known as iBots) and the ability
to execute other iBots, scripts or Java programs to build up analytic workflows. There
is no comparable alerting and distribution functionality in Discoverer other than the
ability to schedule worksheets and share the results with other users of the system.

1.6 Oracle BI Publisher


Oracle BI Publisher enables pixel-perfect reports to be generated using Answers
requests as the source. MS Word or Adobe Acrobat can be used to layout reports and
create templates. There is no equivalent functionality in Discoverer. Note that BI
Publisher also integrates with Discoverer as a source.

1.7 Oracle BI Disconnected Analytics


Oracle BI Disconnected enables the capabilities of Interactive Dashboards and
Answers but available offline via data synchronization between the mobile client and
central BI Server. There is no equivalent in Discoverer.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 5 of 36
1.8 Oracle BI Applications
The Oracle BI Applications are a complete prebuilt BI solutions that deliver intuitive,
role based intelligence for everyone in an organization. They consist of ETL adapters,
metadata, dashboards and KPIs built to industry best practices to gain insight from
applications including Siebel, Oracle E-Business Suite, PeopleSoft Enterprise, JD
Edwards and SAP.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 6 of 36
2. Discoverer to OBI EE Migration Assistant
This section describes and provides instructions for using the Discoverer to OBI EE
Migration Assistant (DOMA). This is a command line utility that greatly accelerates
the translation of Discoverer metadata from the EUL to Oracle BI EE.

2.1 Suitability of the Migration Assistant


There are several types of system that Discoverer can be used to report against:

 Data warehouse i.e. a star or snowflake schema. This is the optimum type of
metadata to use with DOMA and due to the nature of the Oracle BI EE
business model layer generates metadata that in the majority of cases needs
few manual changes before being able to create queries.

 Custom built OLTP schema. This type of metadata will probably need manual
changes after being run through DOMA as the Discoverer metadata can
contain join mappings that do not directly translate to the Oracle BI EE
business model layer e.g. multiple join paths between folders and circular
joins. DOMA can cope with these scenarios by the optional creation of
additional objects in the BI EE metadata logical layer e.g. alias dimension or
fact tables. Further details can be found later in this document.

 Discoverer reporting on Oracle Applications e.g. Oracle BIS or custom built


systems. Oracle recommends customers evaluate the Oracle BI Applications in
these scenarios as they offer the fastest time to value using prebuilt data
warehouse star schemas, ETL routines and Oracle BI EE metadata and
dashboards built to best practices.

DOMA is a free tool kit. It is made available via the Oracle Technology Network on
an as is basis without any provision of support or plan for any additional
enhancements. While every care has been taken with the production of the tool kit,
there are no warranties of any sort made on the outcomes it produces.

While Oracle BI Discoverer and Oracle BI EE are both tools that provide end users
with information sourced from databases, their approach to this is significantly
different, and complete translation of metadata is not possible.

DOMA provides an excellent starting point for evaluating what an OBI EE based
environment can look like, but as with any move to a new environment, a direct
transplantation may not provide the business benefits that the new environment can
deliver. Consideration should be given as to whether aspects of the current reporting
metadata design exist to suit Oracle BI Discoverer rather than the business needs that
the tool serves. Often a fresh approach delivers many more benefits than a literal
translation.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 7 of 36
2.2 Pre-requisites
2.2.1 Windows XP
The DOMA only works on workstations running Windows XP or a virtualized
environment that emulates this operating system.

2.2.2 Discoverer EUL


The minimum version of Discoverer EUL that can be used with DOMA is 10.1.2.n.
If you have an older version, you should download Discoverer 10.1.2.n and create
your eex file using that.

2.2.3 Install Java


A recent version of Java is required for DOMA to run. For example 6.0.25 or later.
Once installed please check to ensure that your PATH variable includes that version
of Java.

2.2.4 Tm-extractors-0.4.jar
DOMA also depends on the above jar file to perform its work. The file
tm-extractors-0.4.jar must be downloaded into the java\lib folder of DOMA’s release
package. One source for this file is
http://mirrors.ibiblio.org/pub/mirrors/maven/org.textmining/jars/tm-extractors-0.4.jar

2.3 Installing the Package


Copy the zip file to your C:\ drive and unzip the contents. The following structure
will be created by default. Both the disk location, and the name of the topmost folder
can be changed, The subfolders (other than Sample) and their contents should not be
renamed.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 8 of 36
File / Folder Description
Doma_bin Contains all the executables released with the Discovere to OBI
EE Migration Assistant (DOMA).
Migrate.bat Orchestrates the process of migrating the
EUL and workbooks to OBI EE. This
must be run in a command window and
takes a minimum of 2 arguments, the name
of .eex file and the location of where the
intermediate workbooks .xml file should be
placed
setEnvironment.bat Sets variables and updates the path settings
required by DOMA. Migtate.bat saves the
PATH when it starts, calls
setEnvironment.bat, then the other
components. Finally it restores the original
path statement.
DOMA_cat Is the folder into which the generated Answers reports will be
placed. This folder must be created by the user, or if the generate
process is to use another folder, then the file
C:\Doma\OracleBIData\web\config\ instanceconfig.xml must be
modified to reference another folder that exists.

Java\lib This contains jar files required by DOMA. This release excludes
the tm-extractors-0.4.jar which cannot be distributed for legal
reasons. This jar file is required and must be downloaded into
this location by users.
Sample & Contains a command file and a sample eex file to quickly test the
..\hrsample translation of its metadata. This serves as an example that you
can replicate or replace with your own .eex file for your own
translation
translateMyEUL.bat Can be double clicked in Windows
Explorer to call Migrate.bat to orchestrate
the translation processes for the
hr_sample.eex. This can be edited to allow
you translate your own custom .eex file
OracleBIData, Contains the OBI EE elements that are called by DOMA to
server & web perform the migration. These elements are from the OBI EE 10g
release, so the resulting RPD and Answers reports need to be
upgraded to whatever version of OBI EE is installed at the
customer site.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 9 of 36
Note: tm-extractors-0.4.jar is not included in the release package and needs to
be downloaded into this folder.

This folder and its contents are provided as an example.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 10 of 36
File / Folder Description
hrsample.eex Is the extracted Discoverer End User Layer and a set of
Workbooks
The resulting RPD file and the logs that document the actions
taken during the translation of the EUL to an RPD will also be
placed here

Move to the Doma\OracleBIData\web\config folder

Edit the instanceconfig.xml file – for the supplied sample the current value is shown
on line 5 of the screen shot below

Optionally change this and save the file.

You are now ready to translate the metadata in the supplied hr_sample.eex

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 11 of 36
2.4 Instructions for using DOMA
2.4.1 Export Discoverer metadata
The first stage in the process is to export the Discoverer metadata you wish to
translate to an .eex file using the Discoverer Administration tool. This document
assumes familiarity with the Discoverer product but details of this process can be
found online in the section About using the Discoverer Export Wizard and Import
Wizard in the Discoverer Administration Guide:

http://download.oracle.com/docs/pdf/B13916_04.pdf

You should export the workbooks as well as the EUL at the same time.

2.4.2 Using the overall command line executable


DOMA is provided as a set of command line executables that must be run on a
Windows machine. Oracle BI EE does not need to be installed for DOMA to work,
the release bundle contains library the pre-requisite software from the OBI EE
installed environment to help it generate the required output.

The release bundle includes a sample that you can use as a template and then modify
if required. The command file translateMyEUL.bat works with the exported EUL file
called hr_sample.eex, the folder hrsample and its sub-folders.

Make sure that new_workbooks are empty and edit the file
Doma\OracleBIDate\web\config\instanceconfig.xml as described earlier.

After the RPD file has been generated, open this file using the Oracle BI EE
Administration Tool to update the connection pool settings to point to the data source
being used, run a consistency check and save these changes to the RPD file.

The rpd file is named <eex_file>.rpd – for the hr_sample.eex sample provided that
will be hr_sample.rpd.

The sequence of execution is as follows

1 <Assistant>\translateMyEUL.bat calls
1.1 <Assistant>\bin\Migrate.bat calls
1.1.1 <Assistant>\bin\MigrateEUL.exe to create the RPD
1.1.2 <Assistant>\bin\WorkbookXMLGen.bat calls
1.1.2.1 Java to generate the XML from the .eex file
1.1.2.2 <Assistant>\bin\MigrateWorkbooks.exe to create the webcat

Step 1 can be run after editing the bat file to make use of a different .eex file
and folder structure
Step 1.1 can be run with custom initiating parameters (equivalent to the edits in
Step 1) to generate an RPD and the webcat files – see the usage notes
later
Step 1.1.2.2 can be run separately to read the XML files and create the webcat. If
some workbooks are causing a problem their XML can be selectively
removed to detour any such problems

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 12 of 36
2.4.3 Usage Notes

2.4.3.1 Editing translateMyEul.bat


This command file assumes the folder structure of the release bundle and that the
EUL to be translated will be in a folder of the same name. For example
hrsample.eex is will be in a folder called hrsample
financials.eex will be in a folder called financials

You can change highlighted items on line 3 of the command file as follows to make
this change

1. @echo off
2. rem MODIFY this value for your own EEX or replace hrsample.eex with yours
3. SET MYSAMPLE=hrsample
4. rem MODIFY this value if you need to set a font family eg ARIAL
5. SET FONTFAM=

The item on line 5 identifies a font family to be used when generating the Answers
reports. By default this is null, but in some cases following the upgrade of the catalog
to the most current version of OBI EE, when running a report you may get the
following error "Catalog object schema validation failed" and this may be
due to an invalid font family. Add a font family that is installed on the machine
running the presentation server. For example Arial or “Times New Roman” – note
that where the font family has a multi part name, enclose it with quotes.

2.4.3.2 Running Migrate.bat


You can run this command file as follows:

Call migrate.bat it 2 required parameters and 5 optional parameters.


Param Usage explanation
1 Full path to the EEX file to be migrated
2 Folder path where workbook xmls will be created
3 true / false (optional)
true – to create rpd (the default)
false – to skip rpd creation
4 true / false (ptional)
true – filters to be shown in Results page of Answers
false – filters not shown in Results page (the default)

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 13 of 36
Param Usage explanation
5 true / false (optional)
true – Use existing discoverer Worksheet format
false – Use OBIEE default format (the default)
6 1 / 2 (optional)
1 less logging (the default)
2 debug logging
7 Font Family Name (optional)

You will probably want to upgrade the generated RPD and Answers from the 10g
format to your current release. Information on how to do this is available in Oracle®
Fusion Middleware Upgrade Guide for Oracle Business Intelligence

Once upgraded to the required version, you should always open the final RPD and do
the following.
a) Set the credential for the data source – these are not migrated
b) Set the database properties to Default
c) Run the consistency checker
d) Save the updated RPD

2.4.3.3 Running WorkbookXMLGen.bat


You can run this command file to generate the workbooks XML passing it 2 required
parameters
Param Usage explanation
1 Full path to the EEX file to be used
2 Folder path where workbook xmls will be created

2.4.3.4 Running MigrateWorkbooks.exe


You can run this command file passing it 2 required parameters and 4 optional
parameters – generation of workbook XML is a prerequisite
Param Usage explanation
1 Full path to the EEX file to be used
2 Folder path where workbook xml is located
3 true / false (optional)
true – filters to be shown in Results page of Answers
false – filters not shown in Results page (the default)
4 true / false (optional)
true – Use existing discoverer Worksheet format
false – Use OBIEE default format (the default)
5 1 / 2 (optional)
1 less logging (the default)
2 debug logging
6 Font Family (optional)

Note: the folder in which the catalog files will be created is dictated by the setting
in the file Doma\OracleBIData\web\config\ instanceconfig.xml .

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 14 of 36
2.4.4 Migration Log Files
DOMA generates two log files that contain the following information:

<eex_file>.migration.log - captures the progress of metadata migration at a high level

<eex_ file>.exception.log - captures the items whose metadata could not be migrated
such as skipped joins and folders.

For each of the business areas whose metadata is translated, these files contain the
following details:

 The name of business area being processed


 Details of any joins in the Discoverer metadata that may be skipped due to the
existence of multiple join paths. For each skipped join, a ‘folder ID’ is
generated that can be used as a reference for a second run of DOMA with the
required folder IDs added to the ‘MigrationConfig.properties’ file in order to
generate folder aliases. The folder IDs are listed with the configuration file
option ‘IncludePathsForFolders’.

An example of the log file created by migrateEUL.exe is included below:

Oracle BI SE - EE Migration Assistant Version 10.1.3.4.1


Repository creation started...
****************************************************************
Business Area : HR - Current Employee Details
****************************************************************
-- Processing EUL Joins....
-- Processing Folder(s) based on EUL Joins....
## List of Folder(s) with SKIPPED JOINS / PATHS
FOLDER_ID SELECTED = ### FOLDER_NAME JOIN_NAME
--------------------------------------------
### FOLDER CONTAINER MAPPING ###
Mapping For Folder : HR: Countries : HR: Departments
Mapping For Folder : HR: Departments : HR: Departments
Mapping For Folder : HR: Employees : HR: Employees
Mapping For Folder : HR: Jobs : HR: Jobs
Mapping For Folder : HR: Locations : HR: Departments
Mapping For Folder : HR: Managers : HR: Managers
Mapping For Folder : HR: Regions : HR: Departments
-- Processing Complex Folder(s)....
-- Processing Dimension(s)....
************* CREATING PHYSICAL LAYER *************
-- Creating Database...[DONE]
-- Creating Connection Pool...[DONE]
-- Creating Physical Table(s)...
-- Physical Table(s) creation...[DONE]
-- Creating Physical Join(s)...
-- Physical Join(s) creation...[DONE]
************* PHYSICAL LAYER CREATION DONE *************
************* CREATING LOGICAL LAYER *************
-- Creating Subject Area...[DONE]
-- Creating Logical Table(s)...
-- Creating Logical Join(s)...
-- Logical Join(s) creation...[DONE]
-- Creating Calculation(s)...
- Creating Complex Folder Calculation(s)...
-- Calculation(s) creation...[DONE]
-- Logical Table(s) creation...[DONE]
-- Creating Dimension(s)...
Dimension : HR: Employees: Hire Date: Default Date Hierarchy

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 15 of 36
Dimension : Geography Hierarchy
-- Dimension(s) creation...[DONE]
************* LOGICAL LAYER CREATION DONE *************
************* CREATING PRESENTATION LAYER *************
-- Creating Presentation Folder(s)...
Folder : HR: Regions
Folder : HR: Countries
Folder : HR: Locations
Folder : HR: Departments
Folder : HR: Employees
Folder : HR: Managers
Folder : HR: Jobs
-- Presentation Folder(s) creation...[DONE]
************* PRESENTATION LAYER CREATION DONE *************
****************************************************************
Business Area : HR - Employee History
****************************************************************
-- Processing EUL Joins....
-- Processing Folder(s) based on EUL Joins....
## List of Folder(s) with SKIPPED JOINS / PATHS
FOLDER_ID SELECTED = ### FOLDER_NAME JOIN_NAME
--------------------------------------------
### FOLDER CONTAINER MAPPING ###
Mapping For Folder : HIST: Departments : HIST: Departments
Mapping For Folder : HIST: Employees : HIST: Employees
Mapping For Folder : HIST: Job History : HIST: Job History
Mapping For Folder : HIST: Jobs : HIST: Jobs
-- Processing Complex Folder(s)....
-- Processing Dimension(s)....
************* CREATING PHYSICAL LAYER *************
-- Creating Database...[DONE]
-- Creating Connection Pool...[DONE]
-- Creating Physical Table(s)...
-- Physical Table(s) creation...[DONE]
-- Creating Physical Join(s)...
-- Physical Join(s) creation...[DONE]
************* PHYSICAL LAYER CREATION DONE *************
************* CREATING LOGICAL LAYER *************
-- Creating Subject Area...[DONE]
-- Creating Logical Table(s)...
-- Creating Logical Join(s)...
-- Logical Join(s) creation...[DONE]
-- Creating Calculation(s)...
- Creating Complex Folder Calculation(s)...
-- Calculation(s) creation...[DONE]
-- Logical Table(s) creation...[DONE]
-- Creating Dimension(s)...
-- Dimension(s) creation...[DONE]
************* LOGICAL LAYER CREATION DONE *************
************* CREATING PRESENTATION LAYER *************
-- Creating Presentation Folder(s)...
Folder : HIST: Employee Job History
-- Presentation Folder(s) creation...[DONE]
************* PRESENTATION LAYER CREATION DONE *************
****************************************************************
Business Area : TEST Business Area
****************************************************************
-- Processing EUL Joins....
-- Processing Folder(s) based on EUL Joins....
## List of Folder(s) with SKIPPED JOINS / PATHS
FOLDER_ID SELECTED = ### FOLDER_NAME JOIN_NAME
--------------------------------------------
### FOLDER CONTAINER MAPPING ###
Mapping For Folder : Countries : Countries
Mapping For Folder : Regions : Regions
-- Processing Complex Folder(s)....
-- Processing Dimension(s)....
************* CREATING PHYSICAL LAYER *************

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 16 of 36
-- Creating Database...[DONE]
-- Creating Connection Pool...[DONE]
-- Creating Physical Table(s)...
-- Physical Table(s) creation...[DONE]
-- Creating Physical Join(s)...
-- Physical Join(s) creation...[DONE]
************* PHYSICAL LAYER CREATION DONE *************
************* CREATING LOGICAL LAYER *************
-- Creating Subject Area...[DONE]
-- Creating Logical Table(s)...
-- Creating Logical Join(s)...
-- Logical Join(s) creation...[DONE]
-- Creating Calculation(s)...
- Creating Complex Folder Calculation(s)...
-- Calculation(s) creation...[DONE]
-- Logical Table(s) creation...[DONE]
-- Creating Dimension(s)...
-- Dimension(s) creation...[DONE]
************* LOGICAL LAYER CREATION DONE *************
************* CREATING PRESENTATION LAYER *************
-- Creating Presentation Folder(s)...
Folder : Regions
Folder : Countries
Folder : Region Country
-- Presentation Folder(s) creation...[DONE]
************* PRESENTATION LAYER CREATION DONE *************

------------------- All Business Area(s) processed --------------- Creating Security


Filter(s)...
-- Security Filter(s) creation...[DONE]
-- Creating User(s)...
DISCOVERER
PUBLIC
HR
CONNECT
DBA
DELETE_CATALOG_ROLE
EXECUTE_CATALOG_ROLE
EXP_FULL_DATABASE
GATHER_SYSTEM_STATISTICS
HS_ADMIN_ROLE
IMP_FULL_DATABASE
PLUSTRACE
RESOURCE
SCHEDULER_ADMIN
SELECT_CATALOG_ROLE
XDBADMIN
XDBWEBSERVICES
-- User(s) creation...[DONE]
The migrated repository is saved at
C:\OracleDiscovererTranslation\hrsample\hr_sample.rpd
------------------------------------------
EUL MIGRATION SUCCESSFUL
------------------------------------------

An example of the log file created by DiscoWkbkXmlGen.jar is included below:

Aug 3, 2011 3:22:42 PM null


INFO: Creating Discoverer workbook xmls in Dir C:\OracleDiscovererTranslation\hrsample\new_workbooks\
Aug 3, 2011 3:22:42 PM null
INFO: Creating C:\OracleDiscovererTranslation\hrsample\new_workbooks\HR.xml
Aug 3, 2011 3:22:42 PM null
INFO: [Done]

An example of the log file created by migrateWorkbooks.exe is included below:

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 17 of 36
Oracle BI SE - EE Workbook Migration Assistant Version 10.1.3.4.1

Using Web Catalog : C:\OracleDiscovererTranslation\hrsample\new_webcat

Request creation started...

Discoverer Worksheet Format will be applied to Migrated Reports as per your Option:
Filters will be shown in Results page of Answers as per your Option:
*** Formula isEVALUATE('TO_CHAR(%1,''YYYYMMDD'' )' AS CHAR,NOW())
*** Formula isEVALUATE('TO_CHAR(%1,''YYYYMMDD'' )' AS CHAR,NOW())
*** Formula isEVALUATE('TO_CHAR(21)',)
Creating Request : discoverer.HR.Job History...[DONE]
Creating Request : discoverer.HR.Emp by Region (NOT IN)...
Token Conditions in Title is not supported, it will not be migrated[DONE]
Creating Request : discoverer.HR.Emp by Dept & Mgr...[DONE]
Creating Request : discoverer.HR.Employee Salary By Dept Custom Format (__)...
Token Conditions in Title is not supported, it will not be migrated[DONE]
Creating Request : discoverer.HR.Employee Salary By Dept Format Currency...
Token Conditions in Title is not supported, it will not be migrated[DONE]
Creating Request : discoverer.HR.Currency Format Only...
Token Conditions in Title is not supported, it will not be migrated[DONE]
Creating Request : discoverer.HR.CASE DECODE...[DONE]
Creating Request : discoverer.HR.CASE Complex...[DONE]
Creating Request : discoverer.HR.Concatenation...[DONE]
Creating Request : discoverer.HR.Substring...[DONE]
Creating Request : discoverer.HR.Parameter...
Token Parameters in Title is not supported, it will not be migrated[DONE]
Creating Request : discoverer.HR.Condition with OR...
Token Conditions in Title is not supported, it will not be migrated[DONE]
Creating Request : discoverer.HR.Format Tests...[DONE]
Creating Request : discoverer.HR.Calc Item Format...[DONE]
Creating Request : discoverer.HR.Crosstab Analysis...[DONE]
Creating Request : discoverer.HR.InitCap...[DONE]

Request creation Complete

---------------------------------------
WORKBOOK MIGRATION SUCCESSFUL
---------------------------------------

2.4.5 Migration exception log


An example of the exception log file created by MigrateEUL.exe is included below:

Oracle BI SE - EE Migration Assistant Version 10.1.3.4.1


****************************************************************
Business Area : HR - Current Employee Details
****************************************************************
## List of Folder(s) with SKIPPED JOINS / PATHS
FOLDER_ID SELECTED = ### FOLDER_NAME JOIN_NAME
--------------------------------------------

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 18 of 36
****************************************************************
Business Area : HR - Employee History
****************************************************************
## List of Folder(s) with SKIPPED JOINS / PATHS
FOLDER_ID SELECTED = ### FOLDER_NAME JOIN_NAME
--------------------------------------------
****************************************************************
Business Area : TEST Business Area
****************************************************************
## List of Folder(s) with SKIPPED JOINS / PATHS
FOLDER_ID SELECTED = ### FOLDER_NAME JOIN_NAME
--------------------------------------------

2.4.6 Configuration options


A configuration file MigrationConfig.properties is provided for the user to control
the migration behavior. The options available are as below:

Property Settings
CreateAggregatedCols TRUE - Columns with aggregations like SUM, MIN, MAX,
AVG and COUNT will be created for measure columns.
FALSE - Aggregated Columns will be created for measure
columns based on the DEFAULT AGGREGATION property
set in the EUL
CreateSeperateRPDs TRUE - Separate repository is generated for each business
area.
FALSE - All the business areas are migrated to a single
repository.
ExcludeJoins A comma separated list of JOIN_ID to be skipped during
migration. Any JOIN_ID listed here will get excluded during
migration.
ConsiderMultiplePaths TRUE - The migration assistant will accommodate the
joins that would be otherwise skipped during migration.
FALSE - The migration assistant will not accommodate
the joins skipped during migration.
IncludePathsForFolders Valid values are comma separated TABLE_IDs as
generated in the log file for the folders with joins that are
skipped to eliminate Circular and Multiple Join paths.
If ConsiderMultiplePaths property is TRUE
 AND IF there are no values specified for
IncludePathsForFolders then
all the Skipped Joins will be migrated.
 If there are values specified, then the joins for these are
migrated.
If ConsiderMultiplePaths property is FALSE
It will not consider IncludePathsForFolders values
Connection pool DataSourceName, Username
parameters

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 19 of 36
3. Problems and Detours
This section provides a list of known problems that are not feasible to fix and require
detours

3.1 Calc decode for character data types


Operations involving columns of data type VARCHAR are permitted in Discoverer
with numeric.values. OBI EE is stricter and requires the numbers to be surrounded by
single quotes.

In such cases Answers will display an error such as


“SQL ERROR:Data type doesn't match, Char is Expected but Number”
The detour to this problem is to edit the column with the problem and add single
quotes around the numbers.

3.2 RPD will not connect to the data source


The Migration Assistant does not transfer database credentials to the RPD, so these
have to be manually supplied. After you have done this verify consistency and save.

3.1 Presentation catalogs with empty folders


Some RPDs generate errors in NQServer.log of the form
[14054] Unable to load subject area: XXXXXX.[nQSError: 15001]
Could not load navigation space for subject area XXXXXX.
[nQSError: 42001] Missing repository object with ID=0:0.

In a number of cases, the subject area contains empty folders as well.

To detour the problem


 open the RPD using Admin tool
 Set the database credentials as described above
 Run the consistency checker
 Save the RPD

3.2 RPD may not return Answers results


The Migration Assistant can take an .EEX file and generate an RPD. This RPD may
fail to return results to Answers even if it does return results via a right click of a
physical Table in the Admin tool.

To detour this problem, use the Admin tool to go to the Database properties and reset
its features to Default. After you have done this verify consistency and save.

3.3 Worksheets with Autogenerate Names


Any worksheet items with names defined as AUTO_GENERATED_NAME n,
cannot be migrated. Examples of this kind of worksheet are found in Video

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 20 of 36
store tutorial sample workbooks. If “generate column name automatically” is
selected in Discoverer, then the XML for the worksheet, does not contain a
real column name as Discoverer dynamically generates this. Consequently a
report cannot be built because there is no way to identify what RPD column to
use.

3.4 Dependence on versions of Discoverer and OBI EE


The minimum version of Discover required is 10.1.2.1 – the Discoverer environment
must be upgraded to this level or later before the Migration Assistant can deal with
the exported .EEX files.

The only supported version of OBI EE is 10.1.3.4.1 and the required components
from this are included with the DOMA bundle – the RPD and Answers reports
generated must then be upgraded using the upgrade tools available with the specific
version of OBI EE 11g that the customer has deployed.

3.5 Privilege Metadata


No privilege metadata is migrated as OBI EE has its own specific privilege and
security features and there is no simple mapping between the tools. This set of
privileges includes Product, Workbook, Worksheet, Query Governor,

3.6 Title metadata


The following title meta data is not taken across to Answers reports
Workbook Name, Worksheet Name, Conditions, Data points, Axis Items, Page Items,
Parameters

3.7 Text formatting


The following formatting is not taken across to Answers reports
Uppercase, Lowercase, Capitalized,

3.8 Workbook Metadata


The following workbook metadata will not be migrated.
Options, Filter Drills, N-pass filters, PL/SQL functions

3.9 Catalog object schema validation failed


In some cases following the upgrade of the migrated catalog to the most current
version of OBI EE, you may get the following error "Catalog object schema
validation failed" when running a report.

This may be due to an invalid font family. In this case you need to specify a font
family that is installed on the machine running the presentation server. For example
Arial or “Times New Roman” – note that where the font family has a multi part name,
enclose it with quotes.

This optional parameter needs to be given to MigrateWorkbooks.exe either directly or


via the command files provided.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 21 of 36
3.10 Japanese workbook names not translated correctly
The character set encoding in the Oracle database used to create the EUL needs to be
UTF-8 otherwise the folder name generated may contain invalid characters.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 22 of 36
4. Description of RPD output from DOMA
This section describes the mappings used by DOMA for the metadata properties in
Discoverer Administrator. Where there is no equivalent property in Oracle BI EE this
is indicated by ‘n/a’. It also describes any assumptions that DOMA makes when
creating the three layers that make up the Oracle BIEE metadata model.

4.1.1 End User Layer


The Discoverer End User Layer (EUL) maps to a BIEE metadata repository file (.rpd
file).

4.1.2 Business Areas


Business Areas map to a presentation catalog also known as a subject area in BI
Answers.

4.1.3 Simple Folders


Discoverer simple folders are mapped against database tables or views. They
correspondingly migrate to physical tables in the physical layer, logical tables in the
business model layer and to presentation tables in the presentation layer. The tables
only migrate to the presentation layer if they are set to be visible to users in
Discoverer. The following table summarizes how the properties are migrated.

Discoverer Target Property Target Property Target Property


Property In Presentation Layer In Logical Layer In Physical Layer
Name Table name Table name Physical table
Description Table description Table description Table description
Visible to Will not appear in n/a n/a
User this layer if set to NO
Database n/a n/a DB user in
connection pool
Owner n/a n/a Physical layer
schema
Object n/a n/a Physical layer table
Optimizer n/a n/a Physical table ‘hint’
Hints property in ‘general
tab of table
properties
Identifier n/a n/a n/a

4.1.4 Complex Folders


Discoverer complex folders are used to combine items from multiple simple folders.
The analogy often used to describe complex folders is that of a database view. From a

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 23 of 36
Discoverer administration perspective, they are useful for combining items into
logical groups to simplify the end users view of the metadata. From an end users
perspective, this can make life easier as they only need to go to a single folder to get
all the items they need for a report rather than multiple folders.

Discoverer Target Property Target Property Target Property


Property In Presentation In Logical In Physical Layer
Layer Layer
Name Table name Table name n/a
Description Table description Table n/a
description
Visible to User Will not appear in n/a n/a
this layer if set to
NO
Optimizer Hints n/a n/a n/a
Identifier n/a n/a n/a

Complex folders will be mapped to a logical table in the Logical Layer having a
Logical Table Source that contains the base folders and the joins between them. This
folder in turn will be joined to those base folders, which are Dimensions.

Complex folders appear in the Presentation Layer with the following mapping:

 The item references of the complex folder will be picked from the respective
base folders in the logical layer.
 For creating the Discoverer ‘admin calculations’ within a complex folder, a
logical table corresponding to the complex folder will be created in the logical
layer.. Those calculations involving items from more than one base table will
be created in the Complex Folder. The Logical Folder will then be moved to
the presentation layer. However, if the ‘admin calculations’ are based on a
single base folder, they will be migrated to the corresponding Logical folder
and not the Complex Folder.

Note that complex folders based on items from another complex folder cannot be
migrated automatically.

4.1.5 Custom Folders


Custom folders enable flexibility in folder creation – e.g. SQL statements using set
operators (e.g. UNION, INTERSECT, MINUS). On entering a SQL statement in the
UI for creating a custom folder, a folder is created containing items that are
referenced in the SQL statement. In Oracle BI EE the custom folders are migrated to
the physical layer with a table type of ‘select’. This is also known as an opaque view.

Discoverer Target Property Target Property Target Property


Property In Presentation In Logical In Physical Layer
Layer Layer
Name Table name Table name Table name
(type = select)

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 24 of 36
Description Description Description Description
Visible to User Will not appear in n/a n/a
this layer if set to
NO
Valid Will not appear in n/a Only created if its
this layer if not valid
valid
Custom SQL n/a n/a Default
initialization string
Identifier n/a n/a n/a

4.1.6 Items
Items are the basic building block for queries. They are mapped to columns in
database tables or views or created from calculations in Discoverer Administrator.
These calculations can be based upon PL/SQL functions. Discoverer items migrate to
physical columns in the physical layer, logical columns in the business model layer
and presentation columns in the presentation layer of Oracle BI EE. Only items that
are not hidden from end users will appear in the presentation layer.

Discoverer Target Property Target Property Target Property


Property In Presentation In Logical Layer In Physical
Layer Layer
Name Column name Column name Column name
Auto generate n/a n/a n/a
name
Description Description Description Description
Data type n/a Datatype Datatype
Formula n/a Column formula in n/a
the logical table
source (LTS)
physical mapping
Database n/a n/a n/a
column
Visible to user Will not appear in n/a n/a
this layer if set to
NO
Item class n/a n/a n/a
Date hierarchy n/a n/a n/a
Default position n/a n/a n/a
Default n/a Default aggregation n/a
aggregate rule for the column.
Heading n/a n/a n/a
Format mask n/a n/a n/a
Alignment n/a n/a n/a
Word wrap n/a n/a n/a
Case storage n/a n/a n/a
Display case n/a n/a n/a
Default width n/a n/a n/a

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 25 of 36
Replace NULL n/a n/a n/a
with
Content type n/a n/a n/a
Alternative n/a n/a n/a
display value
Max char n/a n/a n/a
fetched
Indexed item n/a n/a n/a
Identifier n/a n/a n/a

In Discoverer, when building a query, end users are able to use either the default
aggregation for an item or select from a list of available aggregation functions. In
Oracle BI EE metadata, it is possible to specify the default aggregation for a particular
column in the logical layer, however this aggregation cannot be changed (in a similar
manner to Discoverer) during the creation of the answers worksheet. The user needs
to create another column and define the required aggregation.

In order to offer end users a similar experience for selecting aggregations the
migration has an option to create a separate column in the logical layer for each
default aggregation that is supported in Discoverer. This configuration option is
CreateAggregatedCols. If set to TRUE while migrating, all aggregations supported by
Discoverer will be generated. If set to FALSE then a column with its aggregation
function set to the Discoverer ‘default aggregation’ will be created.

Discoverer calculated items based on Oracle PL/SQL functions or Oracle analytic


functions will be migrated to Oracle BI EE metadata that uses the EVALUATE and
EVALUATE_AGGR functions. These calculations will be created as a logical
column with its formula being set in the Physical Mapping of the Logical Table
Source.

4.1.7 Joins
Joins in Discoverer metadata define relationships between the folders that are used for
building queries. Usually joins are defined using the corresponding key columns of
the underlying database objects. Due to the differences in the metadata models
between Discoverer and Oracle BIEE there are some differences in the types of joins
that can be migrated automatically.

It is in this area of metadata that the differences between Discoverer and Oracle BIEE
metadata become apparent. The main difference is that the logical business model
layer needs to be based around one or more star schema models (this is a common
data model for data warehouse design). A variation on the star schema model is
known as a snowflake model (commonly represents the hierarchy levels of a
dimension as separate tables). In these cases, the migration assistant ‘collapses’ the
snowflake dimensions to their lowest level of dimension above the fact table.

The physical metadata layer does not need to be modeled around a star schema so this
layer is created using the join information from the Discoverer metadata.

Discoverer Target Property Target Property Target Property

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 26 of 36
Property In Presentation In Logical Layer In Physical Layer
Layer
Name n/a Logical join name Physical foreign key name
Auto generate n/a n/a n/a
name
Description n/a n/a n/a
Master n/a Cardinality = 1 The master table is the one
containing a primary key
Detail n/a Cardinality = N The detail table is the one
containing the foreign key
Formula n/a n/a Expression for the foreign
key relationship
Outer join on n/a Type Type.

Default Join Type It is always set


is InnerJoin automatically and cannot
be changed in the Oracle BI
OuterJoinOnDetail EE Admin
is mapped as
LeftOuterJoin

OuterJoinOnMaster
is mapped as
RightOuterJoin

Join details n/a n/a n/a


Join n/a Cardinality. Cardinality.
relationship
OneToOne join It is always set
relationships are automatically and cannot
migrated as 1:N be changed in the Oracle BI
join since 1:1 joins EE Admin
are not supported

DetailItemValuesAl
waysExistInMaster
is mapped as 1:N

DetailItemValuesM
ightNotExistInMast
er is mapped as
0,1:N

Identifier n/a n/a n/a

4.1.7.1 Multiple Join Paths


Discoverer folders having Multiple Join paths to another folder will be supported by
creating object aliases that are based on the same underlying physical object but have
the required alternative join paths.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 27 of 36
In the case of multiple joins to the same folder, the detail folder will be aliased:

CALENDAR DATE

J1 J2

SALES

Join Name Join Condition


J1 CALENDAR_DATE.DATE_COL = SALES.TRANSACTION_DATE
J2 CALENDAR_DATE.DATE_COL = SALES.ORDER_DATE

This alias folder SALES_A1 is created by DOMA to accommodate the join J2 to


CALENDAR_DATE:

CALENDAR DATE

J1 J2

SALES SALES_A1

Multiple paths exist to the same folder:

Join Name Join Condition


J1 EMPLOYEE.DEPT_NO = DEPT.DEPT_NO

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 28 of 36
J2 BONUS.EMP_ID = EMPLOYEE.EMP_ID
J3 BONUS. DEPT_NO = DEPT.DEPT_NO

The BONUS folder is aliased to accommodate the join J3 to DEPT.

4.1.7.2 Circular Joins


In this case, a circular join path exists between the folders:

Join Name Join Condition


J1 EMPLOYEE. DEPT_NO = DEPT.DEPT_NO
J2 DEPT.REGION_ID = REGION.REGION_ID
J3 REGION.REGION_HEAD = EMPLOYEE. EMP_ID

The REGION folder is aliased (REGION_A1) to accommodate the join J3 to


EMPLOYEE.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 29 of 36
4.1.7.3 Duplicate Joins
In the case where duplicate join definitions exist in the Discoverer metadata, only one
of the duplicate joins created in Discoverer will be considered for migration. Any
duplicate joins that have been detected will be noted in the migration log files.

4.1.7.4 Notes on Migrating Joins


This section describes how various joins are treated by the migration assistant due to
differences between Discoverer and the Oracle BI Server.

 The join between any two folders is skipped when they share more than one
common dimension, for example see below:

Table D1 Table F1 Table D2

Table F2 Table D3

This heuristic is applied to simplify the model..In the case above, table F1 and F2
are better treated as facts and D1, D2,D3 as dimensions in a classical star schema.
The join between F1 and F2 is redundant for most practical situations. In the
cases where it is determined to be important, it can be manually restored by
aliasing table F2.

 Folder A has a join to Folder B and vice-versa. In such a scenario one of the
joins will be skipped randomly. The skipped join is not available for further
inclusion
 Joins involving calculations in the join condition will not be migrated.
 Only one join path is available between the component folders of a complex
folder

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 30 of 36
 In the case of non-equi joins in Discoverer metadata, the resulting object in the
physical layer is a complex join
 Oracle BIEE does not support 1:1 joins

In the following cases, Oracle recommends checking the results of the migration
assistant:

 Joins based on columns where the column in the master and the detail tables
have different data type
 Calculations involving EUL_DATE_TRUNC function
 Admin mandatory conditions based on date columns

4.1.8 Conditions
Discoverer allows the creation of conditions in the metadata. Conditions can be both
mandatory and optional. Mandatory conditions are not visible to the end user and
have the effect of limiting the data that can be queried. Optional conditions can be
defined for end user convenience, i.e. the user (who may not be familiar with SQL
syntax) can optionally use pre-defined conditions, perhaps containing complicated
logic in their reports by dragging them into their report from a list of available
conditions.

4.1.8.1 Mandatory Conditions


The migration assistant translates mandatory conditions depending on whether it is a
simple, custom or complex folder. For simple and custom folders, mandatory
conditions are migrated as “Content Filters” in the where clause section of the Logical
Table Source. For complex folders, all users migrated from the Discoverer metadata
will be of the BI EE group ‘everyone’ so mandatory conditions on complex folders
will be applied to this user group as a security filter.

4.1.8.2 Optional Conditions


The optional conditions that can be defined in Discoverer metadata will not be
migrated to the Oracle BI EE metadata in this initial release of the migration assistant.
NOTE: It is expected that Optional conditions will be persisted as saved filters in the
Web Catalog when Workbook Migration is available.

4.1.9 Aggregate Calculated Items


Discoverer aggregate calculations (also known as ‘admin calcs’) are calculated items
that contain an aggregate function (e.g. SUM). They are represented by a different
icon to other items in a folder (see below):

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 31 of 36
The formula for the ‘margin percentage’ item highlighted above is:

SUM (Video Analysis Information.Profit)*100 /


SUM (Video Analysis Information.Sales)

These formulas will be migrated using a variation of the EVALUATE function


available in BI EE.

4.1.10 Item hierarchies


Discoverer item hierarchies provide end users with a drill path through related data. A
simple example is drilling through a geography hierarchy using data aggregated at a
country level through region and city. These item hierarchies are migrated to Oracle
BIEE dimensions. The levels in the Discoverer item hierarchy are migrated to the
associated dimension levels.

Discoverer has the ability to allow the creation of multiple hierarchy drill paths. This
migrates to entries in the preferred drill path property of the BI EE dimension level
property.

All hierarchies based on a folder will be migrated to a single Dimension created on


the folder. Item Hierarchies based on Complex Folders will not be migrated since a
Dimension in Oracle BIEE must be associated with a Dimension table. Hierarchies
spanning tables will be migrated by setting the Preferred Drill Path appropriately

Discoverer Target Property Target Property Target Property


Property In Presentation In Logical In Physical
Layer Layer Layer
Name n/a Dimension n/a
name
Auto generate n/a n/a n/a

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 32 of 36
name
Description n/a Dimension n/a
description

4.1.11 Discoverer Date Hierarchies


There is no equivalent in Oracle BI EE to Discoverer date hierarchy templates so
these will not be migrated. However, the resulting date hierarchies will be migrated.

4.1.12 Item Classes


There is no equivalent metadata object in Oracle BI EE so item classes are not
migrated. When creating filters in Oracle BI Answers lists of values (LOVs) are
generated at runtime.

4.1.13 Summary Folders


Discoverer summary folders are not migrated to Oracle BI EE.

4.2 Description of Catalog output from DOMA


This section describes what DOMA generates Answers Reports from the Workbooks.

4.2.1 Workbooks
A workbook contains worksheets displaying data retrieved from the database.
Workbooks typically contain data that is related in some way but organized to show
different perspectives. Worksheets contain the data that one wants to analyze, together
with a number of Discoverer components like parameters, totals, percentages,
exceptions, and calculations to help one analyze the data. Each worksheet in a
workbook contains the result of a query.

Workbooks that belong to a EUL are mapped to a sub folder under


shared\discoverer\<workbook> folder with all the worksheets being mapped to
requests under the <workbook> folder.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 33 of 36
5. How DOMA Translates RPD Metadata
5.1.1 Measures
Measures are identified by their placement and default aggregation settings in the
Discoverer metadata. Any attribute having placement value as data point and default
aggregation value that is neither ‘none’ nor ‘detail’ is defined as a measure. Any non-
measure is considered a dimension

5.1.2 Facts and Dimensions


A folder is a Fact folder when either it doesn’t join to any folder or is joined to some
folder(s) and is the Detail table in the relationship.

A folder is a Dimension folder when it is involved in a relationship with some


folder(s) where it is the Master table.

The leaf node for any dimension is always the level containing the folder key
columns.

The content of a logical table source for a folder is mapped to its linked dimension
levels.

5.1.3 Key Columns


Keys are created for tables in the Physical layer based on the columns involved in the
join. A primary key is based on the columns involved in the join in which the table
acts as a Master. A foreign key is based on the columns involved in the join in which
the table acts as a Detail.

Logical folder key is based on: -


o Dimension folder – columns referenced by another folder
o Degenerated Dimension – foreign key columns
o Standalone folder – all non–measure columns if they exist else all the
columns of the folder

5.1.4 Migrating Folders without Joins


The Oracle BIEE metadata requires that folders must be joined to another folder in the
logical layer. In cases where the Discoverer metadata contains a standalone folder, a
fact alias folder is created with just the measure columns from the standalone folder.
If no measure columns exist then a COUNT column based on one of its key columns
is created in the alias folder.

 A COUNT and COUNT_DISTINCT column is created in the logical folder


for those columns that form part of the primary key and foreign key
respectively.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 34 of 36
5.1.5 Creation of Alias Objects
A dimension alias is created for a fact folder when there exists a hierarchy based on it.

A fact alias is created for a dimension folder if it has measure attribute(s).

An aliased folder is propagated to the presentation layer only in case of a folder


having more than one join to the same folder [multiple join scenario].

The description of an aliased folder contains the usage information and the join for
which it was created. The original folder must be used for all those joins which don’t
have an aliased folder based on it.

5.1.6 Aggregates and Calculations


Aggregated columns are created for measure attributes based on the default
aggregation setting in the EUL.

Calculations involving columns from only one folder is created in its own folder
whereas those calculations that involve columns from multiple folders are created in
the complex folder.

All calculations are created using either the Evaluate or Evaluate_Aggr function in the
logical table source containing the column mappings.

5.1.7 User Privileges


The migration of roles and privileges is limited to user creation only. All users found
in the EUL export file will be migrated to the Oracle BIEE Group “Everyone” with a
password that is username in UPPERCASE.

Discoverer ‘Admin Mandatory’ conditions based on simple folders are migrated as


“where clause” for the logical table source corresponding to the simple folder.

Admin Mandatory conditions based on complex folders are migrated as security


filters set on the Group “Everyone”. This is set on the presentation folder
corresponding to the complex folder.

5.2 Evaluating the Output from DOMA


The goal of DOMA is to accelerate the migration of Discoverer metadata to Oracle
BIEE. This section describes scenarios where the results of DOMA will need to be
reviewed and validated as described below.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 35 of 36
5.2.1 Use of the EUL_DATE_TRUNC function
The date hierarchies that Discoverer can automatically generate make use of a built in
function called EUL_DATE_TRUNC. For example, the following calculation in
Discoverer returns a ‘Quarter’ for a date column e.g. ‘Transaction Date’. The valid
values are ‘Q1’, ‘Q2’, ‘Q3’, ‘Q4’ and the result is a ‘date’ data type:

EUL_DATE_TRUNC(Transaction Date,'"Q"Q')

The result of passing this calculation through DOMA is:

Evaluate( DECODE( %1, NULL,


TO_DATE('01011900','MMDDYYYY'), TRUNC( %1,
'Q')),TIMES.TRANSACTION_DATE)

Again, the resultant column is a ‘date’ data type. However, if this column is used in
another calculation:

DECODE(Times."Transaction Date: Quarter",'Q1','First


Quarter',’Q2’,’Second Quarter’,’Q3’,’Third
Quarter’,’Q4’,’Fourth Quarter’,’Unknown’)

The result of passing this calculation through DOMA is:

EVALUATE('DECODE(DECODE( %1, NULL,


TO_DATE(''01011900'',''MMDDYYYY''), TRUNC( %1,
''Q'')),Q1,''First Quarter'',Q2,''Second
Quarter'',Q3,''Third Quarter'',Q4,''Fourth
Quarter'',''Unknown'')' AS VARCHAR ( 50 ),
"Test".""."VIDEO5"."TIMES"."TRANSACTION_DATE")

that can result in a data type mismatch.

5.2.2 Joins Involving Different Data Types


In the case of a join that involves columns of different data type, e.g.

Folder A.Column 1 [number] = Folder B.Column 1 [varchar]

The migration assistant will not apply any data type Translations but will migrates the
join ‘as is’. The Translations need to be added as a post migration assistant step.

Migrating Oracle BI Discoverer metadata to Oracle BI Enterprise Edition

Page 36 of 36

Оценить