Scribd
Upload
26 views

06 - Testing and Validating Repository

Testing and validating a repository involves: 1. Checking the repository for errors using the consistency check option. 2. Testing queries using the Analysis Editor. 3. Examining the query log file to verify the SQL generated. This ensures the repository is functioning properly before continuing development.

Uploaded by

Navdeep Sharma
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
26 views

06 - Testing and Validating Repository

Testing and validating a repository involves: 1. Checking the repository for errors using the consistency check option. 2. Testing queries using the Analysis Editor. 3. Examining the query log file to verify the SQL generated. This ensures the repository is functioning properly before continuing development.

Uploaded by

Navdeep Sharma
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Testing and validating repository

Checking Repository for consistency:


Scenario:
You finished building the initial business model, and now you must test the repository before
continuing. You begin by checking the repository for errors by using the consistency check
option. You then test the repository by using the Analysis Editor to run queries. Finally, you
examine the query log file to verify the SQL generated by Oracle BI Server.

Outcome:
A tested and verified repository file

It is useful to check entire RPD, mainly it will check below points


1. All logical columns are mapped directly or indirectly to one or more physical
columns.
2. All logical dimension tables have a logical key.
3. All logical tables have a logical join relationship to another logical table.
4. There are at least two logical tables in the business model:
a logical fact table and a logical dimension table. Both can map to the same
physical table.
5. There are no circular logical join relationships.
6. A presentation catalog exists for the business model

Consistency Check Manager

1. Displays consistency check messages


a. Errors: Must be fixed to make the repository consistent
b. Warnings: Condition that may or may not be an error
• We must make sure there are no errors and if possible debug warnings.
Note: Till 11.1.1.5 version it used to display best practices in 11.1.1.6 it is
internally taken care

Process:
Do by using any one way
Servers in OBIEE 11G:

1. Oracle BI server:
1. It is a main server.
2. It controls all data security rules.
3. RPD will be loaded in this server .
2. Oracle BI presentation server:
1. It is used to develop reports, dashboards, key performance indicator (KPI),
score cards etc8
3. Oracle BI Java host:
1. It is used to display charts (graphs.)
4. Oracle BI scheduler:
1. It is used to schedule reports (Agents).
5. Oracle BI cluster controller:
1. It is useful to integrate ‘n’ number of servers.
6. Web logic:
1. It is web server useful to access reports and dashboards globally.

 Above 1 to 5 servers are integrate in OPMNCTL (oracle process management


network control).

Loading Repository:
In loading repository into oracle BI server we have below six steps.

1. Close RPD.
2. Start the web logic server alone or all OBI severs.
3. Configure RPD in EM (Enterprise manager).
4. Start or restart oracle BI server.
5. Confirm RPD loaded or not by checking log file.
6. Confirm RPD loaded or not by developing report.
Step 1: Close RPD

1. It is not mandatory in OBIEE 11g, where as in 10g it is mandatory.


2. In 10g RPD opened and if we load RPD in Oracle BI Server then we can not
open RPD in online mode with write permissions (it opens only read only mode)

Process:
Go to file menu of Administration tool  click on close.

Step 2: Start the web logic server Services alone or All OBI severs
Go to Start  All Programs  Oracle Business Intelligence  Click on Start BI Services

Step 3: Configure RPD in EM (Enterprise manager)

Open internet explorer type: http://localhost:7001/em


Provide user name: web logic
Pass word: Oracle123.
1. Click on login.
2. Click on business intelligence  core application Deployment repository
click on lock and edit configuration close click on repository file
browseSelect
ORA_RPD.rpd open Repository password: Oracle123Confirm
password: Oracle123Click on apply.
3. Click on activate changes

Step 4: Start or Restart oracle BI server

Method: Using EM
1. Click on capacity management  availability
2. Select BI servers Click on restart selected  yes  after sometime close.

Step 5 :Confirm RPD loaded or not by checking log file

1. Go to below path
BI11g\instances\instance1\diagnostics\logs\OracleBIServerComponent\cor
eapplication_obis1
2. Open Nq server.log file observe our rpd name in the bottom of the notepad

Step 6: Confirm RPD loaded or not by developing a report

1. Open Intrenet Explorer


2. Type URL http://localhost:7001/analytics press enter
User id: web logic.
Password: Oracle123.
3. Click on new analysis  select subject area supplier sales
4. From subject area pane double click on year, dollars columns
5. Click on results.
Note1:

1. Whenever we click in activate changes in backend RPD Xerox copy will be


created in repository folder. this process is called as version control of RPD
2. In Nqsconfig.ini file RPD name will be modified.
3. we can find Nqsconfig.ini file in below path

E: /bi11g/instances/instance1/config/oracle BI server component/core


application_obis1.

Log Level:
1. Oracle BI Server provides a facility for logging query activity at the individual user
level
2. Log levels are available from 0 to 7.
3. In production we use ‘0’ i.e., No log level .This process is useful to improve the
performance of environment by reducing log creation work of oracle BI server.
4. In development and testing environments we use log level ‘2’.
5. The query log file is named Nq query.log and is located in the directory
Bi11g/instances/instance1/diagnostics/logs/oracle-bi servercomponent/
coreapplication-obis1.
Modifying rpd in online mode:

1. Check out.
2. Modify metadata.
3. Check in.
4. Save rpd.
5. Use copy as option to override original rpd (Optional)
6. Reload server metadata.

You might also like