2012/05/02

An only too easy trap...

The few who follow this blog know I don't at all like the way Oracle is slowly forcing customers to use the OCM and direct Oracle support links, for patching and upgrades.

Why?

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 11.2.0.3 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 11.2.0.3 distribution is actually release 11.2.0.1.7 of opatch!

And the April PSU patch for 11.2.0.3 requires which opatch release?

...
...
...

what for it...

...
...
...

opatch 11.2.0.3!

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.

Ah well...

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 11.2.0.3 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.

As if...

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 11.2.0.3!

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.

Capice?

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!

Catchyalata, folks.

6 Comments:

Blogger Joel Garry said...

The city near where I live has some pretty keen art.

words: curail tymee
words: usecat forkeym
words: Iernal withect

Friday, May 04, 2012 6:05:00 am  
Blogger Noons said...

Cool! I love it when city councils decide to give priority to art instead of "more building".

Friday, May 04, 2012 9:14:00 am  
Anonymous John Hurley said...

I like the ( long awaited ) changes to the 11.1 opatch and like you recently put on the 11.2 PSU. I typically start by backing up the current OPatch directory and then start "thinking" about what funky things will happen with latest opatch.

For me in the 11.2 environment I run first the utility to create the ocm response file and then invoke the auto patching and point to the ocm response file.

Just nagging is all and the "do you wish to remain uninformed" stuff ... no big deal really.

I guess one should be able to ask oracle back if they wish to take no actions on security exposures that have been pointed out to them years and years ago eh?

Monday, May 21, 2012 5:21:00 am  
Blogger Noons said...

You got it in one, John. Would be heaps more useful if they actually LISTENED, instead of trying to tell everyone how to run their shop.

Tuesday, May 22, 2012 9:24:00 am  
Anonymous Marco Gralike said...

> Or we'll simply move to DB2 or MSSQL.

MSSQL? Isn't there a tool for this called "MPatch" (I hear "O" people thinking from a far distance)?

Be aware. You might inspire people.

;-)

Thursday, September 13, 2012 8:48:00 am  
Blogger Noons said...

Yeah... Who knows? The way Oracle is going in this state, I wouldn't be surprised if they got "replaced" here and there by even MSSQl.
There is only so much nonsense Oracle can get away with. They were warned - many times - that "let's use the db maintenance fees to pay for the other disasters" was a dumb idea and akin to shooting themselves in the foot.

Kinda like the whole "dba 1.0" dumb thing, really. That was a fantastic concept: "let's deride and disparage the very same professional category who always defended and promoted our products and let's create an 'Ace-award' for those who have never shown any professional commitment to the cash cow".

What a brilliant, long term marketing strategy!
Sometimes I wonder if the brains at the helm haven't been fried...

Saturday, September 15, 2012 10:51:00 pm  

Post a Comment

Links to this post:

Create a Link

<< Home