Charles Wilson (pictured left) was a Scottish physicist in the early part of the 20th Century who invented the first cloud chamber. Particles ionizing the air in his chamber caused ‘vapour trails’ to form and you could thus “see” atomic particle interactions for the first time. It was no small achievement and he won the 1927 Nobel prize in physics for it. He also got a crater on the moon named after him (though a couple of other ‘Wilsons’ are involved there, it has to be said).
For the purposes of this blog, the inventor of the cloud chamber sounds like a good name to use for a new Asquith-framework component server that’s to be used as an Enterprise Manager 12c “Cloud Control” host.
A “Wilson server” has 4GB RAM, ~40GB hard drive and a dual-core CPU. It runs Oracle Database 11gR2, and that database gets used as the repository for an installation of Enterprise Manager 12c Cloud Control Update 3. Once built, you add ‘targets’ to Wilson’s Enterprise Manager (EM) and thus can use it to graphically monitor and control your other Asquith-based servers. You can, for example, use EM to create a Gamow-Dalton Data Guard copy of your original Alpher-Bethe RAC, entirely graphically.
So that’s what Wilson is. How do you build one? Well, you make sure your original Asquith server is built with the new 1.08 version of the Asquith ISO, which is available from the usual place. To upgrade a previously-built Asquith server to version 1.08, simply mount the 1.08 ISO then copy the asquith.ks, rosebery.ks and kickstart.php files over the top of the existing version of each file stored in the /var/www/html directory.
The updated Asquith Server also needs to house copies of the three files which make up the Enterprise Manager 12c Update 3 software stack. You can obtain all three required zip files from OTN. However, you have to re-name the downloads before they can be used. So, whilst you download files called em12103p1_linux64_disk1.zip, em12103p1_linux64_disk2.zip and em12103p1_linux64_disk3.zip you have to rename them, once they’re copied to Asquith’s /var/www/html directory to be:
If you source your download from somewhere other than OTN (say, from edelivery), the download files will have completely different names -but you must still rename them to conform to the names shown above.
You obviously also need your Asquith server to be hosting the Oracle Database software, too. Enterprise Manager software is a new addition to Asquith, not a substitute for any of its previous components.
So, once you’ve got a version 1.08 Asquith server hosting the Database and Enterprise Manager software, you’re ready to build your new Wilson server. You do so by booting it with appropriate CentOS/Scientific Linux/OEL boot media and creating a bootstrap line to initiate a Kickstart build. For Wilson servers, the bootstrap line will contain a new parameter: cloud=y.
If that parameter is present, then the Enterprise Manager software is copied off Asquith onto the new server’s /osource/em directory automatically, as part of the base build process. That’s in addition to the database software, which already gets copied to the /osource/database directory.
So, once your new server build is complete, you just have to:
Log on remotely using ssh -X as oracle
Launch the Oracle database installation procedure with /osource/database/runInstaller
Modify the starter database by running /home/oracle/emprep.sh
Launch the Oracle Enterprise Manager installation procedure with /osource/em/runInstaller
The full procedures to follow will be documented in due course, but the net effect is that it’s relatively painless to create a standalone EM server that can monitor, control and administer all your other Asquith component servers.
Note, finally, that I’ve added a new “speed key” to make building a Wilson server even simpler: sk=5. Specifying that implies your new component server will be called wilson.dizwell.home, have an IP address of 192.168.8.252, will be built using CentOS 6.5 and isn’t going to be running RAC or Data Guard. It will also imply “cloud=y”, so the EM software gets copied across and unpacked.
At its simplest, therefore, you add a dedicated Enterprise Manager server to your Asquith family of servers by using this bootstrap line when you start to build it:
(You can specify any other appropriate “oraver” there, of course: I use 11203 a lot these days, for example).
Finally, I’ll just mention that this feature isn’t coming to Salisbury any time soon. The ethos of Salisbury is command-line management. This is where Asquith and Salisbury really part ways, therefore.
I have spent three days puzzling over this little nasty concerning the Enterprise Manager 12c Cloud Control (Release 3):
No matter how carefully I built my server, no matter what I re-configured, the EM installation would always fail at the point where it tries to create the MDS Schema. If you follow the trail of logs produced during the installation, you come across this:
2013-12-28 11:15:34.190 rcu:Extracting Statement from File Name: '/u01/app/oracle/oms12cr3/oms/rcu/integration/mds/sql/mds_user.sql'Line Number: 30 2013-12-28 11:15:34.190 rcu:Extracted SQL Statement: [CREATE USER &&1 IDENTIFIED BY &&2 DEFAULT TABLESPACE &&3 TEMPORARY TABLESPACE &&4] 2013-12-28 11:15:34.190 rcu:Statement Type: 'DDL Statement' JDBC SQLException - ErrorCode: 922SQLState:42000 Message: ORA-00922: missing or invalid option Error encountered executing SQL statement FileName: '/u01/app/oracle/oms12cr3/oms/rcu/integration/mds/sql/mds_user.sql' LineNumber: '32' SQL Statement: [CREATE USER SYSMAN_MDS IDENTIFIED BY ****** DEFAULT TABLESPACE MGMT_TABLESPACE TEMPORARY TABLESPACE TEMP] java.sql.SQLSyntaxErrorException: ORA-00922: missing or invalid option
So, in a nutshell, creating the MDS schema failed because the Oracle database took exception to this SQL statement:
CREATE USER &&1 IDENTIFIED BY &&2 DEFAULT TABLESPACE &&3 TEMPORARY TABLESPACE &&4
Now all those substitution variables take well-defined values: &&1 in this case is ‘SYSMAN_MDS’, &&3 is ‘MGMT_TABLESPACE’ and &&4 is ‘TEMP’. And knowing what password I suggested during the earlier phases of the installation, I know that &&2 is going to take a value of Oracle1!.
Why that value? Because I remember reading on one of the Enterprise Manager installer screens that the administrator, node manager and MDS passwords needed to be at least 8 characters long, start with a a letter, have at least one numeric and contain at least one special character. Which is, of course, pretty standard fare these days for complex passwords. So “Oracle1!” it was: a capital letter, a numeric, a special character, 8 characters long. What could go wrong?
Well, judging from the ORA-00922 error displayed in that EM installer log, quite a lot! And sure enough, if you take all the known values for all those substitution variables and plug them into a basic SQL statement, you can generate ORA-00922 errors on demand:
SQL> create user sysman_mds identified by Oracle1! 2 default tablespace mgmt_tablespace 3 temporary tablespace temp; create user sysman_mds identified by Oracle1! * ERROR at line 1: ORA-00922: missing or invalid option
The problem, as the precise position of that asterisk makes plain, is the exclamation mark: Oracle doesn’t like special characters much… not unless you wrap them in double quotes. Had that SQL statement read create user sysman_mds identified by “Oracle1!”…, all would have been fine. But quote-less, it fails.
Clearly, this is an Enterprise Manager bug!! If it’s going to demand that you supply a password of sufficient complexity that it must contain a special character, then it damned-well ought to be able to submit it wrapped in quotes when its JDBC process try to submit “create user” statements to the database!!!
Well, maybe. But let’s just read the installer’s actual instructions again, shall we? (Something I only did, as I say, after three days of faffing around with this problem!):
Just focus on that error message at the bottom of the screen again. “Specify Administrator Password: Password must contain at least 8 characters, begin with a letter and include at least one numeric value”.
Er, where is the bit about ‘special characters’? Not there, that’s where. That, it turns out, was a figment of my imagination -no doubt tainted by over-familiarity with Oracle’s “password_verify” function which you can use as a database profile limit to enforce database password complexity checks and which does specify the use of punctuation characters. Clearly, what Oracle deems to be a minimum level of password complexity for its database is not quite the same thing as what it seeks to enforce as password complexity for its Enterprise Manager tool.
In short, I had assumed the need to specify a punctuation or special character in the EM administrative password when, if I’d read the on-screen instructions carefully enough, no such special character is actually needed. Which is particularly unfortunate when the inadvertent use of a special character actually breaks the EM Installer!
So, two lessons here. One, always read the instructions printed on the tin. If it doesn’t demand a special character, don’t assume it does. And Two: Oracle’s EM Installer ought to be able to handle complex passwords and can’t. So that’s a bug in my book.
Oh, and Three: don’t use punctuation characters when specifying your EM 12c Cloud Control administrative password. It breaks Oracle, big- (or bug-) time.
I started the New Year at a new employer, doing RAC and Data Guard configuration/setup and various bits of database development work. I end it with us preparing (finally!) for a disaster recovery test in which we will find out if I am as good as configuring multi-node Data Guard setups as I think I am! First few weeks of the New Year will reveal all…
Meantime, my job’s changed a bit over the course of the year. Day-to-day management of the database infrastructure having been (or about to be) outsourced to a consultancy, I am more focussed than ever on development activities… and these have suddenly taken a turn in the direction of SAP BusinesObjects. Which makes me Universe Designer-in-Chief, trying to master a product I’ve never really used in anger before. Some learning curve! Fun times ahead, methinks.
Lucretia (the cat) has proved as young-at-heart as ever, despite turning 18. She lost a lot of weight at the veterinary ‘hotel’ we put her in whenever we take a holiday. So much so that, this time, I thought we were going to lose her. She literally couldn’t purr right: she’s normally double-bass profundo but could only manage a pathetic sort of high-pitched wheeze on our return. If she’d eaten at all during the fortnight we were on holiday, it would only have been on day 1. But four days after our return, having not touched food no matter how nicely we put it out or varied it, she finally got her mojo back. The purr returned on day 6. And now we’ve been back two weeks, I doubt you’d notice the problem. She’s good for another year or two after all, it seems.
Chandler (the wallaby) still looks as if she’ll be around for years, to, where “around” can mean “eating out of the cat’s bowl” or “watching TV in the lounge” as she deems appropriate. Four other wallabies have persistently attended the back door throughout the year, making us feel very lucky and very happy.
Personally, I spent a lot of the year gearing up for the Benjamin Britten centenary. We got the Royal Mail stamps, then the Royal Mint 50p proof coin, then the full scores of the War Requiem and Gloriana. Then it was a long, long wait for the flight to Blighty, spent for the most part panicking that I’d fall prey to some virus or bug or other. But in the end, I awoke in Aldeburgh on the appointed day with no sniffles and just the merest hint of a chest infection that has subsequently developed into a nice dose of body-wrenching bronchitis. Returning to the Red House (where Britten and his partner Peter Pears lived from the 1950s to the 1970s) for the first time since 1986 was one of those truly memorable, once-in-a-lifetime, experiences.
“Have you ever been here before” asked the guide. “Why yes, actually,” I replied. “In 1986, I came and had a cup of tea and a digestive biscuit with Sir Peter Pears, who’d invited me to discuss the works of Britten”. At which the guides (pleasingly!) expressed suitable amounts of awe and admiration. I didn’t remember the room where he’d handed me the digestive, because they’ve moved everything around, back to the way it was in 1967. But, satisfyingly, the dip in the floor where I embarrassedly tripped over in 1986 was still there, still familiar… though somewhat less embarrassing second-time-around!
I have to say, “Britten Country” (that is, Aldeburgh, Snape, Orford, Thorpeness and their surrounds in east Suffolk) is utterly wonderful (though we were lucky with the weather: typical bright-sun-clear-sky-cool-temperatures November, basically). I’ve dreamt about it ever since returning. If someone would kindly donate about half a million pounds, I’d be buying a house there and moving back almost immediately. It was that good -and much better than I had remembered from my last trip there in 1989. God’s own country, for sure.
I only changed operating systems three times in the year, which is some sort of record (low!) for me. Windows 8 (and 8.1) were good, but uninteresting. Fedora 19 was good, but Gnome Shell is bloody awful, despite copius quanitites of goodwill and patience on my part. And Linux Mint KDE 16 is new and experimental, but I’m enjoying it. No doubt, the story will develop in 2014…
Coming back from Paris a few weeks ago was not the nicest flight I’ve ever had: the incipient chest infection finally took hold, and by the time we started the final leg from Kuala Lumpur, I expect I was that sort of unavoidable, irritating passenger everyone dreads: my cough was persistent, loud and annoying. I end the year on a course of antibiotics as a result, though they don’t seem to be doing an awful lot.
Somewhat more worrying was the perpetual numbness in parts of my assorted limbs on the right-hand side of my body. A CT scan was ordered… and bizarrely tended to suggest I’d suffered a minor stroke at some point. Thus a referral for a more detailed MRI scan, which took place at the start of this week. If you haven’t had an MRI scan, I wouldn’t recommend one! The procedure consists of being inserted a very long way into a very confined space and being told to stay absolutely still for about half an hour (which is much, much harder than it sounds!). They also tell you that ‘the machine will make lots of noises’… and you sort of expect a bit of a hum, whirr and kerphhutt. Actually what you experience, despite ear plugs AND ear defenders, is the most godawful, body-ripping WHOOOOOOOOOORRRRRRRRRRRR-KERPPPPPPPPPPPPPPPPPPHGHGGHHHHHHHT-BOOOM-ditty-BOOOOM-ddiiittty-kerdiddle-kerdiddle-bludge-phhot-quot-kerpling. Repeatedly, incessantly and at a volume I can only imagine that, without ear defenders, would make your eyes bleed.
I’m not surprised to be told that approximately 50% of people who start an MRI scan hit the emergency release button they give you and thus fail to complete it. I was pretty close to hitting ’emergency stop’ myself, but managed to make it through, with gritted teeth.
I am dubious about what passes for much of ‘medical science’ these days: doctors taking a quick look in the back of your throat, making three passes of your chest with a stethescope and then reaching for the day-off-work sick-form pad doesn’t actually count, in my view, as medicine. MRI machines, on the other hand, really are cutting-edge science and definitely count as “proper medicine”… but they really need to do something about how user-unfriendly they’ve made it!
Anyway, I haven’t had the results yet, but the numbness persists. We shall see. I have no symptoms apart from being able to stick needles into parts of my right leg without it hurting, when it probably should. Oh, and the tip of my nose constantly feels cold, too, which is an odd sensation to be sure.
Otherwise, the year has not been at all bad. I’ve enjoyed work and the company of many colleagues, I’ve loved getting back to Cambridge and Aldeburgh, ToH is happy, the cats and wallabies are content, I’ve spent more than I should on music and less than I ought on computer hardware (not something that has happened often in the past decade or so, I can tell you!). My sisters back in England are all well, as are my various nephews and nieces. I turn 50 on January 7th… all-in-all, it’s not been a bad run-up to it.
I shan’t be posting much (if anything) between now and the turn of the New Year, so can I take this opportunity to thank all my readers and correspondents for their continued interest in all things Dizwell… and to wish you all a joyous Christmas and a very happy New Year.
For no particular reason, I decided I really didn’t like Gnome Shell as implemented by Fedora 19. As with previous Fedora installations, I thought I did for a while, but soon came to the realisation that it just gets in the way of doing things efficiently. I didn’t fancy installing MATE (flakey) or Cinnamon (a hack) desktops either.
So I did something I haven’t done for years and years: installed a KDE desktop. Much to my surprise, I really liked it. I’m now wondering what it was about KDE4 desktops in the past that put me off… but I can’t remember. All I can say is that whatever it was, it’s no longer an obstacle. Instead, I find KDE a pleasure to use, highly intuitive and aesthetically pleasing. For anyone transitioning to Linux from Windows, it’s a much more familiar GUI than Gnome Shell is, too.
Not only did I switch to KDE, but I also switched from Fedora to Linux Mint (the release candidate for the KDE spin, version 16, called “Petra” is available now and will eventually upgrade over time to the final release when it’s ready in a couple of weeks’ time). I’ve used Mint before (I’ve even donated money to the project, making it only the second version of Linux I’ve personally paid money for), and I’ve always found it a pleasure: lots of software in the repositories; applications such as Handbrake, Stellarium, VMware Workstation and others… all easy to install; all major multimedia codecs pre-installed from the get-go; and so on. Mint 16 KDE doesn’t disappoint on any of these grounds, and is definitely ‘fit for purpose’.
Getting Oracle installed on it was a bit tough, but I used my existing Gladstone script and tweaked it a bit and all went well in the end:
I may document that more fully… perhaps even release an updated version of Gladstone to automate the various fix-up steps I had to take. But not right away (certainly not while it’s still in release candidate mode, anyway!)
Anyway, in the meantime: Linux Mint 16 “Petra” KDE Release Candidate …recommended.
Whilst I was busy planning my Paris perambulations, Red Hat went and released version 6.5 of their Enterprise Server distro. Oracle swiftly followed …and, even more remarkably, CentOS managed to be almost equally as swift, releasing their 6.5 version on December 1st. Scientific Linux has not yet joined this particular party, but I assume it won’t be long before they do.
I had also assumed Asquith would work unchanged with the new distro -but I hadn’t banked on the clumsy way I originally determined the distro version number which actually meant it all fell into a nasty heap of broken. Happily, it only took a minute or so to work out which bit of my crumbly code was responsible and that’s now been fixed.
Asquith therefore has been bumped to a new 1.07 release, making it entirely compatible with any 6.5 Red Hat-a-like distro (and any future 6.x releases, come to that).
Another feature of this release is that the ‘speedkeys’ parameters have been altered so that they assume the use of version 6.5 of the relevant distro. That is, if you build your RAC nodes by using a bootstrap line that reads something like ks=http://192.168.8.250/kickstart.php?sk=1…, then you’ll be assumed to be using a 6.5 distro and the source OS for the new server will be assumed to reside in a <distro>/65 directory.
If you want to continue using 6.4 or 6.3 versions, of course, you can still spell that out (ks=http://192.168.8.250/kickstart.php?distro=centos&version=63…). You just can’t use speedkeys to do it.
An equivalent update to Salisbury has also just been released.
I haven’t been to Paris since about 1986. I can’t say I’ve missed it much, and this trip has not made me any more enamoured of it. The architecture is certainly impressive, if you like La Belle Epoque, which makes rococo look restrained. Bear in mind that this is a city that has historically more to fear from Hausmann’s bulldozers and the extensive elephant-eating communard population than Frtiz’s bombs or shells (surrendering all the time does wonders for your historical districts). The net result for me, however, is a bunch of frippery-draped buildings scattered over a comparatively tiny area and divorced from much real sense of history.
The revolutionaries did a good job of stripping away centuries of history, such that the handful of true remnants, such as the Sainte-Chapelle, are all the more appreciated because of their rarity.
The English had their Protestant zealots trying much the same thing, of course… but Royal authority was re-stamped early on and the 12 years of English Republicanism was more of an abberation than anything else. Precisely the opposite of French experience since the 17th Century, in other words. I think you can “taste” the result. Elegant it certainly maybe; tasteful… questionable (imho); historically interesting… mostly not, again in my view.
I don’t get the sense that I’m treading on the ground that Rousseau or Descartes would have known, let alone Napoleon. I’m disappointed as a result.
Happily, tomorrow is Eurostar day and a return to the relative sanity of Cambridge!
On the whole, Fedora is a nice operating system. But installing the damn thing is a pain in the butt and makes my eyes bleed. Here’s a typical example of the horrors that await:
I mean, seriously?
They couldn’t manage to align the ‘C’ of “configuration” with the ‘U’ of “user settings”?
They were amused at the idea of putting the ‘U’ of “user settings” so far off to the left of the screen that it practically walks off the set?
They thought a progress bar that appears to disappear off either side of the screen was a good idea?
They broke open the tin of fonts, so that all the fonts above the progress bar are completely different to those underneath it?
They couldn’t consistently find the ‘Bold’ option, so ‘CONFIGURATION’ is and ‘FEDORA 19 INSTALLATION’ isn’t?
They thought spewing all manner of entirely disparate elements all over the screen counted as good design?
It’s possible to go on (at length), but I’ll simply sum up with: what a ghastly, typographically-inept piece of bollocks. The screen screams that if I have a question, “we have answers”. But my question is, “What on Earth were you thinking?”… and I suspect they have no answer to that, other than “we weren’t”.
Shame really. It’s a nice O/S once the hideousness of the installer is forgotten.
My 2-node production RAC had been suffering from ‘checkpoint incomplete’ messages in the alert log for a while, so back at the end of October, I finally got off my bottom and bothered to take a look: only to discover the beast had been created with just 2 logs per thread and each of only 50MB.
My ‘standard, do it without even thinking’ approach to online logs has long been: 4 logs per thread minimum, each at least 500MB in size.
So, this database was under-specc’d by quite a long way. No problem: it is easy enough to alter database add logfile thread 1 ‘/blah/blah/log4a.rdo’ size 500M; several times until the requisite number of logs of the right size has been created. Problem solved.
Now, this 2-node RAC happens to be the Primary database in a Primary-Standby Active Data Guard setup. I did idly wonder whether the creation of the 500MB online logs would automatically happen over on the standby site, especially since we long ago issued the command alter system set standby_file_management=auto, but since “online” logs are never used on a genuinely standby database, it didn’t seem important to check it out one way or another. (I should clarify that redo generated by a primary is shipped to an Active Data Guard standby by LGWR and stored in standby redo logs, from where they are read by the managed recovery process, and out of which archived redo logs are thus generated. So standby logs are definitely used at an active data guard standby database, but not the “online” logs… they are there for when disaster strikes and the standby needs to become the new primary).
So, anyway: long story short, I increased the size of the primary’s online logs and didn’t bother to check what had happened over on the standby, Redo continued to flow from the primary to the standby, and a check of the latency of redo transmission showed that all was well (the standby never lagged the primary by more than 12 seconds). All’s well that ends well, I guess.
Except that, one day, for no real reason, I did this:
SQL> archive log list Database log mode Archive Mode Automatic archival Enabled Archive destination +FRA Oldest online log sequence 23445 Next log sequence to archive 23448 Current log sequence 23448
That’s on the primary node 1. And just for the hell of it, I did the same thing on the standby node 1:
SQL> archive log list Database log mode Archive Mode Automatic archival Enabled Archive destination +FRA Oldest online log sequence 23244 Next log sequence to archive 0 Current log sequence 23245
And that’s an apparent discrepancy of around 200 archive logs! This worried me, so I checked the alert log of the standby:
Thu Nov 07 11:39:23 2013 RFS: Selected log 10 for thread 1 sequence 23448 dbid -2003148368 branch 798942256 Thu Nov 07 11:39:23 2013 Media Recovery Waiting for thread 1 sequence 23448 (in transit) Recovery of Online Redo Log: Thread 1 Group 10 Seq 23448 Reading mem 0
…which showed that the standby was actually processing redo from time 23448 or so, which is exactly the ‘time’ being displayed by the archive log list command when run on the primary node 1. So the alert log was saying “no discrepancy”, but the SQL*Plus archive log list command was saying “200 logs out of whack!”.
Puzzled, I dug a little deeper:
SQL> select to_char(first_time,'DD-MON-YYYY HH24:MI') 2 from v$archived_log where sequence#=23245 and thread#=1; TO_CHAR(FIRST_TIM ----------------- 25-OCT-2013 10:11
The standby’s response to the archive log list command showed that it thought log 23245 was the last one applied.This query shows that specific log to have been created a couple of weeks ago, on 25th October at 10:11AM. So what happened around then that apparently stalled the increment of the redo log sequence number? Well, here’s primary node 1′s alert log for the relevant time:
Fri Oct 25 10:17:25 2013 alter database add logfile '+DATA/proddb/log1a.rdo' size 500m Completed: alter database add logfile '+DATA/proddb/log1a.rdo' size 500m
…and that’s me resizing the primary’s online redo logs, at about 10:17AM on 25th October!
Personally, I think this is a bug. The standby was always receiving the latest redo, into its standby logs, as designed. Yet the SQL*Plus command was returning incorrect data, apparently flummoxed by the size discrepancy in the online logs between the primary and standby sites.
But whether it’s a bug or not, the fix-up suggested itself: take the standby out of managed recovery mode (alter database recover managed standby database cancel), switch to manual file management (alter system set standby_file_management=manual) and then add new online redo logs of the right size and drop the originals. When all log groups are of 500MB, simply reverse the process: file management becomes auto once more and recovery of the standby is re-commenced. Net result: output from archive log list immediately ‘catches up’ and starts displaying exactly the log sequence numbers that the primary reports.
Anyway, and happily, I don’t generally go around resizing redo logs more than once in the lifetime of a database. Just be aware that SQL*Plus gets a bit upset if you do and neglect to do it equivalently on both sides of your Data Guard setup.
It’s been almost a year since I switched my desktop to Windows 8 (and recently upgraded to 8.1). I don’t have any particular gripes with it: the Metro apps are mostly awful and I avoid them whenever I can. Otherwise, the big tiles on the ‘Start Screen’ work well as application launchers and I haven’t missed the Start menu at all. Frankly, I can’t see what all the fuss has been about… and that’s me and Windows 8.x!
I do, however, have a gripe with my Laptop (Toshiba p870, 16GB RAM, 1.5TB SSHDD). That was upgraded to Windows 8.1, too… and I immediately noticed that my fleet of 6 VMware virtual machines, acting as a 2-node ASM-based RAC replicating to a 2-node ASM-based Active Data Guard RAC, was unstable where previously it had been rock-solid. Instances would spontaneous crash; the physical laptop would keep blanking its screen (despite all the power save and screensaver options telling it to do no such thing); and so on.
I could investigate, I suppose. I’m fairly convinced that it’s just a weird interaction between VMware Workstation and Windows 8 -something that a new update to VMware Workstation will soon sort out. But I’ve decided not to wait that long. It’s the turn of the year (nearly!), after all, and I haven’t changed operating systems for at least 12 months… so you can guess what’s coming.
I had enjoyed running Fedora 18 on that laptop for a few months earlier in the year, so I decided to do a complete wipe of Windows 8.1 and replace it with virgin Fedora 19. The usual gripes with Gnome 3 aside, I was impressed when it detected the wireless networking interface during the initial installation. Stellarium worked flawlessly after a standard installation from the ordinary repositories. Most important, I guess: VirtualBox installed easily and ran my 6 RAC-and-Data Guard Asquith servers without a hitch.
Since it all went so well on the Laptop, I figured I’d try and be consistent. So the Desktop gets it in the neck next. I’ll see how it goes… and whether I am reduced to installing Mate or Cinnamon to rid me of the Gnome Shell horrors or not.
Meanwhile, I have just 7 sleeps until I trek off to Paris and Aldeburgh for a late northern Autumn holiday. I’m looking forward to it a lot, and have been brushing up ma français in the hope that I might be able to order un autre bouteille de vin rouge when the need arises without too much linguistic embarrassment. It’s been over 30 years since I last spoke French meaningfully… this could prove a lapse too long, I fear!
The trip to Aldeburgh will be celebrating Benjamin Britten’s 100th birthday, so that’s going to be pretty special. But I have planned a side-trip to the sites of the Battle of Bosworth. (I say “sites” because no-one is entirely certain where the one true battlefield is situated, although recent studies have found a likely candidate a couple of kilometres from the one all the tourists go to visit. Naturally, I’ll be visiting all of them, just in case!) As a member of the Richard III society, and as one who (along with every other British school child of my generation, I suspect!) was taught ‘The Tudors and Stuarts’ as an article of national faith, to go to the site where Henry VII beat Richard III and began the entire Tudor era of government will be a wonderful experience for me, no matter it being November, 7 degrees Celsius and a chance of snow!