1. What is repository?

Repository stores the metadata information used by the BI server.

2. What are the different modes of repository?

Offline Mode
 Oracle BI is not started
 Repository does not load into Oracle BI server Memory
 Used for development.
Online Mode:
 Oracle BI is started.
 Repository loads into memory.
 Users can submit query requests.
3. Where can I define default repository path?
In C:\OracleBI\server\Config\NQSConfig file
Under [ REPOSITORY ]
Star = SH.rpd, DEFAULT;
NQSConfig.ini is the initialization file read by the Business Intelligence Server when it starts up. It
contains a number of parameters that control server settings and behavior. Right now, you are
concerned with the section that tells the server which metadata repository to read.
4. What is tnsnames.ora path?
C:\app\chrome\product\11.1.0\db_1\network\admin\ tnsnames.ora
5. What is a connection pool describe its attributes?
 Connection Pool is a connection to a Physical data source. Multiple connection pools can
be created to the same source to improve end-user query performance.
 Connection pool contains information about the connection to the database but not the
database itself.
 Defines how BI server connects to the database source
 Specifies the ODBC or native data source name.
 Allows multiple users to share a pool of data source connections.
6. What is difference between complex and foreign key join? Why and where are they used.
Logical layer supports both foreign key and complex joins
Foreign key joins not recommended
Restrict choices that BI server can make over join paths
Only there for backward compatibility
Complex joins are preferred
Indicates relationship between tables
Allows BI Server to determine best join path
Useful when more than one Logical Table Source
The complex join in the BM is what you should use 100% of the time for all
joins. "Complex Join" is a terrible name in the BM, a better on is
'Intelligent Join'. And that's just what it is - it will dynamically select
 which Logical table sources to join together from the Logical tables. For
example, it may elect to join the Monthly Fact aggregate with the monthly
time aggregate instead of the daily/details LTSs. It does not determine how
those LTSs are actually joined - that is done in the Physical Layer. A
complex join there is more aptly named - it is any join that is not
considered a simple Foreign Key join.
If you use a FK business model join, you are forcing which fields OBI can
use and therefore which LTSs it can use. The joining is not physical table
to physical table, but really LTS to LTS. Whatever phys joins are
underneath it will use (as long as they are there). But the concept is
LTS-to-LTS, not the individual tables inside. Kind of like joining 2 views
together

In short, just use the Complex joins always.

Jeff M.

Complex is best when you have

a > or a CAST() type of thing in the join.

7. What is BMM? Why is it used? What are its elements?

It’s a logical Star-Schema representation of the Physical objects.

The Business Model and Mapping layer of the Administration Tool defines the business, or
logical, model of the data and specifies the mappings between the business model and the
Physical layer schemas.
This is where the physical schemas are simplified to form the basis for the users’ view of the
data.
BMM can contain one or more business model objects.
A business model object contains the business model definitions and the mappings from logical
to physical tables for the business model.

8. What is hierarchies and its attributes?

Hierarchies allow Oracle BI Server to calculate useful measures and allowing users to drill down
to more detail.
9. What is presentation layer? How is it used? What is subject area?
Presentation layer contains presentation objects. It provides customized view of business model
to the user.
Simplifies and organizes the business model to make it easy for user to understand and query.
Exposes only data meaningful to the users.
10. What are initialization blocks? What are different types?
Initialization blocks are used to initialize dynamic repository variables, system session variables,
and nonsystem session variables.
11. What are repository variable.
 Repository variables streamlines the administrative tasks and modifies the meta data content
dynamically to adjust to the changing environment
A repository variable has a single value at any point in time.

Presentation layer as the name susggests is the layer which is presented to the user containing
subject areas and business nomenclature
12. What is a repository file.
Files ending in .rpd are metadata files, also known as repositories. The metadata contains the
information that the server uses to translate from a logical query (using business terms) to one
or more physical queries needed to retrieve the correct information to satisfy the request.

13. Connection pool properties:

1. What is repository?

Repository stores the metadata information used by the BI server.

2. What are the different modes of repository?

Offline Mode
 Oracle BI is not started
 Repository does not load into Oracle BI server Memory
 Used for development.
Online Mode:
 Oracle BI is started.
 Repository loads into memory.
 Users can submit query requests.
3. Where can I define default repository path?
In C:\OracleBI\server\Config\NQSConfig file
Under [ REPOSITORY ]
Star = SH.rpd, DEFAULT;
4. What is tnsnames.ora path?
C:\app\chrome\product\11.1.0\db_1\network\admin\ tnsnames.ora
5. What is a connection pool describe its attributes?
 Connection Pool is a connection to a Physical data source. Multiple connection po
be created to the same source to improve end-user query performance.
 Connection pool contains information about the connection to the database but
database itself.
 Defines how BI server connects to the database source
 Specifies the ODBC or native data source name.
 Allows multiple users to share a pool of data source connections.
6. What is difference between complex and foreign key join? Why and where are they used
Logical layer supports both foreign key and complex joins
Foreign key joins not recommended
Restrict choices that BI server can make over join paths
Only there for backward compatibility
Complex joins are preferred
Indicates relationship between tables
Allows BI Server to determine best join path
Useful when more than one Logical Table Source
The complex join in the BM is what you should use 100% of the time for all
joins. "Complex Join" is a terrible name in the BM, a better on is