There is a lot of information in the public domain that aids in making educated guesses as to what Big News(tm) will emerge from Oracle OpenWorld 2012.
I recently posted a sneak peek based on information disclosed at Enkitec’s E4 conference. I’d like to reiterate that I do not disclose Oracle confidential information nor have I ever. I signed a binding agreement with Oracle back in 2007 and I honor that agreement. The topic of non-disclosure is fresh on my mind after reading today about the former Navy Seal in hot water for what actually reads just like the legalese I subjected myself to back in 2007. I had no idea service members signed that sort of thing these days. But I digress.
I’ve just got back from watching the re-spin of Total Recall. I was a fan of the Arnold version, but that was 22 years ago (Wow!), so I though it was worth a watch to see what they had brought to the table. As you would expect, some bits are very similar, but there is a lot that is very different from the previous incarnation.
Colin Farrell was pretty good. He certainly looked like he’d hit the gym and stuck to his diet in the lead up to the film. Very impressive. At times I was watching him and found myself thinking he’d make a cracking James Bond! When Daniel Craig gets bored of that gig, Colin should send in his CV.
MySQL management plugin for EM 12c has been long overdue. I’ve initially migrated the older plugin to EM 12c about 6 months ago, and few dozen people received this as the initial beta of the plugin. It worked OK but didn’t use any of the new 12c features, and its home page was a bit of a mess in the EM 12c Cloud Control web interface.
I’ve given examples in the past of how you can be suprised by Oracle when a mechanism that has “always worked” in the past suddenly just doesn’t work because some unexpected internal coding mechanism hits a boundary condition. One example I gave of this was rebuilding indexes online – where a limitation on the key size of index organized tables made it impossible to do an online rebuild of an index on a heap table because of an ORA-01450 (maximum key length) error that was raised against the (index-organized) journal table that Oracle creates internally to support the rebuild.
This blog is a little bit self serving and I’d normally not post it but I think that it would be an awesome deal for those of you who are thinking of buying an Oracle Database Appliance now. We have
several just two left brand new, unopened ODAs left in our inventory that we need to move. Half of them are gone to our customers but there are few still left. We are not really interested in holding on to them while somebody else can put them to good use so we have very very (did I say very?) good price. :) Limited time offer as they say.
Thanks again to everyone who attended part 2 of my Oracle SQL Performance webinar series entitled Making SQL Performance Solutions Stick. Embarcadero will be posting the recording within the next few days. In the meantime, I have uploaded the slides and scripts.
Thanks again and don't forget about the final installment in the series coming next month on September 29 entitled Making Impactful Performance Changes.
I hope to see you then!
There are many questions from few of my clients about asmlib support in RHEL6, as they are gearing up to upgrade the database servers to RHEL6. There is a controversy about asmlib support in RHEL6. As usual, I will only discuss technical details in this blog entry.
ASMLIB is applicable only to Linux platform and does not apply to any other platform.
Now, you might ask why bother and why not just use OEL and UK? Well, not every Linux server is used as a database server. In a typical company, there are hundreds of Linux servers and just few percent of those servers are used as Database servers. Linux system administrators prefer to keep one flavor of Linux distribution for management ease and so, asking clients to change the distribution from RHEL to OEL or OEL to RHEL is always not a viable option.
Do you need to use ASMLIB in Linux?
Here’s the content of an email I sent to Packt back in February this year:
Please ensure that I don’t hear from Packt again.
I have been approached twice in the past and explained that I don’t have the time, and I’m not interested in reviewing books where I have had no involvement with the authors.
This elicited an apology, of course, then on 4th August (after two more pieces of spam from them) I sent them another email quoting the above with the following introduction:
Further to your recent emails, please see below the contents of a note I sent to one of your fellow “executives” at packt a few months ago.
Please note that if I hear from packt again I will publish a note on my blog pointing out that you are a disorganised, incompetent and unprofessional bunch of spammers.
Here’s a simple piece of SQL that could, in theory, compare the current size of a table with the size it could be after a call to “alter table move” – and it’s followed by the results for a table that’s current in the database that I’m looking at:
select blocks, num_rows, avg_row_len, pct_free, ceil(num_rows * avg_row_len / (8000 * ((100 - pct_free)/100))) blocks_needed from user_tables where table_name = 'T1' ; BLOCKS NUM_ROWS AVG_ROW_LEN PCT_FREE BLOCKS_NEEDED ---------- ---------- ----------- ---------- ------------- 25 1000 22 10 4