Like an invincible psycho with a knife, Log Buffer is back, with a Friday the 13th issue (“Larry’s Revenge!”). Daniel Fink of OptimalDBA is the lucky one to do this 53rd edition of the weekly review of database blogs.
Let’s focus on what 11g is all about. The main message I got is that Oracle 11g is the consumer release. According to Mr. Phillips, what this means is that Oracle has listened to its clients and has worked in the areas that the consumers needed the most. The fact that Ari Kaplan, the president of the IOUG, was on stage during the launch speaks for itself. As for what’s new in 11g, three major features come to mind…
n the following SQL*Plus output something is goofed up. You should not have a no rows selected with this SQL. When you see something like that for the first time, you can generally draw from four conclusions: Someone edited the output, SQL*Plus bug, Oracle bug, combination of the above. Since it was me who saw this, number one was an easy but irrelevant answer. What about an SQL*Plus bug? OK, run this using some other ad hoc tool. Same result. Time to take a more precise look at the problem. What is trans?
Taking the cue from Jay Pipes, as so many other bloggers have done, I present the five things I would most like to see in a future release of MySQL.
Last week, in collaboration with several of my colleagues here at Pythian, I published an open letter to Larry Ellison. The response to this letter has been — well — surprising, both in volume and in character. It is clear that many in the Oracle community seem to share the sentiments that we have expressed. In fact, we know that we are not alone in this endeavour.
The 52nd edition of Log Buffer is up, edited by Dominic Brooks and published on his blog, OraStory. On deck, Daniel Fink.
As you might imagine, the traffic to the open letter from the oracle.com domain has been spiking in the last few days. Two days ago, in fact, Christo received an email from Oracle putting into question the fact that AWR data collection could not be disabled without a license to the diagnostic pack, and promptly forwarded that note to me. So as it turns out, Oracle has been working on a package to disable the AWR data collection without requiring a license for at least two months. But as of yesterday, it had not yet been published.
15 years ago, with the release of Oracle 7.0.12, Oracle gave the world—or at least its customers—something really great: the Oracle Wait Interface (OWI). We believe that the Oracle database software is the best instrumented database software available. The fact that Oracle already leads the industry in this regard probably led to their decision to make this leap forward in instrumentation an extra-cost item. However, in the interest of making Oracle even better, we would like to invite readers to join us in signing the following open letter to Larry Ellison, CEO of Oracle Corporation.
Wilfred van der Deijl (fresh from an award-winning appearance at ODTUG) has published the 51st Log Buffer on OraTransplant.
Before you proceed with reading this post, I strongly encourage you to read Tom Kyte’s trilogy about write consistency, since I’ll do only a brief introduction to the subject. The way Oracle ensures UPDATE write consistency is through a mechanism called restart. Let’s take a look at an example before we proceed with the main topic of this blog post, Will there be any difference if we substitute the following MERGE for the last UPDATE?