A few months ago I mentioned doing some Fedora 22 installations. At the time I did some pre-emptive installations on the Alpha release of Fedora 23 also.
Now the final release of Fedora 23 is out, I’ve run through the articles again to make sure things are all ship-shape.
It’s pretty much as it was before, with the nice bonus that the “MATE Desktop” package group has been fixed. Happy days!
As always, installations of Oracle server products on Fedora are not a great idea, as explained here.
If you do like playing with this stuff, knock yourself out…
Fedora 21 has arrived and it’s now delivered in three focussed flavours (Workstation, Server and Cloud). This of course resulted in the usual articles from me.
As always, read the warnings before you start down this path.
From an Oracle installation perspective, it’s almost identical to Fedora 20. I chose to use the server flavour and install the “MATE Desktop” package group. I suspect others may prefer to start with the workstation release. Either way it should be fine.
As I suspected, switching my main desktop from Fedora to the MacBook means I care significantly less about this release than before, but I still have some upgrades I’ll need to plug through.
I’ve been having a play with Oracle Linux 7 beta over the weekend. Not surprisingly my first thoughts were to install the Oracle database on it.
As expected, the installations were almost identical or Fedora 19.
I’ve put a warning on the front of the OL7 articles, but I’m sure it won’t stop some Muppets using it in production then trying to blame me.
I don’t know how long it will be until OL7 goes to production and I’m sure it will be a long time before anything is certified against it, but it’s always nice to see what’s coming… I’ll update the articles when anything significant happens…
Just a little slice of reality to cut through all the 12c stuff that is floating around at the moment. I’ve just moved the last of our databases to 11g. Yay! As well as upgrading, we’ve been culling or consolidating old and unused stuff, which has drastically reduced and simplified our Oracle database landscape.
We currently have four projects running databases on HP-UX on Itanium (spit), one project on Solaris and the rest on Oracle Linux under VMware. If I had my way we would kick out HP-UX and Solaris and do everything on Oracle Linux.
We’ve still got one project on 11gR1, but that is being held back intentionally because of some issues with the vendor of the application that runs against it. Hopefully that will soon be on 11gR2 also.
So about 7 years after the release of 11gR1 and 5 years after the release of 11gR2 we have finally managed to get there. Judging by the conversations I’ve had over the last year, I would say we are ahead of the curve. There are still plenty of people out there with old versions lurking around for a variety of reasons…
With this in mind, what do you think our timescales are for a move to 12c? Like many people, I don’t think it will even be considered until 12cR2 is released and even then it won’t happen over night.
Even so, I still believe it is important that people get their heads around what 12c has to offer. Of all the releases in my time working with Oracle products, I think 12c is the one that is really going to mess with people’s heads. If people don’t spend a significant time getting to know this stuff they are going to make really bad decisions and totally stuff up their installations!
I mentioned the day before Open World I put a Virtual RAC on Oracle Linux 6.1 article live. Although the procedure was complete, some of the screen shots were from an old article as I didn’t have time to redo them before my flight. I’ve just run through the procedure again and taken new screen shots. As a result, I’ve allowed the article to display on the front page of the website, which is why you will see it listed as a new article there.
This kinda rounds out the whole Oracle on 6.1 stuff as there has been a single instance installation guide out for ages and more recently the Cloud Control installation, which references it.
Remember, it’s still not certified yet, but it’s coming.
Update: It’s finally certified. See here.
Well a new day and a fresh pair of eyes and it all went well. I was out this afternoon so I started the final bit of the installation running and it had completed successfully when I got home.
I’m not totally sure what was causing the previous problems. I had been taking snapshots of my VM at regular intervals over the last couple of days and I guess something must have been dodgy because when I threw it all away and started again from scratch it worked fine. Here is the installation guide listing all the steps:
So does this success change my opinion of this release? Not at all. The installation is a mess and I think Oracle really do need to have a shrink-wrapped install, even if it is a 8G download. It would reduce the barrier to entry and I just think it feels a little poor that you have to manually install a bunch of patches before you can get the product working. Makes me wince a little.
I’ve spent the last couple of days failing to install OEM Grid Control 11g on OEL 5.5 x86-64 with a 11gR2 database for the repository. The installation process is horrid. You have to manually install and patch the database and middleware software before starting the GC installation. So you end up with a whopping 7.1G of software, not including patches and the OS.
The docs are not ideal. There is a lot of cross-referencing to bugs, patches and metalink notes, which means I’ve often had about 10 browser tabs open while performing the installation. I can only assume that somewhere in the mish-mash of the docs I’ve missed something out.
I feel really disappointed with the installation process for this release. In my opinion there should be a single installation that includes the middleware, database and all necessary patches. I like to think of GC as a shrink-wrapped product I can install separate to everything else and leave alone. Not any more…
I’m off to ODTUG this week, so I’m not sure I can be bothered to waste more time on this until I get back. Perhaps someone there will be able to explain to me what the hell is going on with it.
My previous article discussed the DBFS. This article gives an overview of the PL/SQL APIs for managing and interacting with the DBFS.
There’s a lot in there, so this is just skimming the surface.
I finally got round to trying an NFS installation of 11gR2 RAC.
No real surprises here. It all seems a little simpler when using NFS, but it was cronically slow on my crappy kit.
I’ve taken my first tentative steps into 11gR2 RAC and it was a big surprise.
11gR2 RAC feels very different to 11gR1 RAC. I can imagine quite a few people wanting to upgrade from 11gR1 thinking it will be trivial and getting a rude awakening…
The Grid Infrastructure (Clusterware + ASM) seems more complicated. There are more installation options, more prerequisites, more background processes and a bigger memory requirement…
I typically install 11gR1 RAC on VMware using 1G of RAM per VM. If you try that with 11gR2 you will get to the end of the Grid Infrastructure installation and have nothing left. The minimum recommendation for Grid Infrastructure alone is 1.5G, but if you want the RAC DB as well you are talking 2.5G. It actually worked fine with 2G of RAM allocated to each VM, but this is a whopping increase compared to 11gR1.
At this point I feel like I know nothing about 11gR2 RAC, but it certainly doesn’t feel like a patched version of 11gR1. If this had been released as 12g I would have still have been surprised by the level of change.
So over the next few days I’m expecting the dust to settle, my residual fear of all things new to subside and I’ll probably change my opinion completely and think it’s all the same as it was before…
PS. Please don’t try this installation on your 32-bit Windows laptop with 2G of RAM then write to me complaining it doesn’t work and telling me the article is rubbish…