Hot on the heels of the Linux 64-bit release, Oracle 11g for Windows (32-bit only for now) is now available for download on OTN.
It looks like the second public platform release for Oracle 11g is (surprise, surprise) Linux x86-64. Downloads are available on OTN.
If you are or have ever been a SQL developer, it’s very likely you’ve been asked to return the rows from two joined tables, including all the rows from both tables that do not have a corresponding row in the other table. Oracle 9i introduced the FULL OUTER JOIN syntax to better address this scenario. Now it looks as if 11g has introduced a new algorithm to handle that. So how can you get a look at this? Find out here.
I was very pleased when I heard about Oracle adding pivot functionality in select statements. Finally — we wouldn’t have to copy the data to a spreadsheet or code a ton of sum(case when col1 = ‘X’ then amount else 0 end) total_X for each column we would want to display. I am basically looking for three things in a pivot-style query: the ability to specify which column will be pivoted as one or more columns in the resulting query, row subtotals, and column subtotals. The first item is the only one that really matters. I can work around the other two, so let’s get started.
It seems Oracle 11g introduces a difference between count(*) and count(1). The way this happens is just the opposite of what I was thinking would happen. NB: I ran my test using “126.96.36.199 32bits” on Ubuntu Linux 7.04 (Feisty) which is not officially supported1, and which has already lead me to some unexpected behaviors. If this difference with count() is really the 11g way and not buggy behavior related to the Ubuntu install, I’m glad to have found it. Here’s what you can do to observe (or confirm or dispute) this.
I’m a MySQL DBA trying to draw a map of this new (to me) world called Oracle. The other day I was trying different things with Oracle, like (but not limited to) issuing kill -9 to random Oracle processes to see what would happen (on my own box of course!). I was a little surprised by the results. They’re probably no news for most of you guys, but it is new to me, and I’d like to share my findings with other MySQL guys around the planet.
Today, I installed RAC on Oracle Enterprise Linux 5 (OEL5), and I can tell you that there’s nothing exceptional about the process. The only trouble I encountered had nothing directly to do with the installation. Besides that, it’s all quite simple once 10g’s prerequisites are met. After an hour and a half, it was all wrapped up, at least for two nodes. I didn’t see anything revolutionary differences, but nonetheless there are some points worth mentioning.
In the previous article, I described my observations of RC Enqueue. Now it is time to take a look at the RC latches.
If you heard something about Miracle Database Forum, you might already know what to expect. Those of you who have already been there once probably registered already. For the rest of you, keep clicking these links to read reviews of last year’s event in Lalandia, and even take a peek here.
The latest release of Grid Control (10.2.0.3 at the time of this writing) is only able to schedule backup jobs with simple interval based on frequency (every month, week and etc). So if you want to schedule incremental backup from Backup Wizard – you will have to do a trick. First create this job using the wizard and then change its schedule. When you editing the job – more options are available. View the screen shots in this post