Setting up Usage Tracking in OBIee in 2 steps

Disclosure: When you purchase a service or a product through our links, we sometimes earn a commission

Setting up usage tracking can be tricky now in 11g because it is a feature that exists for a long time now. Actually, it existed in the previous versions and has (almost) not changed over time whereas OBIee architecture changed significantly.


Step 1 :  Create required tables in database, following the scripts hosted in
{obiee_home}\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1\sample\usagetracking

Step 2 : Add the content of the rpd “UsageTracking.rpd” (found in the same directory) in your rpd :
– either using drag and drop method
– or using File->Merge utility

If you get an error message (about upgrading your repository), it means that your UsageTracking.rpd comes from the 10g version, and

Solution 1 :  it needs to be upgraded to 11g via the following commands :

set ORACLE_INSTANCE={obiee_home}\instances\instance1
cd {obiee_path}\Oracle_BI1\bifoundation\server\bin
obieerpdmigrateutil.exe -I {obiee_home}\bifoundation\OracleBIServerComponent\coreapplication_obis1\sample\usagetracking\UsageTracking.rpd -O {obiee_path}\bifoundation\OracleBIServerComponent\coreapplication_obis1\sample\usagetracking\UsageTracking11g.rpd -L {obiee_path}\bifoundation\OracleBIServerComponent\coreapplication_obis1\sample\usagetracking\ldif -U Administrator

You will be asked for a password : in 10g the rpd didn’t have passwords : you’ll have to choose one.

Solution 2 :  you can try to get the latest version of the rpd on the oracle support website

———————————————————————————————-

Notes : 

  • prefer re-creating reports and dashboards for usage tracking rather than using existing ones.
  • the “group” table may not work in 11g




Troubleshooting :
1) In the RPD : right clic -> view data  on usage tracking tables in the physical layer in order to see if tables are correctly created, seeded and mapped.
2) In Enterprise Manager : view logs for errors
3) In NQSConfig.INI file : check connection pool and database path