I heard this on Thinking Allowed and thought how applicable it was to the attitudes that you can sometimes encounter in both systems development, and the support of production systems: “Each uneventful day that passes reinforces a steadily growing false sense of confidence that everything is all right – that I, we, my group must be OK because the way we did things today resulted in no adverse consequences.” by Scott Snook (Senior Lecturer in the Organizational Behavior unit at Harvard Business School )

Last month I wrote about a problem that Informatica as part of OBIA was causing us, wherein an expired database account would bring Oracle down by virtue of multiple connections from Informatica. I raised an SR with Oracle (under OBIA support), who after some back-and-forth with Informatica, were told: This is not a bug. That the two error messages coming back from Oracle are handled differently is the result of a design decision and as such not a product fault.

As Twitter learnt yesterday, you should always sanitise user input. I was amused to see My Oracle Support doing so….recursively :) The apostrophe in “doesn’t” got escaped once, and then again, and then again, and then again, and then again ……

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.

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.

Metalink was retired this weekend and made way for the new My Oracle Support system. It didn’t go as smoothly as it could have done. This post is going to be a bit of a rambling rant. Ultimately people, including me, don’t like their cheese being moved (not unless there’s a really runny piece of Camembert at the end of it). That makes it a bit more difficult to discuss because some of people’s complaints will just be geeks being stubborn (and boy, can geeks be stubborn).

For some reason Oracle haven’t put out a 10.x version of the error & message codes reference guide for OBIEE, but the previous version for Siebel Analytics is still useful: PDF version: http://download.oracle.com/otndocs/products/bi/bi-ee/docs/784/AnyMsg.pdf HTML version: http://download.oracle.com/docs/cd/E12103_01/books/AnyMsg/AnyMsg_Messages.html#wp1007961

A follow up to my previous post about Metalink’s “Do you mean” feature, this one made me laugh: I shall miss this kind of thing when Metalink3 merges into My Oracle Support…. Meep meep!

One of my little gripes with Metalink is its purporting to be helpful when it’s blatantly not. Here’s one: Now which is more likely, on Metalink 3; that I’m searching for sawserver (integral component to OBIEE), or sqlserver?!

I’m learning about a lot of the Oracle BI stack through reading manuals and trial-and-error. One thing I’ve realised is that Metalink holds a whole heap of useful information. For example, simply searching on “publisher cluster” throws up these two very pertinent docs: OBIEE Clustered Installation with BI Publisher (Doc ID 744515.1) BI Publisher does not accept cluster jdbc connection strings (Doc ID 559795.1) The first one is a publically available PDF, the second one is the answer to the problem I spent more time than I needed to scratching my head over yesterday.