We use cookies to optimize our website and our service.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
I wish Oracle would make patching as easy as Microsoft. You just run setup.exe and it does the rest. With Oracle patching, even finding out which patches are applicable and how to apply them is an exercise in frustration. Reminds me of the rules of Fizzbin, a fictional card game which captain Kirk played with the bad guys in Star Trek episode A Piece of the Action. The rules were made on the fly by Kirk and were so complex that everybody got confused.
Arun,
you are not the only one giving such feedback. Actually I receive a good bunch of mails per day from people who know how patching works with similar and even worse feedback.
At the moment "we" are working on a more obvious way to show what’s included in whatever PSU or BP – and what’s not.
Furthermore OJVM patching is a huge area where almost nobody seems to understand what has to be done – and what hasn’t.
I don’t want to turn this blog into a "how to patch" as this is really not the area I’m working in. But maybe due to my support background – and of course due to the fact that we highly recommend to patch before you upgrade or migrate – this topics has some sort of sticky-note-flavor to me.
Cheers
Mike
Mike,
I have patched Oracle Databases with PSU+DB and PSU+GI however I’ve never just done client patches. Is there anything different with Patching clients? Are there different Patch sets for clients?
Thanks,
Dave
FYI – The non-exadata non-rac patch readme only has instructions for applying in a GI/RAC environment.
Steve
Dave,
PSUs and BPs are meant for the server only.
For any client software please see the link here:
http://www.oracle.com/technetwork/security-advisory/cpujul2016-2881720.html
Cheers
Mike
@Steve:
I know – the logical structure of the note is broken. But I got too tired in raising this over and over again …
That’s basically why I blogged about "how to apply …" in order to have the information ready to reuse in my environment 😉
Cheers
Mike