Step 1 : Create the following sql scripts: Oracle_create_nQ_CalendarCreate table scripts Oracle_create_nQ_ClockCreate Table Scripts Oracle_nQ_CalendarInsert Scripts Oracle_nQ_ClockInsert

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;

BIPLATFORM repository created by the RCU you will see that the S_NQ tables already have been created for you:

What is missing are the S_ETL tables. We can get the scripts from Middleware/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/sampl e/usagetracking/SQL_Server_Time

Note : Dont 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/sampl e/usagetracking/ As mentioned it is a bug so you can get the RPD and Catalog from the above mentioned links. Step 3 : Upload the RPD and Catalog in the Enterprise Manager (EM) to make it online. Step 4 : Open the RPD in online mode and change the Usage Tracking Writer Connection Pool settings to your database credentials.

Update the row count and check whether data was populating or not. Step 5: OBIEE 11g Usage Tracking Server Configuration: To configure the server configuration parameters, we can do it manually or using enterprise manager. To do manually perform the following steps: a) Open Middleware\instances\instance1\config\OracleBIServerComponent\ coreapplication_obis1\NQSConfig.ini in Notepad and edit. b) Next, set the usage tracking options. Scroll to the Usage Tracking section. Set Enable = Yes; to enable usage tracking.

c) In the section that lists parameters used for inserting data into a table, set the PHYSICAL_TABLE_NAME = OBI Usage Tracking.Catalog.dbo.S_NQ_ACCT ;

d) The table name is the fully qualified name as it appears in the Physical layer of the Server Administration Tool. The general structure of this parameter depends on the type of database being used. For Oracle, the structure is PHYSICAL_TABLE_NAME = <Database>.<Schema>.<Table>.]

e) Set the CONNECTION_POOL parameter to specify the connection pool to use for inserting records into the usage tracking table. The setting is CONNECTION_POOL = OBI Usage Tracking.Usage Tracking Writer Connection Pool. Leave the default settings for BUFFER_SIZE, BUFFER_TIME_LIMIT_SECONDS, NUM_INSERT_THREADS, and MAX_INSERTS_PER_TRANSACTION. Your configuration file should look like this:

The connection pool name is the fully qualified name as it appears in the Physical layer of the repository. f)Save and close the NQSConfig.ini configuration file. Step 6 : Login to analytics http://<hostname>: <port >/analytics/ by using Administrators credentials. Check the Usage Tracking dashboards .