Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Copyright © 2006, Oracle. All rights reserved.
Overview | Common Schema | Discoverer Samples | Sample Workbooks | BI Beans | Spreadsheet Add-In |
These instructions guide you through the installation of the sample workbooks for OracleBI Discoverer. When you have completed the installation process, you can use OracleBI Discoverer to analyze data from both relational and multidimensional (OLAP) data sources.
The installation program installs sample workbooks and metadata used to access both OLAP and relational data.
The procedure performs the following tasks:
For relational access:
For OLAP data access:
<SAMPLE_HOME>
) on the computer where Oracle Business Intelligence middle tier is installed.
<
SAMPLE_HOME
>
<
SAMPLE_HOME
>\samples\discoverer
directory.
If you plan to user Discoverer only against relational datasources, verify that the following requirements have been met:
SQL> drop user bi_user cascade;
If you plan to user Discoverer against an OLAP datasource, verify that the following additional requirements have been met:
SQL> CREATE USER scott PROFILE default IDENTIFIED BY tiger DEFAULT TABLESPACE users ACCOUNT UNLOCK;
SQL> GRANT olap_user TO scott;
You can install the relational and OLAP Discoverer samples separately, if you so want. This installation must be performed on the computer where the Oracle Business Intelligence middle tier is installed.
set ORACLE_HOME=c:\oracleBI
<
SAMPLE_HOME
>\samples\discoverer
directory.
Installing the relational Discoverer workbooks
install_rel.bat
(on Unix you need to run install_rel.sh) file using the following parameters: SYSTEM
user. Note: The host and Oracle database parameters are for the instance that will contain the Discoverer Catalog and EUL. This must be the same host machine and database that contains the common schema sample data.
The following line provides a sample command for running the file:
c:\samples\discoverer> install_rel orcl system_pwd USERS TEMP c:\samples\discoverer
Installing the OLAP Discoverer workbooks
install_olap.bat
(on Unix you need to run install_olap.sh) file using the following parameters: SYSTEM
user. D4OSYS
user. This user is the owner of the Discoverer Catalog. If the Discoverer Catalog has not been installed, then the D4OSYS
user will be created with the password that you entered. Note: The host and Oracle database parameters are for the instance that will contain the Discoverer Catalog and EUL. This must be the same host machine and database that contains the common schema sample data.
The following line provides a sample command for running the file:
c:\samples\discoverer> install_olap bi.oracle.com 1521 orcl myhost_tns system_pwd d4osys_pwd c:\samples\discoverer
Installing both relational and OLAP Discoverer workbooks
install_all.bat
(on Unix you need to run install_all.sh) file using the following parameters: SYSTEM
user. D4OSYS
user. This user is the owner of the Discoverer Catalog. If the Discoverer Catalog has not been installed, then the D4OSYS
user will be created with the password that you entered. Note: The host and Oracle database parameters are for the instance that will contain the Discoverer Catalog and EUL. This must be the same host machine and database that contains the common schema sample data.
The following line provides a sample command for running the file:
c:\samples\discoverer>
install_all bi.oracle.com 1521 orcl myhost_tns system_pwd d4osys_pwd USERS TEMP c:\samples\discoverer
This page provides an overview of the sample workbooks.
It is often a requirement to scope the set of data values that users are permitted to analyze. For this OLAP sample, Scott and BI_USER are not allowed to see the forecasted data for future time periods (such as 2002). In order to set up this type of security, the Discoverer manager must define an environment similar to the one that is described here.
The data used for the sample workbook is stored in an Oracle OLAP analytic workspace named shaw
. In this workspace, a stored procedure named scope_data
was defined that scopes the time periods based on the current database user ID. The scope_data
stored procedure is defined as follows:
DEFINE SCOPE_DATA PROGRAM
PROGRAM
"Scopes data based on user id trap on error noprint aw attach SH_OLAP.SH_AW first
"***
"* shawt_time_isvisible specifies for each user the time periods that are visible.
"* The SCOTT user does not have access to 2002 forecast data
"***
limit shawusers to upcase(userid)
cns shawt_time
permit read when shawt_time_isvisible
error:
return
END
This stored procedure is called every time Discoverer Plus OLAP connects to Oracle OLAP. Discoverer Plus OLAP provides an application "hook" to allow Discoverer managers to run preprocessing tasks such as data scoping. This application hook is defined in the form of a PL/SQL procedure called d4o_autogo
in the D4OSYS schema. This procedure is called by Discoverer Plus OLAP and accepts the user ID as a parameter. In this case, the d4o_autogo
stored procedure attaches the sh_aw
analytic workspace and calls the scope_data
stored procedure. The d4o_autogo
procedure is defined as follows:
CREATE OR REPLACE PROCEDURE D4OSYS.D4O_AUTOGO (user_id
IN VARCHAR) is
BEGIN
dbms_aw.aw_attach('SH_OLAP', 'SH_AW');
dbms_aw.execute('scope_data');
END;
To uninstall the relational sample:
SQL> DROP USER bi_user CASCADE;
To uninstall the OLAP sample: