Letters from the Past

When I was a good deal younger than I am today, I would stumble bleary-eyed upon my father in the kitchen on Sunday mornings preparing that day’s roast lunch and, as he did so, listening to “the wireless”. Invariably, his choice of radio station was Radio 4 …and on Sunday mornings, equally invariably, Radio 4 would broadcast Alistair Cooke’s Letter from America.

Letter from America ran from 1946 to 2004, and Alistair Cooke’s ‘take’ on American life, delivered in round, warm and comforting tones, was enthralling and entertaining. Most things stopped in the kitchen so we could listen to him without interruption. His tendency to digress as though in ordinary conversation was, at times, infuriating; but his ability to digress in a full circle, as it were, meant that the concluding minute or two would usually wrap up in a satisfying way an intellectual yet genial jaunt through whatever topic had caught his eye that week.

I can’t recommend those broadcasts highly enough for an object lesson in clarity of thought and diction, an ability to express an opinion without rancour, to entertain by telling a tale well. And, praise be, the BBC has finally gotten around to making the entire 58 years’-worth of broadcasts available to anyone with an internet connection.

Can I therefore point you in the direction of the BBC’s new Letter from America archive? I particularly liked his remembrance of FDR and his analysis of Nixon’s response to Watergate. But all deserve listening to. And not just on Sundays.

Solaris Pitfalls

I should have learnt by now: never promise the second of a two-part article before you’ve finished it! Last week, I published an article about installing Solaris 11.1 as a text-based server, promising to pair it with an article about installing Oracle 11gR2 on it which was ‘about 90% done’.

Many hours of head-banging later, however, and the missing 10% turns out to be quite serious:

That is Oracle’s installer declaring ‘success’ whilst also simultaneously announcing that it couldn’t configure Enterprise Manager (which makes it something less than a success in my book!). It is true that the database is all present and correct (and happy to display 14 rows of EMP when asked), but we require a bit more from our installations than that, I think!

The error message hints it might be because the ORACLE_UNQNAME as an environment parameter hasn’t been set… but it has, so that’s a red herring.

It is quite probably something to do with networking, my hosts file and my DNS set up, but if it is, I haven’t worked out precisely what, despite around 30 installation attempts.

I shall continue to plug away at it, but don’t expect that second article in a hurry. Sorry.

OS Baby

On the day Windows 8 is finally released to the public (I used it for a month, quite liked it, but decided Linux remained more fun and thus wiped it last week), I realised that not only is Red Hat Enterprise Linux ten years old, but that I remember struggling for days trying to get Windows 3 to run in 386-enhanced mode on a diskless workstation, some 22 years ago.

Yikes.

It took me a while to realise that if you were using a 80286 chip, you couldn’t actually do 386-enhanced mode. I should have guessed…

This was my favourite wallpaper of the time:

What sophisticates we were back then! :-)

I also have fond memories of the London Borough of Bromley Council, for they ran Xenix …in 1987, one of my first database-using clients. That was my introduction to the tar command and the mysteries of TCP. Ten years later, I spent six weeks wrestling with my HP Vectra:

…trying to get Red Hat 5 printing and dialling the nascent Internet via my 14 kbps modem. The printer, I finally managed. The modem never worked. Ten years later still, I finally persuaded my company to move its databases off Windows and onto RHEL 5 servers. Ah, the circular irony.

However, my first ever professional involvement with an operating system was with MS-DOS 3.1 in 1985, at an accounting firm. I was following the manual (OSes came with manuals back then!) which had a section on the format command. I dutifully typed in the sample command shown (format c:), turned the page and only then saw the warning that this command would destroy your data. I remember trying to hit Ctrl+C to interrupt the format… but discovered that wouldn’t work. Happily, there were only a dozen or so sets of client accounts on it, none of them backed up, all of them production data.

Everyone should be allowed to format a production hard disk once in their lives. Just not twice. That was my shot and, happily, it’s never happened since :-)

Should I mention the many Novell Netware 286 installations? Nah… no point. We only did them because DOS couldn’t handle volume sizes larger than 32MB anyway.

I like operating systems. Can you tell?

A Lean Solaris 11 Server

I’ve just put together a brief guide to installing Solaris 11 in text mode and making it ready for a subsequent installation of Oracle 11g. That basically involves installing a minimum of X-related software and then knowing how to get Solaris-based graphical clients talking to a locally-run X server. The results aren’t always pretty …but they’re functional enough to run things like Oracle Universal Installer or Database Configuration Assistant without too much drama!

I haven’t actually documented that sort of Oracle installation on Solaris yet: but consider it a ‘forthcoming attraction’ (it’s already 90% written, so early next week is looking good!)

Solaris 11 has surprised me a bit: even in text mode, it’s easy to install, mostly painless to configure and (!) attractive to use. I wish other OSes would adopt its default choice of bold, serifed fonts in their terminals, anyway! If you prefer the full-on desktop experience, it can be installed with a slick Gnome desktop that is instantly familiar to any Linux user …and it’s Gnome 2, which is even better!

