Why do I do this? As mentioned in the first link, Fedora is a proving ground for future versions of RHEL, and therefore Oracle Linux. I like to see what is coming around the corner. Doing this has no “real world” value, but I’m a geek, and this is what geeks do. 🙂
As an aside, when Fedora 35 was released I was having a lot of trouble getting 19c and 21c installed on it. I tried a number of times over the course of a few weeks and failed each time. When I tried those same installations on Fedora 36 they just worked, so I went back and tried on Fedora 35 again, and they worked there too. Clearly there have been some changes to underlying Fedora 35 packages that have fixed whatever the problem was with the Oracle installations. As a result, I also produced these.
So what’s new with Fedora 36? It’s a bleeding edge distribution, so as you might expect, loads of package version updates, bringing most things to the latest and greatest versions. The things that stand out for me are Ansible 5 and Podman 4.0. If you want a more complete perspective on this, you might want to look here.
Fedora 29 has been out for a bit over a week now. Over the weekend I had a play with it and noticed a couple of differences between Fedora 28 and Fedora 29 as far as Oracle installations are concerned. There are some extra packages that need to be installed. Also, one of the two symbolic links that were needed for the Oracle installation on Fedora 28 is now present in Fedora 29, but pointing to the wrong version of the package.
Fedora 28 has been out for quite a while now. I installed it pretty much when it was released, but hit a problem with installing Oracle 12c on it. I didn’t have much time to investigate at the time and I kind-of forgot about it. A couple of days ago someone asked me about it, so I had another attempt. The only difference compared to Fedora 27 was a couple of extra symbolic links were needed.
Fedora 27 has been out for a couple of weeks now, but I’ve not really been able to do anything with it because I couldn’t get it installed on VirtualBox. I finally managed to get the installation to work, provided I used the Live DVD when I was running VirtualBox on an Oracle Linux 7 host. That means I was finally able to have a play with 12cR2 on Fedora 27.
Fedora 26 has been out for a while now. As soon as it dropped I tried to do some 12c installations on it and hit a stumbling block. The software would install and link fine, but it wouldn’t start up Oracle processes, so you couldn’t actually create a database using the DBCA or SQL*Plus. I roped in Frits Hoogland to help me find the issue, which he did through the magic of strace. 🙂
With that information, a bit of Googling revealed other software that was struggling with changes to glibc, with the only reliable solution (to their problems) being to downgrade to glibc from Fedora 25. That didn’t sound too satisfactory to me.
If I’m honest, I got kind-of bored by it until Andy Campbell made me aware of a workaround, so I was finally able to get 12cR1 and 12cR2 working fine on Fedora 26.
Since Fedora is the proving ground for future releases of Red Hat Enterprise Linux (RHEL) and I’m a fan of running Oracle on a binary clone of RHEL called Oracle Linux (OL), I am curious about any new release.
Not surprisingly, Oracle database 12c installs really easily on Fedora 25, just as it did on previous releases.
I did have the usual problem with the Perl stuff, as I’m running the VM on a relatively modern MacBook Pro, which has a CPU that freaks out the version of Perl shipped with Oracle, but the article includes a link about how to fix that. I’ve repeated the installation under VirtualBox on systems using older chips (my work PC and an old server at home) and it works without complaint. No drama.
So all seems well in the world of Oracle 12c on Fedora 25. Now you know how to do it, please don’t. Use Oracle Linux. 🙂
No real drama here. It was pretty much the same as Fedora 23 in that respect.
It’s kind-of hard to get excited about a new version of Fedora since I switched my desktop from Fedora to Mac. One thing that was interesting is the change to the upgrade process. In previous releases I used “fedup” to do it. Now it’s pretty much done using DNF (YUM). If you are interested, you can read about it here.
This did cause one really annoying problem in F23 though. The “MATE Desktop” had a single documentation package that was causing a problem. Usually I would use the following.
yum groupinstall "MATE Desktop" -y --skip-broken
Unfortunately, DNF doesn’t support “–skip-broken”, so I was left to either manually install the pieces, or give up. I chose the latter and use LXDE instead. 🙂 F23 is an Alpha, so you expect issues, but DNF has been in since F22 and still no “–skip-broken”, which I find myself using a lot. Pity.