Oracle’s 220.127.116.11 was released a few weeks ago (You can download it from OTN here: Oracle 18.104.22.168 Download). While technically a minor point release, it contains a couple of major features that would normally be rolled out in a more substantial version change like 12cR2 or perhaps V13. Of course the most highly anticipated feature is a new option (Oracle In-Memory Option) that provides a column oriented, in-memory store. Enkitec was in the Beta program, so we’ve been testing it out for quite a while now and we are impressed.
As well as losing the ACED OpenWorld confirmation email, it turns out my website/mailbox move also caused me to lose the email about being accepted on the OTN APAC Tour 2014. I saw a tweet this morning saying that I was on the agenda for the NZOUG event and checked with Francisco to see what was going on. That’s when I found out that yet another important email had gone missing…
The good news is I had already agreed the time off work, so everything is good for the tour.
When installing Enterprise Manager 12c, the host value can come from a number of places for different applications/tiers. For most, it comes from the environment variable $ORACLE_HOSTNAME, (for Windows Servers, %ORACLE_HOSTNAME%).
As much as KSCOPE 14 fixed any and all Low-T levels, it couldn’t do anything for our the WiFi problems we were experiencing back in May. I’ve been a telecommuter for almost 4 straight years now and was quite frustrated when our WiFi service became dismal back then.
If you watched my (No) Ice Bucket Challenge yesterday, you will know I nominated my Oracle family.
The first family member to step up to the plate was the daughter, Heli “Hell-Squirrel” Helskyaho. She shared the video on Facebook, which you can see here if you are a friend. We have to be careful with the parental controls to keep her safe!
Next up was the wife, Debra Lilley, who used the opportunity to do an Oscar acceptance speech.
The title of this piece is the name given to a new feature in 22.214.171.124, and since I’ve recently blogged about a limitation of the in-memory option I thought I’d pick this feature as the next obvious thing to blog about. This is a bit of a non sequitur, though, as the feature seems to have nothing whatsoever to do with the in-memory option; instead it’s a cunning mechanism combining aspects of the star-transformation (but without the bitmap indexes), Bloom filters, and “group-by” placement to minimise the cost of aggregation over high-volume joins.
Here’s a small data set I’ll use to demonstrate the feature:
I recently read a blog post by Kyle Hailey regarding some lack of randomness he detected in the Orion I/O generator tool. Feel free to read Kyle’s post but in short he used dtrace to detect Orion was obliterating a very dense subset of the 96GB file Orion was accessing.
Here’s a script to create a table, with index, and collect stats on it. Once I’ve collected stats I’ve checked the execution plan to discover that a hint has been ignored (for a well-known reason):
I forgot to mention, I put another multitenant article live at the weekend.
I’m not sure I will ever use it, but it’s good to know it’s there.
I was originally working on an article on a completely different multitenant feature, but the examples I was using highlighted a bug, which kind-of scuppered that article. I’ve raised an SR and I’m waiting on the acknowledgement and possible fix. I’ll hold that article back until the fix is in place.