I’m doing my first ever conference presentation next month at the 2010 Rittman Mead BI Forum. My presentation is called Performance Testing OBIEE, which is something I’ve spent a lot of time working on over the last few months. I think the challenge is going to be distilling it all into a session that’s not going to overwhelm everyone or bore them to death! Well, actually, the challenge is going to be the presenting.

Spotted this when trawling through My Oracle Support. It’s pretty common knowledge anyway amongst people already familiar with hacking around with OBIEE, but worth recording for people coming along to it new. Doc ID 1068266.1 states: UDML is not supported in OBI 10g. in 11g, XUDML (the Oracle BI Server XML API) will be fully supported and documented.

JMX OBIEE’s Systems Management functionality exposes performance counters and the application’s configuration options through Java MBeans and optionally a protocol called JMX. It’s extremely useful, and is documented pretty widely : JConsole / JMX JConsole / JMX – followup Oracle BI Management / Systems Management MBeans PerfMon OBIEE MBeans and OC4J OBIEE performance monitoring and alerting with jManage In this article I’m going to discuss the use of JMX to access these counters remotely, and a possible security issue that’s present in the BI Management Pack manual.

We hit a very interesting problem in our Production environment recently. We’d made no changes for a long time to the configuration, but all of a sudden users were on the phone complaining. They could login to BI from EBS but after logging in the next link they clicked took them to the OBIEE “You are not logged in” screen. Our users login to EBS R12 and then using EBS authentication log in to OBIEE (10.

A sad little passing last week, of the Oracle Support Blog and related tweets by Chris Warticki. Last week Chris posted this comment on twitter “So, what to do if you’re the “online customer presence” and your own leadership wants to censor your posts and comments?” followed by this terse blog posting: Support Blog: No longer available By chris.warticki on February 12, 2010 4:08 PM Please use My Oracle Support Communities instead

I stumbled across this blog posting recently, and am reposting the link here as I’ve seen no mention of it elsewhere. This surprised me as with Exadata (and most new technologies) any snippet of news or tech insight gets blogged and tweeted multiple times over. Any insight into Exadata is interesting as unlike all the other Oracle software which can be downloaded and poked & prodded, this is a physical box so we rely on blog postings and marketing (with a BS filter) to understand more about it.

You get a call from your friendly DBA. He says the production database is up the spout, and it’s “that bee eye thingumy causing it”. What do you do now? All you’ve got to go on is a program name in the Oracle session tables of “nqsserver@MYSERVER (TNS V1-V3)” and the SQL the DBA sent you that if you’re lucky will look as presentable as this: The username against the SQL is the generic User ID that you had created for connections to the database from OBIEE.

This error caught me out today. I was building a Linux VM to do some work on, and for the life of me couldn’t get the OBIEE Admin Tool to connect to the BI Server on the VM. The error I got when trying to define a DSN on the Windows box was: [nQSError: 12008] Unable to connect to port 9703 on machine 10.3.105.132 [nQSError: 12010] Communication error connecting to remote end point: address = 10.

Quick post as the snow’s coming down and I wanna go home … I’ve been working on building a VM based on OEL5.4 and OBIEE 10.1.3.4.1. After installing XE 10.2 I tried to fire my RPD up, but hit this: /usr/lib/oracle/xe/app/oracle/product/10.2.0/server/lib/libnnz10.so: cannot restore segment prot after reloc: Permission denied [nQSError: 46029] Failed to load the DLL /app/oracle/product/obiee/server/Bin/libnqsdbgatewayoci10g.so. Check if ‘Oracle OCI 10G’ database client is installed. If you trace the ‘stack’ back you find that it parses down to this nub of an error:

Mucho kudos to Borkur Steingrimsson for getting the OBIEE admin tool working on Unix!