ODI 11g and Java location

Oracle Data Integrator 11g requies Java to run and install. This is required when performing the installation from setup.exe of location ofm_odi_generic_11.\Disk1. Depending on your system, the Install may show the following error:

Error: Provide the JDK/JRE location while launching the installer. Invoke the setup.exe with –jreLoc

with below Error Message:


The JDK location needs to be specified while running the setup.exe from a MS-Dos (CMD) Window. However, the path may not contain any spaces! If Java has been installed in the default location like C:\Program Files\Java\ , then the path must be expressed like C:\Progra~1\java\ while invoking the setup.exe:

C:\Users\****\Downloads\ofm_odi_generic_11.\Disk1>setup.exe -jreLoc C:\Progra~1\java\jdk1.8.0_171


This will then allow the installer to run properly.



Downloading a rpd from OAC Thin Client Modeller

The web modeller or Thin Client Modeller was introduced with BICS and OAC respectively, to allow a more agile metadata modelling. The thin Client modeller does not provide the same level of modelling functionality compared to the “classic” .rpd metadata model. Additionally, with the current release of OAC only one modelling approach is supported. Thus, only the thin client model or the classical model can be deployed as metadata at a time.

Hence, the might be a scenario for switching from the thin client modeller (web modeller) to the classic .rpd model to support more complex metadata modelling.

A .rpd file can be generated from OAC when downloading a Snapshot and extracting the .bar file. The .bar file can be downloaded from the Snapshots area of the OAC Console:


When clicking on a option menu right to the Snapshots, the Console allows  to download the snapshot as .bar file. Once the .bar file is downloaded (after assining a password to protect the downloaded file), the file can be opened with a Archive Tool such as 7z.


The .rpd data model can be opened like any other classical metadata model using the BI Administration Tool. This will contain system generated Objects and Names:


Referencing Oracle BI System Session variables

Oracle BI (OBIEE) provides multiple categories of Variables, such as:

  • Session
  • Repository
  • Presentation
  • Global

These different categories of variables need to be referenced using a specific syntax. However, the required syntax depends on the category of variable and the context. Below are examples for referencing Session variables in Analysis/Reports and within the narrative View. This is often useful for debugging scenarios or for performing unit test when creating complex formulas.

To reference a Session Variable within a Report use: VALUEOF(NQ_SESSION.GROUP) like below:


To reference a Session Variable within a Narrative View use: @{biServer.variables[‘NQ_SESSION.GROUP’]} like below:


The complete code to reference the different Session variables (User, Group, Roles) is as follows:

[b]Derzeitiger User:[/b] @{biServer.variables['NQ_SESSION.USER']} [br/][br/]
[b]Derzeitiger Anzeigename:[/b] @{biServer.variables['NQ_SESSION.DISPLAYNAME']} [br/][br/]
[b]Derzeitiger Gruppen:[/b] @{biServer.variables['NQ_SESSION.GROUP']} [br/][br/]
[b]Derzeitiger Rollen:[/b] @{biServer.variables['NQ_SESSION.ROLES']} [br/]

For a exessive list of available Session variables check:

For general Overview check:

For short reference card check:

For Official Documentation check (11g):

Protecting Filters

The Protecting Filters Option in Oracle BI or Oracle Analytics Cloud is usually not used or needed. However, it may be required when using multiple Filters on the same Column (Subject area Field) and using Action Links as Drill-down navigation or in conjunction with Dashboard Prompts.


The following is an example scenario without protecting the Filters: On the Detailed Report, the following Operators are defined:


When making the Drill-down from the Top Report using the Action-link Drill-down navigation:


The Filter Operators are overwritten by the internal Background process for navigating to the Detail Report (compare Operator which is “is equal to / is in” which should have been “is less than or equal to” from Report definition):


After selecting “Protect Filter” the Operator is protected from the Background navigation process and the intended Operator is used on the Detailed Report:


This feature is also described in the following article:

OAC: specifying the Connection string within rpd model

The following is a step-by-step guide to determine the Connection string for Oracle Analytics Cloud and Oracle Database Cloud.

When logging into your Oracle Cloud Service using your identity Domain, a similar page is being displayed:


Click on the Action Menu of the Database Cloud Service and select “Open Service Console”.

This Page shows details about your Cloud Services such as OCPUs, Storage or Memory:


click on the Database Service Name to get to the Details Page:


This reveals the Public IP of the Oracle Cloud Database and the required Service Name.

Within the Oracle BI Administration Tool, the connection string needs to be created in the Data Source Name Field:


Using the following format:







After modelling the data and saving the .rpd File, the Model can be uploaded to the OAC Cloud: