OBIEE 11g training.

Repository development-
Step 1: Create new repository
i) Oracle BI Admin tool > File > New Repository
ii) In Create Input Name of the repo



iii) Location of the repository
D:\Oracle\Middleware\instances\instance1\bifoundation\OracleBIServerComponent\c
oreapplication_obis1\repository

iv) Repository password should be of minimum 8 letter strength. With combination of letters
and numerical digits.
v) Along with the new RPD, a log file will also be created which will store all information about
the repository.
vi) Now Select data source.
vii) There are many inbuilt native connections in OBIEE: for Essbase, for Hyperion, OCI 10g/11g,
SAP etc. When you are connecting to these data sources, use inbuilt native connections.
When you want to connect to the data sources where there is no inbuilt connector present,
use ODBC connectivity. For example for SQL server, there is no inbuilt connector. In such
cases use ODBC.

viii) Physical Layer development:
a) Connection development b) Importing Metadata, c) Creating physical layer joins

ix) Constraints: Not Null constraint, Unique Constraint, PrimaryKey( Satisfies unique and not
null constrainst) , Foriegn Key (reference of primary key is called foriegn key)


x) DB Joins : Equi Join(innerjoin) only accepts '=' operator
Non Equi join
Outer Join
Self Join
Cross Join

xi) OBIEE only has two Join:
Foriegn Key Join
Complex join

OB Foriegn Join is equal to DB Equi Join
OB Complex join is equal to DB non equi join

Cardinalities: One to many, Many-Many and one-one

Whenever we are joining two tables, always start from 'Many side' to 'One Side'. ie If you
are joining Dept and Emp table (1:N) start the join from Employee and drag it to Dept.

Illustrative: Hit New Join and then drag the join from Emp to Dept






This window will appear then:




If the join is not recognized, it can be changed manually.









Condition for Complex join:

Consider the tables EMP and Salgrade:

EMP
Emp No Name Sal
100 Suresh 1000
101 Mahesh 2000

Grade LowSal HighSal
A 900 1800
B 1900 2500

There are no matching columns in two tables. But if we look carefully, Sal and lowSal and
HighSal do have certain relationship which can be utlized to create a join.
To join these table put this expression:

Sal >=lowsal and sale<= high sal




Now double click on the join and you will see that the join has been automatically changed
to complex join :



Keys
I. To make the execution level fast, each table should have a key column even though its not present
in DB.
II. To make a primary key , double click on the table, go to the key tab, name the key and provide the
corresponding column alongwith optional description.





If you create a key in OBIEE, OB doenst push it back to DB and keeps it at the OB level only.
Also there are no foriegn keys, only Primary keys in OB. To understand which column to
make primary key, view the data and try to figure out which column is unique.


Appendix:

I. ODBC: Open data base connectivity
II. OCI: Oracle Call interface
III. For importing metadata, either right click on connection pool or go to file > import
metadata