A frequent question on the OTN OBIEE forum is how to fix this error: [nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. The error is simply OBIEE reporting that it tried to connect from the BI Server to an Oracle database and the Oracle client returned an error. Distilling it down gives us this error:

October’s Oracle Critical Patch Update Advisory has been released. There are two vulnerabilities (CVE-2009-1999, CVE-2009-1990) listed under Oracle Application Server for “Component” Business Intelligence Enterprise Edition and one (CVE-2009-3407) for “component” Portal. CVE-2009-1999 is OBIEE and “Fixed in all supported versions. No patch provided in this Critical Patch Update.”. CVE-2009-3407 looks like only OAS (not OBIEE), up to versions 10.1.2.3 and 10.1.4.2. CVE-2009-1990 is OBIEE and is the main vuln of interest.

Two new blogs of note : Shiv Bharti’s Blog Debashis’s OBIEE Blog Both are well worth a read & following.

Watch out if you are using init blocks in your RPD. We hit a bug (#9019374) recently that caused BI Server (10.1.3.4) to hang. The init block in question should have returned a date to update a repository variable, but because of badly-written SQL and abnormal data in the source table actually returned a null value. BI Server evidently didn’t like this null being inserted somewhere where it shouldn’t have and understandably logged :

The Critical Patch Update Pre-Release Announcement for October has been published. The pre-release is advance notice of the affected software prior to release of the quarterly Critical Patch Update. It is published on the Thursday prior to the patch releases (which was postponed by a week because of OOW). It looks like if you’re running OBIEE 10.1.3.4.0 or 10.1.3.4.1 through OAS 10.1.2.3.0/10.1.3.4.0/10.1.3.5.0 then you should check back next Tuesday 20th for details.

A new OBIEE benchmark has been published by Oracle. It’s on the same hardware as August’s benchmark - Sun T5440s. Anyone would think that Oracle like Sun ;-) Details here Numbers added to my collation post here

OBIEE comes with a very useful usage tracking feature. For information about it and how to set it up see these links: http://obiee101.blogspot.com/2008/08/obiee-setting-up-usage-tracking.html http://www.oracle.com/technology/obe/obe_bi/bi_ee_1013/usage_tracking/usage_tracking.htm http://108obiee.blogspot.com/2009/07/obiee-usage-tracking-setup-and-cloning.html Usage Tracking captures the logical SQL of queries in a column called QUERY_TEXT in the table S_NQ_ACCT. However, out of the box this column is defined as 1k (1024 bytes) long. In some situations this will limit its usefulness because the text will be truncated if necessary when it’s inserted.

This is a supplemental post to this one describing how to set up a VUser in LoadRunner to test OBIEE. It’s various notes that I made during the development but which aren’t directly part of the step-by-step tutorial. They’re not necessarily vital for recording scripts, but observations and explanations that should be helpful when working with LoadRunner and OBIEE. Validation using sawserver logs It’s no use running a load test if the load you think you’re applying isn’t actually being applied.

My two earlier posts (here and here) detail the difficulties I had with LoadRunner (now called HP Performance Center). After a bit of a break along with encouragement from knowing that it must be possible because it’s how Oracle generates their OBIEE benchmarks I’ve now got something working. I also got a useful doc from Oracle support which outlines pretty much what I’ve done here too. In essence what you do - and what the Metalink document 496417.

(Updated 12th Oct 09) Here’s a list of the OBIEE benchmark documents published by Oracle: BenchmarkDateSource document1 - IBM System x3755Sep-07PDF2 - HP DL380 G4Sep-07PDF3 - Sun T2000Sep-07PDF4 - Sun SPARC Enterprise T5440Aug-09PDF5 - Sun SPARC Enterprise T5440Oct-09PDF Collecting the numbers into one table gives this: Based on the details in the documents I think these were all against OBIA’s Service Analytics schema & dashboards/reports. Interesting to note the side-by-side comparison in benchmark 3 (Sun T2000) of two servers, in one case both running BI and Presentation Services and in the other having the two components separate.