I virtualized my Solaris box in KVM (Linux’s built-in virtualization tool). It worked well enough, provided I lied upfront and said I was about to run a Unix/FreeBSD box. That stops KVM building the virtual machine with virtio hard disks, a format that Solaris neither supports nor recognises. There were a couple of other KVM-specific virtualization issues that arose during and after O/S installation, too -but those are documented in the main article. Anyway, VirtualBox runs Solaris 11 quite well -but VMware Workstation 9 had “issues” that prevented me from ever getting it working. Nevertheless, most people will be able to virtualize a Solaris server pretty easily, I think.

Give it a whirl, anyway: you may be pleasantly surprised!

Fedora Glitch

One of the consequences of tidying up Gladstone before his retirement has been the discovery that installing 11g Release 2 on Fedora 17 is a variable experience, depending on the Oracle version you’re using. This has revealed a bit of a stuff-up on my part regarding the sort of Oracle installations I do!

To explain: my standard advice when installing 11gR2 on Fedora 17 has been that you should expect to experience a linking error (relating to the $ORACLE_HOME/sysman/lib/ins_emagent.mk makefile). Gladstone knows this ahead of time and therefore writes out a little shell script (in your Desktop directory) which you can run the moment the linking error appears. As soon as it has completed its work, you switch back to the Oracle installer, click Retry …and everything will then complete successfully. A perfect installation in the end, then, with just a minor blip on the way.

However, it turns out that this advice is only true if you are installing Oracle 11.2.0.3!

If you are instead using the 11.2.0.1 version, the advice is wrong …because you will experience a completely different linking error much earlier in the piece. This one relates to the …ctx/lib/ins_ctx.mk makefile …and there’s no fix for it (not one I can work out, anyway). The only thing you can do when this particular error appears is to click ‘continue’ in the Oracle installer. The installer will then carry on linking everything else, bump into the “known” ins_emagent problem as before… and you can worked around that with the fix-up shell script previously described. Overall, you’ll experience two linking errors, only one of which can be fixed. You will therefore complete the installation, but you’ll be left with defective Oracle Text functionality, which may or may not matter to you.

Put it this way, then: if you’ve got paid access to My Oracle Support, you can use the latest version of Oracle and you won’t have an ins_ctx.mk problem. If you’re relying on the freebie downloads from OTN, though, you will.

I should have noticed this much sooner than I did. Trouble is, with access to the latest version of Oracle 11g, I inevitably got into the habit of using it when testing Gladstone, so I never noticed the big difference in the way the two versions behave during installation.

This is particularly bad on my part because, of course, the people most likely to be using Gladstone on non-supported Distros are precisely the people least likely to have access to the higher version. (Home learners, basically).

I should have kept “my audience” in mind, and stuck to working things out on the 11.2.0.1 version only, therefore… which is what I’ll definitely be doing in future. Apologies in the meantime: 11g on Fedora 17 will work, but only with slightly defective Oracle Text functionality and a willingness to accept the first of the two linking errors that result, without trying to fix it.

Gladstone Goodbye

After nearly three years, I’ve decided that it’s time to say goodbye to Gladstone. I hasten to add, I don’t mean that the script itself will be disappearing any time soon: it’s still here, still available for download and isn’t going anywhere.

What I mean, though, is that I won’t be developing it any further.

In the past couple of weeks, I’ve tidied him up and tweaked all sorts of bits and pieces, ensuring that he works for correctly preparing assorted Linux Mint, Debian, Fedora, Sabayon, Ubuntu, Centos, Scientific Linux and Oracle Enterprise Linux distros for running Oracle 10g and 11g. As far as I know, every one works as intended (you may well have to click ‘ignore all’ on the Oracle Universal Installer’s prerequisite checks page, but actually everything under-the-hood is fine). I’ve even made sure it works with the latest Developer build of Ubuntu 12.10, so I can’t make it much more up-to-date than that. There are just a couple of instrumentation changes I want to make, probably by the end of the coming weekend, but other than that, I think he’s “done”.

Gladstone now therefore deserves a ‘code freeze’, because it’s getting harder and harder to make it work for new distros without stuffing it up working with previous ones. What’s more, it’s silly having to make sure he handles Oracle 10g installs when 10g itself is no longer available for download: that particular dead equine has long since been flogged past the point of useful reward. Additionally, trying to handle the imminent release of 12c in that mass of ancient and straggly code is going to take me way beyond where I am comfortable being, I think!

So this weekend will mark the point where gladstone.sh becomes ‘read only’.

I haven’t abandoned attempts to automate the process of preparing a Linux system for running Oracle, however. It’s just that I need something more maintainable, more modular, forgetting about 10g, but capable of doing 12c when it’s finally here.

Watch this space for ‘son of gladstone’, therefore, which will hopefully be along soon enough.