An only too easy trap...
It's very simple: our db servers are in an intranet, in a designated set of subnets that will N-E-V-E-R be open to anything past the DMZ. And even then only as the originators and to a known IP address.
This, I stress again, will N-E-V-E-R change!
There have been numerous attempts from external "con-sultants" to change this state of affairs. Under all sorts of argumentation - including the tired old "your dba is an incompetent" - and all have resulted in nothing.
Nuff said? Now, to this blog entry.
As part of our 188.8.131.52 upgrade to our 10.2.0.3 db servers, I have downloaded the April 2012 PSU for Oracle on Aix and tried to install it.
Not because I am terribly fond of the latest-whitest-brightest mantra but because in the list of fixed bugs there are a few that might be relevant to our processes. And I prefer to be pro-active than reactive.
Yes, I DO read the readme files! I don't need some idiotic piece of Oracle software to do it for me.
It's a quaint concept, but it comes with the territory of hiring someone who can actually read and think at the same time. Rather than just push buttons.
So how come I "tried" to install the PSU? Well, you might say that something went amiss.
To put it simply: the opatch program version released with the standard 184.108.40.206 distribution is actually release 220.127.116.11.7 of opatch!
And the April PSU patch for 18.104.22.168 requires which opatch release?
what for it...
Wonders will never cease!...
Unbelievable that in this day and age something so wrong as this can evade the so-called QA of Oracle software releases.
So, after a quick call to Oracle Support I got back the URL to download the correct version of opatch. Yes, I DO know the URL is also embedded in the readme file for the PSU!
How about making it the FIRST paragraph of the pre-requisites section of the readme, mr Oracle?
Narh! Too common sense and easy, isn't it?
Anyways: downloaded and installed opatch following the readme instructions. Which promptly wiped out the existing OPatch directory under $ORACLE_HOME.
One wonders what would have happened to any patches I might have installed in between initial 22.214.171.124 and the PSU, mr Oracle?
Details, Nuno. Details... Why worry about what could have happened?
Besides, the readme for the PSU explains what to do in case that happens and how to recover from it.
Only it's hidden away at the end of the file.
Instead of being RIGHT UP FRONT where it would have been easy to find and useful.
Isn't it mr Oracle?
Ah yes: we need to impress on folks the "need" for Oracle-managed services instead of relying on those pesky dbas that actually check what the heck is going on in their systems, isn't it? So, let's lay down a trap for them.
But, I digress. I was finally able to run the correct opatch for the PSU I was installing.
Only to be greeted with a bunch of questions about how to get my db servers to connect to www.oracle.com! Apparently, THE "new" feature of opatch 126.96.36.199!
When is it gonna dawn on the idiotic marketeers of Oracle that there is simply NO WAY a lot of customers out there will ever authorize their db servers to directly connect to the Internet? Proxy or no proxy?
No! We do NOT want to connect to your "management services"!!!
Nor is that in any way, shape or format desirable or even in scope. As such, kindly STOP THE NONSENSE once and for all!
Here is a hint, mr Oracle: STOP trying to force on us how we should run our data centres!
Or we'll simply move to DB2 or MSSQL. Where we are not told how to setup our computers: it's a lot simpler there and no one is forcing us to do things their way.
Don't say I didn't warn...
Anyways, enough of the Oracle marketing lunacy.
I like this:
This couple just hopped out of the trike and started to exercise right in the middle of the Sydney CBD. After a while, they both hopped back in and kept going. WTH????
One of my cyberfriends has tried the leg position of the guy in the photo. Only to end up with a persistent joint pain! :-)
One sees the weirdest things on top of the Sydney CBD buildings:
All we have to do is look up!