RSS

Tag Archives: session logs

OBIEE 11.1.1.6.0 is available now

The Oracle Business Intelligence Enterprise Edition (OBIEE) 11.1.1.6.0 has been made generally available.

The software is available for download from OTN.

@ http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/downloads/bus-intelligence-11g-165436.html

The related documentation is published and available from Oracle Business Intelligence Enterprise Edition Documentation library.
With this release of OBIEE 11.1.1.6.0, the entire Business Intelligence Foundation Suite has been made generally available, opening the door for “Oracle Exalytics Super-fast, Super-ready”.

For more information on exalytics: http://www.oracle.com/exalytics

Oracle Exalytics installation,configuration and deployment info: http://docs.oracle.com/cd/E23943_01/bi.1111/e24706/toc.htm

Happy Reporting….

 

Thanks,

Shiva

 
Leave a comment

Posted by on March 3, 2012 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , ,

RCU Schema Configuration failed with the error “The specified prefix already exists”

We all know that we need to create RCU schemas before starting OBIEE 11G (In fact, for any Fusion Middleware application) Installation. Because it is the base store for FMW.

Recently I came across a scenario where my customer created RCU schemas with Oracle Repository Creation Utility (RCU) version 11.1.1.3.0 and Installed OBIEE 11.1.1.3.0. Now after new OBIEE 11.1.1.5.0 release he wants to upgrade his application from 11.1.1.3.0. But he is not interested at the In-place upgrade. So we uninstalled weblogic and OBIEE 11.1.1.3.0 and started RCU 11.1.1.3.0 to drop the _BIPLATFORM and _MDS schemas.

The RCU shown up with successful message and so we thought everything is cleaned up and it’s good to create schemas again. I started RCU 11.1.1.5.0 and selected Oracle Business Intelligence component and given prefix as DEV. But am not able to assign this prefix and got a message like “The specified prefix already exists”.  Though I got successful dropped schemas message, just for cross check I looked at database for the DEV_BIPLATFORM and DEV_MDS schemas. There I am not seeing any of them.

Then I checked at dropped schemas log generated by RCU and realized that there is an entry in System.SCHEMA_VERSION_REGISTRY$ table which is stopping me to assign the same DEV prefix which we used for earlier version schemas.

Actually the RCU should drop schemas using mdsschemamanager.pl script. This script has capability to do cascade delete and will delete entries in System.SCHEMA_VERSION_REGISTRY$ table.

To make sure this log into RCU DATABASE as sys and run the following SQL Query:

Select * from System.SCHEMA_VERSION_REGISTRY$;

If this query returns any record then it means the RCU didn’t drop the schemas properly.

Actually what happened in this case is the RCU schemas were not dropped using mdsschemamanager.pl script, it’s just dropped with normal schema delete and the resulting repository record for the schema is not clean. Keep in mind, this is just in case if you want to use same prefix. Otherwise RCU will let you proceed to create new prefixed Schemas.

If the RCU schemas have been deleted incorrectly using the RCU drop user command, then We need to clean these entries before starting new repository schemas creation.

To do this, run the following SQL*Plus command as sys to complete the removal of the RCU schemas records in the repository database:

delete from System.SCHEMA_VERSION_REGISTRY$;

Once you confirmed there are no entries in System.SCHEMA_VERSION_REGISTRY$  table and start the RCU to create repository schemas with the prefix (DEV in my case). The RCU will go smooth and wont complain with any error.

Hope this helps you in your RCU issues troubleshooting.

 

Thanks,

Shiva

 
7 Comments

Posted by on November 16, 2011 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , , , , , , , ,

How to Visualize your Audit Data with BI Publisher? – Setup BI Publisher Usage Tracking

