This is probably as much a note-to-self as it can possibly be. Recently I have enjoyed some more in-depth research about how the Linux kernel works. To that extent I started fairly low-level. Theoretically speaking, you need to understand the hardware-software interface first before you can understand the upper levels. But in practice you get by with less knowledge. But if you are truly interested in how computers work you might want to consider reading up on some background. Some very knowledgable people I deeply respect have recommended books by David A. Patterson and John L. Hennessy. I have these two:
Oracle 18.104.22.168 is out, after lots of announcements the product has finally been released. I had just extended my 22.214.171.124.3 cluster to 3 nodes and was about to apply the July PSU when I saw the news. So why not try and upgrade to the brand new thing?
What struck me at first was the list of new features … Oracle’s patching strategy has really changed over time. I remember the days when Oracle didn’t usually add additional features into point releases. Have a look at the new 126.96.36.199 features and that would possibly qualify to be 12c Release 2…
In summary the upgrade process is actually remarkably simple, and hasn’t changed much since earlier versions of the software. Here are the steps in chronological order.
I don’t know how often I have type ./ruinInstaller instead of runInstaller, but here you go. This is the first wizard screen after splash screen has disappeared.
I did a quick update of my Oracle installation articles on Oracle Linux 7. The last time I ran through them was with the beta version OL7 and before the release of 188.8.131.52.
The installation process of 184.108.40.206 on the production release of Oracle Linux 7 hasn’t changed since the beta. The installation of 220.127.116.11 on Oracle Linux 7 is a lot neater than the 18.104.22.168 installation. It’s totally problem free for a basic installation.
You can see the articles here.
With all the excitement around the release of Oracle Database 12.1.02, it’s easy to forget that there is other stuff going on as well.
Just remember, it takes quite a while to get products certified on this stuff, so although I’ve already tried installations on the beta versions, I would not install any Oracle products on this stuff “for real” until the official certification is announced for each product.
I had an interesting discussion as part of my latest presentation at the UKOUG RAC CIA & Database Combined SIG. Part of my talk was about the implications of the new threaded execution model in Oracle.
Since “we do not use Windows” (except for gaming) I can’t compare the Windows thread model to the new 12c implementation on UNIX. There are however interesting implications when switching to the new model, some of which I’d like to demonstrate here. First of all, threaded execution is not enabled by default. With 22.214.171.124.3 on top of Oracle Restart you get the either all or a subset of the following background and auxiliary processes for a CDB:
Direct NFS is a great feature that I have finally had the time to investigate further. Since I always forget how to set it up and I didn’t find blog posts about this subject elsewhere I decided to put something together.
In this configuration I am using a virtual machine named server1 to export a directory to server2. Oracle is not as lenient as myself and may have certain support requirements when it comes to dNFS servers but I just wanted to get started.
The export of the NFS mount is shown here:
A few months ago I wrote about some MySQL on Oracle Linux migrations we were working through. It’s been a long time coming, but last weekend was the go-live for this batch of migrations. So far so good!
Most of the elapsed time since my last post on this subject has been spent with the developers and users testing the migrations.
I recently was involved in an investigation on a slow-running report on an Exadata system. This was rather interesting, the raw text file with the query was 33kb in size, and SQL Developer formatted the query to > 1000 lines. There were lots of interesting constructs in the query and the optimiser did its best to make sense of the inline views and various joins.
There’s been some debate about how to get the parameters from a spfile. A spfile is a binary version of the parameter file of the Oracle database.
I added to the debate that my experience is that there are is some weirdness with using the strings command on the spfile. The discussion was on twitter, I didn’t add that doing that it most of the time meant it costed more time than I saved from using the “shortcut” of using strings on a spfile.
Let me show you what it means.
I’ve got a database with storage on ASM. Among other options, there are two simple methods to get the spfile from ASM:
You can get the spfile by logging on to the database, and create a pfile from the spfile, and create a spfile again:
It feels almost like heresy to discus something that isn’t Oracle-related on the day that Oracle announced the new In-Memory Database Option, but something else was also released today. Red Hat gave birth to Red Hat Enterprise Linux (RHEL) 7.
I’m a big fan of all things Linux. I’m typing this blog post on a Fedora 20 desktop at home. I’m a rabid fan of Oracle Linux for servers at home and at work. As a result, the birth of RHEL7 is a pretty big deal for me.