A customer raised this question recently: Why do you need a password to download older patch bundles? The customer wanted to download a PSU from July 2020 on the MyOracle Support (MOS) platform but this wasn’t possible without a password.
Photo by Privecstasy on Unsplash
Why is there an extra password required?
In MOS Note: 888.1 – Master Note for Database Proactive Patch Program we documented the following:
1.4 Policy to obtain older Oracle Database Bundles, Updates & Revisions
Through our review of customer Service Requests (SRs), we find that customers frequently run into issues because they have unknowingly downloaded older database bundles. To help mitigate this going forward, when a customer tries to download bundles, updates (RUs), or revisions (RURs) older than 12 months, they will be redirected to information on newer versions. We will password-protect these older versions to prevent customers from unintentionally downloading them. Customers are still entitled to download these older versions, and can obtain them by logging an SR to request the password. This will also allow us to capture reasons for these requests so that we can formulate corrective actions to improve delivery and uptake of the latest versions.
So you simply need to open an SR and request the password in such cases. But please explain briefly why you need a patch bundle older than 12 months.
A quick check
Let us do a quick check. You find all the download links in MOS Note: 2118136.2 – Assistant: Download Reference. When you check for instance to download the database RU 19.4.0 from July 2019:
Then you will see the following screen:
And here, you will need a password to be able to download the patch bundle. In case you are in this situation, please open an SR.
Further Links and Information
- MOS Note: 888.1 – Master Note for Database Proactive Patch Program
- MOS Note: 2118136.2 – Assistant: Download Reference for Oracle Database/GI Update, Revision, PSU, SPU(CPU), Bundle Patches, Patchsets and Base Releases
- Patching all my environments with the July 2021 Bundle Patches
–Mike
The read me is also requiring a password not sure if this makes sense other than it makes it easy on Oracle.
Hi Sanil,
I agree and I disagree 🙂
Actually, for us it makes some sort of sense as we really don’t want customers to install old RUs. The problem I see in many projects is this crazy “freeze” in February for a project supposed to go live in October. But even in such cases, you’ll be able to access the RU from January. But you won’t be able to fetch the one from July the year before.
I see your point with the README. But the README wouldn’t help you a lot as it describes how to apply the patch – and this doesn’t change usually. You may be more interested in the list of bugs fixed – but this not is accessible without restriction.
Cheers,
Mike
Hi Mike,
but is there a reason why a password is required for the download of the 19.10 RU? The previous versions can be downloaded without a password.
Cheers
Christian
Hi Christian,
is it the 19.10.0 GI RU? Then the reason is that there were some real issues which require one-offs which are all in 19.11.0.
But I wasn’t aware that it got password protected. I thought it had been removed completely.
If it is the database RU, then this is a failure I guess.
Cheers,
Mike
For ISVs that are partner with Oracle, Technical SR have to be bought to have acces to these password. The end result is : More money for Oracle.
Hi Carl,
trust me that this is clearly not the motivation. This decision has been taken by development owners. And as I know everybody involved here, I can ensure you that this decision was not taking into account your case.
Cheers,
Mike
Hello Mike,
One of my customer is applying EBS pre-req patches on their source environment. They have raised a concern that the Apr 2022 DB PSU patch is password protected. Their OS is HPUX & DB version is 12.1.0.2. does this apply to the DB version as well?
Many thanks in advance.
Hi Praveen,
you please (or your customer) must log an SR and check with Oracle Support please. I have heard about this discrepancy between support time frames when a customer has EBS. But I’d hope it has been solved by now.
Cheers,
Mike