In my other blog post (https://shivabizint.wordpress.com/2011/06/19/bi-publisher-usage-tracking-in-obiee-11g/) I have posted a nice video on BI Publisher Usage tracking. After this I have been asked by many of our friends to know how this can be get in action. while I am preparing to write the steps for this, I have found a great article by Kan Nishida from  blogs.oracle.com on same job.For the benifit of readers am sharing the same steps illustrated by him.

With Fusion Middleware Audit Framework you have an option to store the auditing data into a database instead of a log file, which is the default option. Once you enable the database storage option, that means you have your auditing data (or, user report access data) in your database tables, now no brainer, you can start visualize the data, create reports, analyze, and share with BI Publisher.

So, first, let’s take a look on how to enable the database storage option for the auditing data.

How to Feed the Auditing Data into Database

First you need to create a database schema for Fusion Middleware Audit Framework with RCU (Repository Creation Utility). If you have already installed BI Publisher 11G you should be familiar with this RCU. It creates any database schema necessary to run any Fusion Middleware products including BI stuff. And you can use the same RCU that you used for your BI or BI Publisher installation to create this Audit schema.

Create Audit Schema with RCU

Here are the steps:

  1. Go to $RCU_HOME/bin and execute the ‘rcu’ command
  2. Choose Create at the starting screen and click Next.
  3. Enter your database details and click Next.
  4. Choose the option to create a new prefix, for example ‘BIP’, ‘KAN’, etc.
  5. Select ‘Audit Services’ from the list of schemas. image
  6. Click Next and accept the tablespace creation.
  7. Click Finish to start the process.

After this, there should be following three Audit related schema created in your database.

  • <prefix>_IAU (e.g. KAN_IAU)
  • <prefix>_IAU_APPEND (e.g. KAN_IAU_APPEND)
  • <prefix>_IAU_VIEWER (e.g. KAN_IAU_VIEWER)

Setup Datasource at WebLogic

After you create a database schema for your auditing data, now you need to create a JDBC connection on your WebLogic Server so the Audit Framework can access to the database schema that was created with the RCU with the previous step.

image

  • Click ‘Lock & Edit’ so that you can make changes

image

  • Click New –> ‘Generic Datasource’ to create a new data source.
  • Enter the following details for the new data source:
    Name: Enter a name such as Audit Data Source-0.
    JNDI Name: jdbc/AuditDB
    Database Type: Oracle

image

  • Click Next and select ‘Oracle’s Driver (Thin XA) Versions: 9.0.1 or later’ as Database Driver (if you’re using Oracle database), and click Next.
  • The Connection Properties page appears. Enter the following information:
    Database Name: Enter the name of the database (SID) to which you will connect.
    Host Name: Enter the hostname of the database.
    Port: Enter the database port.
    Database User Name: This is the name of the audit schema that you created in
    RCU. The suffix is always IAU for the audit schema. For example, if you gave
    the prefix as ‘BIP’, then the schema name would be ‘KAN_IAU’.
    Password: This is the password for the audit schema that you created in RCU.

image

  • Click Next.
  • Accept the defaults, and click Test Configuration to verify the connection.
  • Click Next
  • Check listed servers where you want to make this JDBC connection available.

image

  • Click ‘Finish’ !

After that, make sure you click ‘Activate Changes’ at the left hand side top to take the new JDBC connection in effect.

image

Register your Audit Data Storing Database to your Domain

Finally, you can register the JNDI/JDBC datasource as your Auditing data storage with Fusion Middleware Control (EM). Here are the steps:

1. Login to Fusion Middleware Control

2. Navigate to Weblogic Domain, right click on ‘bifoundation…..’, select Security, then Audit Store.

image

3. Click the searchlight icon next to the Datasource JNDI Name field.

4.Select the Audit JNDI/JDBC datasource you created in the previous step in the pop-up window and click OK.

image

5. Click Apply to continue.

6. Restart the whole WebLogic Servers in the domain.

After this, now the BI Publisher should start feeding all the auditing data into the database table called ‘IAU_BASE’. Try login to BI Publisher and open a couple of reports, you should see the activity audited in the ‘IAU_BASE’ table. If not working, you might want to check the log file, which is located at $BI_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/logs/AdminServer-diagnostic.log

to see if there is any error.

Once you have the data in the database table, now, it’s time to visualize with BI Publisher reports!

Create a First BI Publisher Auditing Report

Register Auditing Datasource as JNDI datasource

First thing you need to do is to register the audit datasource (JNDI/JDBC connection) you created in the previous step as JNDI data source at BI Publisher. It is a JDBC connection registered as JNDI, that means you don’t need to create a new JDBC connection by typing the connection URL, username/password, etc. You can just register it using the JNDI name. (e.g. jdbc/AuditDB)

  1. Login to BI Publisher as Administrator (e.g. weblogic)
  2. Go to Administration Page
  3. Click ‘JNDI Connection’ under Data Sources and Click ‘New’image
  4. Type Data Source Name and JNDI Name. The JNDI Name is the one you created in the WebLogic Console as the auditing datasource. (e.g. jdbc/AuditDB)
  5. Click ‘Test Connection’ to make sure the datasource connection works.
  6. Provide appropriate roles so that the report developers or viewers can share this data source to view reports.
  7. Click ‘Apply’ to save.

Create Data Model

image

  1. Select Data Model from the tool bar menu ‘New’
  2. Set ‘Default Data Source’ to the audit JNDI data source you have created in the previous step.
  3. Select ‘SQL Query’ for your data set
  4. Use Query Builder to build a query or just type a sql query. Either way, the table you want to report against is ‘IAU_BASE’. This IAU_BASE table contains all the auditing data for other products running on the WebLogic Server such as JPS, OID, etc. So, if you care only specific to BI Publisher then you want to filter by using  ‘IAU_COMPONENTTYPE’ column which contains the product name (e.g. ’xmlpserver’ for BI Publisher).

Here is my sample sql query.

select     “IAU_BASE”.”IAU_COMPONENTTYPE” as “IAU_COMPONENTTYPE”,
“IAU_BASE”.”IAU_EVENTTYPE” as “IAU_EVENTTYPE”,
“IAU_BASE”.”IAU_EVENTCATEGORY” as “IAU_EVENTCATEGORY”,
“IAU_BASE”.”IAU_TSTZORIGINATING” as “IAU_TSTZORIGINATING”,
to_char(“IAU_TSTZORIGINATING”, ‘YYYY-MM-DD’) IAU_DATE,
to_char(“IAU_TSTZORIGINATING”, ‘DAY’) as IAU_DAY,
to_char(“IAU_TSTZORIGINATING”, ‘HH24’) as IAU_HH24,
to_char(“IAU_TSTZORIGINATING”, ‘WW’) as IAU_WEEK_OF_YEAR,
“IAU_BASE”.”IAU_INITIATOR” as “IAU_INITIATOR”,
“IAU_BASE”.”IAU_RESOURCE” as “IAU_RESOURCE”,
“IAU_BASE”.”IAU_TARGET” as “IAU_TARGET”,
“IAU_BASE”.”IAU_MESSAGETEXT” as “IAU_MESSAGETEXT”,
“IAU_BASE”.”IAU_FAILURECODE” as “IAU_FAILURECODE”,
“IAU_BASE”.”IAU_REMOTEIP” as “IAU_REMOTEIP”
from    “KAN3_IAU”.”IAU_BASE” “IAU_BASE”
where “IAU_BASE”.”IAU_COMPONENTTYPE” = ‘xmlpserver’

Once you saved a sample XML for this data model, now you can create a report with this data model.

Create Report

image

Now you can use one of the BI Publisher’s layout options to design the report layout and visualize the auditing data. I’m a big fan of Online Layout Editor, it’s just so easy and simple to create reports, and on top of that, all the reports created with Online Layout Editor has the Interactive View with automatic data linking and filtering feature without any setting or coding. If you haven’t checked the Interactive View or Online Layout Editor you might want to check these previous blog posts. (Interactive Reporting with BI Publisher 11GInteractive Master Detail Report Just A Few Clicks Away!) But of course, you can use other layout design option such as RTF template.

Here are some sample screenshots of my report design with Online Layout Editor.

image

image

Visualize and Gain More Insights about your Customers (Users) !

image

Now you can visualize your auditing data to have better understanding and gain more insights about your reporting environment you manage. It’s been actually helping me personally to answer the  questios like below.

  • How many reports are accessed or opened yesterday, today, last week ?
  • Who is accessing which report at what time ?
  • What are the time windows when the most of the reports access happening ?
  • What are the most viewed reports ?
  • Who are the active users ?
  • What are the # of reports access or user access trend for the last month, last 6 months, last 12 months, etc ?

I was talking with one of the best concierge in the world at this hotel the other day, and he was telling me that the best concierge knows about their customers inside-out therefore they can provide a very private service that is customized to each customer to meet each customer’s specific needs. Well, this is true when it comes to how to administrate and manage your reporting environment, right ? The best way to serve your customers (report users, including both viewers and developers) is to understand how they use, what they use, when they use. Auditing is not just about compliance, but it’s the way to improve the customer service. The BI Publisher 11G Auditing feature enables just that to help you understand your customers better.

Happy customer service, be the best reporting concierge!.

(Original post: http://blogs.oracle.com/xmlpublisher/entry/how_to_visualize_your_audit_da)

 

Thanks,

Shiva

 
6 Comments

Posted by on November 16, 2011 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , ,

Predefined Presentation Variables in OBIEE 11G

The OBIEE has couple of predefined presentation variables which we can reference in analyses, dashboards, KPIs, and agents. we can take advantage of these varaibles and can be used in analysis for better presentation.

The below table contains a list of the predefined presentation variables. For time zone variables, the time zone for a user must be set to a value other than Default in order for this variable to work. (Users set their preferred time zone in the “My Account dialog: Preferences tab”.)

Note that the syntax for these predefined presentation variables omits the variables qualifier. 
for example, @{session.locale} rather than @{session.variables.locale}.


Hope this post helps you in your report developments.


Thanks,
Shiva
 
Leave a comment

Posted by on October 23, 2011 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , , ,

what is the DXE Execution in OBIEE 11G Session log?

In OBIEE 11G if we look at Session logs, we will see a new status called ‘DXE Execution’ with amount of time its been executed. I did some research on this to answer my burning questions ‘ What this new alien will do? and How it is helpful for Performance tuning?.

Then I founded interesting news about this and actually the DXE Execution means “Data Transformation Engine which handles post-processing of the BIServer results within OBIPS”.

The post-processing can involve resorting, filtering, aggregating, and/or indexing the original BIServer result set so that the data can be consumed by a view’s renderer. And It can be automatically kicked off when the BIServer query finishes.

So if the DXE Execution is running long time, Then it’s time to open your arms to tune your report UI/Presentation Server.

Of course if the sql query is taking long time, We know how to tune DB(A)’s  :).

 

 

Thanks,

Shiva.

 
9 Comments

Posted by on September 30, 2011 in BI Publisher, OBI EE, OBIEE 11g

 

Tags: , , , , , , , , , , , , ,