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.

A new blog from James Morle, who I don’t know but from other bloggers sounds well respected, and describes himself thus: Since it’s been nearly ten years since I wrote my book, Scaling Oracle8i, I thought it was about time that I started writing again. I thought I would start with the new-fangled blogging thing, and see where it takes me. Here goes. He’s got a really interesting post on “red flags” to look for in diagnosing performance problems in Oracle: Spotting the Red Flags (Part 1 of n).

SQL Developer v2.1 Early Adopter was released yesterday. Download it here New features list Hat-tip and hat-tip

Bit of an odd one this. Oracle 11g database, a user’s password has expired. But when I try to change it, I can’t: [sourcecode language=“bash”] $sqlplus MYUSER/oldPW@oraDBServer SQL*Plus: Release 10.2.0.1.0 - Production on Wed Sep 23 07:57:41 2009 Copyright (c) 1982, 2005, Oracle. All rights reserved. ERROR: ORA-28001: the password has expired Changing password for MYUSER New password: Retype new password: ERROR: ORA-01017: invalid username/password; logon denied Password unchanged [/sourcecode]

(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.

Here’s a list of the OBIEE benchmark documents published by Oracle: 28,000 User Benchmark on Sun SPARC Enterprise T5440 Server running Solaris 10 [Aug 09] 10,000 User Benchmark on Sun T2000 [Sept 07] 5,800 User Benchmark on HP DL380 G4 [Sept 07] 4,000 User Benchmark on an IBM System x3755 Server running Red Hat Enterprise Linux

Production cluster is 2x BI Server and 2x Presentation Services, with a BIG-IP F5 load balancer on the front. Symptoms Users started reporting slow login times to BI. Our monitoring tool (Openview) reported that “BIServer01 may be down. Failed to contact it using ping.”. BIServer01 cannot be reached by ping or ssh from Windows network. Diagnostics nqsserver and nqsclustercontroller on BIServer01 was logging these repeated errors: [nQSError: 12002] Socket communication error at call=send: (Number=9) Bad file number

A new version of the web browser Opera was released recently. Several years ago I used Opera and may even have paid for it IIRC. Then Firefox came along, and the “it’s not IE” excuse was lost for Opera. Not that I mind IE too much nowadays but at the time it was atrocious. Since then I’ve revisited Opera each time a new release has come out, but nothing has impressed me enough to ditch Firefox (and nowadays Google Chrome).