Usage Tracking is used to monitor
system and ad-hoc query performance and to provide input on usage trends for
use in billing users and departments for resources. Usage tracking is
particularly useful in determining user queries that are creating performance
bottlenecks, based on query frequency and response time. When usage tracking is
enabled, the Oracle BI Server collects usage tracking data for each query and
writes statistics to a usage tracking log file or inserts them directly to a
database table. For the purposes of this tutorial, you will use a database
table, which is the recommended leading practice.
Here we will separate Usage Tracking
Process to 4 Steps
I. Creating Usage Tracking Table
II. Creating and customizing rpd file
III. Changing the Configuration in EM
IV. Testing the Usage Tacking in Answers
Before implementing
Usage Tracking we need to run the following scripts.
Step 1 :
Create the following sql scripts:
- Oracle_create_nQ_Calendar—Create
table scripts
- Oracle_create_nQ_Clock—Create
Table Scripts
- Oracle_nQ_Calendar—Insert
Scripts
- Oracle_nQ_Clock—Insert
Scripts
- Also
create S_NQ_ACCT table
- We
need to even create NQ_LOGIN_GROUP view also using the following syntax:
CREATE OR REPLACE VIEW nq_login_group AS SELECT DISTINCT user_name
AS login, user_name AS resp FROM s_nq_acct;
Grant select on nq_login_group to public;
We
can get the scripts from Middleware/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/sample/usagetracking/SQL_Server_Time
Note : Don’t forget
to commit the changes after creating the tables and inserting the data.
Step 2 : We can get the upgraded Usage Tracking RPD and Catalog from the
below path after installing OBIEE 11g.
Middleware/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/sample/usagetracking/
As mentioned it is
a bug so you can get the RPD and Catalog from the above mentioned links.
No comments:
Post a Comment