Yes, I have quite a backlog of topics I should blog and thanks to Robin for pointing it out.

A quick reminder about using the right wlst.sh.

In a normal OBIEE installation, you will find multiple wlst.sh in the MIDDLEWARE_HOME:


Make sure to always start your wlst scripts from

in order to prevent erroneous behaviour. Running them from a different location will yield interesting errors like the one below – taken from a migrateSecurityStore example:

    TypeError: cannot concatenate ‘str’ and ‘NoneType’ objects



OBIEE became available yesterday evening (CET) first on edelivery and in the meantime on OTN as well. Here’s a link library of the most important and interesting sources.


Overview and explanatory blog posts:

“New Features with OBIEE”

“OBIEE Now Available for Download – Release Highlights”
“OBIEE : MDS XML Repositories, and Integration with Source Control”

Michael Verzijl
“OBIEE Released – Short overview”

“OBIEE 11g R1.6 New Admin Feature”

Alex Hansal
“OBIEE is here”

“OBIEE new features/enhancements”

Official Documentation

Maintenance Release Guide (List of Bugs Fixed) for Oracle Business Intelligence Enterprise Edition (OBIEE) [ID 1412748.1]

Documentation Library
New Features OBIEE
New Features OBIEE for Users
(h/t @lex!)

This is just a first list and will grow over time. If you have new, interesting links to add, please put them in the comments and I’ll update the list.



I recently deployed a new RPD to one of my BI servers and after restarting the coreapplication, wasn’t able to log on anymore – the login process hung at “Singing in…” indefinitely.

After some investigation, I found out what had happened:
1.) The new RPD used connections to a datasource situated on a different database (other than the primary DWH) which were utilised in new initialization blocks which fired upon login (no “deferred execution”).

2.) The TNSNAMES on the BI server machine had contained all necessary connectivity information until the night before, but had been reset to a default configuration during the night for some reason and only retained the primary DWH.

3.) This caused the login process to hang indefinitely without any meaningful errors being logged and hence nothing was visible in Enterprise Manager.

4.) Restoring the TNSNAMES with all relevant DB entries removed the error and login was possible again.

Conclusion: never assume that your infrastructure setup is a “given” and won’t change.