Catch Up Delayed…

Sadly, my uncle died on Easter Sunday, at the (for our family!) grand age of 82. My aunt is not taking it particularly well which, given they were married for 59 years, is not entirely surprising.

I will say that getting 12cR2 installed on Ubuntu-based distros is not just a question of altering the gcc version in use, as I had hoped in my last post: I tried that without success. Meaning that we are still without 12cR2 working on any Ubuntu-based distro and with no obvious, simple fixes.

And, I’m afraid, given the need to organise family stuff and deal with funeral attendance etc., it’s unlikely I’m going to get much further with Ubuntu and 12cR2 for some weeks to come.

I’ll get back to it when I can. Meantime, please forgive and understand the posting silence that will now ensue for some time.

Atlas and 12cR2

Continuing the saga of “catching up” with software developments whilst I was en route to the UK from Australia, the question next to be addressed is simply: does Atlas work to allow Oracle 12c Release 2 to be installed onto the many and various distros it claims to support.

The answer is a bit mixed, I’m afraid!

First thing to say: I deliberately coded Atlas to specifically declare 12cR2 ‘didn’t work yet’ when I first released it. So, for it to work for 12cR2 at all, that bit of code has to be removed -and that means Atlas straightaway gets bumped to version 1.2.

Once that code has gone, the good news is that Atlas will successfully help 12cR2 be installed on the majority of the distros it works with (15 out of 19, as it happens). But the bad news is that if your distro is Ubuntu or even just Ubuntu-based, then the linking phase of the Oracle 12c Release 2 installation fails irreparably after Atlas has been run.

The complete list of distros and their results with Atlas for 12c Release 2 is therefore as follows:

Debian 8.2+ ............................ Works fine
Linux Mint 18+ ......................... Fails
Mint Debian Edition 2+ ................. Works fine
Red Hat ES 7.0+ ........................ Works fine
Scientific Linux 7.0+ .................. Works fine
CentOS 7.0+ ............................ Works fine
OpenSuse Leap 42+ ...................... Works fine
Antergos  2016.11+ ..................... Works fine
elementary OS 0.4+ ..................... Fails
Mageia 5+ .............................. Works fine
Korora 25+ ............................. Works fine
Zorin Core 12 .......................... Fails
Ubuntu 16+ ............................. Fails
Manjaro 15+ ............................ Works fine 
Fedora 23+ ............................. Works fine
Peppermint Linux 7+ .................... Fails
GeckoLinux Static 422+ ................. Works fine
Chapeau Linux 24+ ...................... Works fine
PCLinuxOS 2016+ ........................ Works fine

As I say, the pattern is pretty obvious and I suspect the problem is that the gcc versioning tricks I had to pull to get 12cR1 to compile properly on any Ubuntu-based distro back in January are now the cause of woes for 12cR2. The failure always manifests itself in the following manner:

There’s no recovering from that as yet, but I hope to get it sorted within the week.

On the other hand, for any distro listed as working fine in the above list, you can expect the usual plain sailing:

That’s specifically Oracle 12.2.0.1 running on GeckoLinux, which is a spin of openSUSE Tumbleweed, but you get the same outcome for all non-Ubuntu distros.

Whilst testing all this, I discovered a couple of distros which had incremented their version strings since January (Manjaro, for instance, now reports itself as version ’17.something’, so the part of Atlas where it checked for version strings containing the numbers 15 or 16 obviously needed updating). Those sorts of versioning updates are now also included in Atlas 1.2.

There is very little updating of the Atlas doco to do, happily. For a start, you will obtain the new Atlas version just by running exactly the same wget command as was previously documented: the URL alias simply points to the latest version, but the URL itself doesn’t change.

When you install Oracle 12cR2 onto any of these non-standard distros (except the RHCSL ones, of course), you will get this dire-looking warning:

It’s better than the 12cR1 equivalent, which was to say ‘your system is inadequate’! Anyway, for all the distros for which Atlas works at all, it’s perfectly OK to say ‘yes, I want to continue’. The installation will succeed anyway.

Have fun… and wish me luck whilst battling with Ubuntu later this week 🙂

Atlas, Ubuntu 17 and 12cR1

As I mentioned last post, one major issue that has arisen since I left Australia is this: does Atlas run on the freshly-released Ubuntu 17.04 to make Oracle 12c Release 1 (12.1.0.2) installations a piece of cake? It was working fine on 16.04 and 16.10; but would things break with the fresh 17.04 release?

Here’s the answer:

To be fair, I had to alter the Atlas script in one tiny respect: it originally tested for the existence of ’16’ as one component of the distro’s version string. That was obviously a bit restrictive! I’ve now added ’17’ as a test, too… and that means Atlas’s version bumps to 1.1.

You don’t need to do anything different than was originally documented, though: the ‘wget http://bit.do/dizatlas -O atlas.sh‘ instruction works as it always did. It’s just that it now downloads the newer Atlas script instead of the original.

Catch Up

Well, it’s been a rather longer break than I had expected, but I now found myself living in my new 1930s house in sunny Nottingham. The sale finally completed on March 24th; I moved in on April 1st; the furniture from Australia doesn’t get here until early June. In the meantime, I have one sofa bed, 2 plates, 2 cups, 3 pairs of knives and forks and a kettle to live with. A comfortable transition it is not!

But I have proper Internet (50Mb/sec seems like luxury to me, anyway) and the cats arrived safely from Down Under just in time for Easter. They seem to have survived the journey without mishap and don’t appear to be too put out about it. Finding an English cat food they actually like is taking time and many trips to different supermarkets, however!

Short version: private life is still a bit on-hold and will be until at least June, after which we can think of renovating the place properly and turning it into the Art Deco palace we think it could be.

But back to techie stuff: there are two major items of interest that require some catching up, I think. The first is the fact that Ubuntu 17.04 was released on 13th April. Does Atlas work with that as it did for 16.10?

Secondly, and much more substantially: does Atlas work with the new Oracle 12c Release 2 version, for any or all of the distros that it was working with for 12cR1?

This being Day 2 of having a functioning Internet, and all my servers still in a cargo ship’s container somewhere between Sydney and Suez, it’s going to take a while before I can definitively address these issues. But I am at least back on the job… whenever the cats will get off my keyboard, at least.