Oracle Database and Grid Patch versioning from 12.2 * *Intro to RU and RUR**

So oracle has announced to discontinue terms like PSU,Patch Set and Bundle Patch  for *Nix variants from 12.2 release.

“As of July, 2017, the legacy terms 'Patchset', 'Patchset Update', and "Database Bundle Patch' are not used for 12.2.0.2 database software and subsequent feature releases”

Now these are replaced with RU and RUR ,we can say.But not exactly a replacements

So what is RU and RUR Terms

RU  referred to Release UPDATES  (UPGRADES)

RUR referred to Release Update REVISIONS (REVISIONS)

 

To support both security-related fixes and high-priority non-security fixes to each feature release, quarterly Release Updates (Updates) are being provided each January, April, July and October. Oracle's quarterly Updates contain fixes for the bugs that customers are most likely to encounter:

• Query optimizer bug fixes, which were not allowed in PSU's and BP's from earlier releases are included disabled by default in the Updates.
• Updates include fixes for security vulnerabilities.
• Updates go through extensive testing at Oracle, covering functional, stress, performance, and destructive testing scenarios.
• Applying Updates in a timely manner reduces the likelihood of rediscovery of known issues.
• Updates can be installed with zero down time via RAC rolling

 

Now let we dig into RU and RUR’s

Below mentioned is RU and RUR’s version release for 19c DB/GRID .

So we can say RU will be released on every Querter with upto 2 revisions for RUR maximum.
 

 

New functionalities for a release will no longer be published as Patch Sets. PSs are substituted by Release Updates (RUs). Also, Patch Set Updates are substituted by Release Update Revisions (RURs). Both will be published in a quarterly manner.

If we download patch for below example then we can see numbering diff as below .

For 19.8

RU => Oracle® Database Patch 31305339 - GI Release Update 19.8.0.0.200714

RUR => Oracle® Database Patch 31719890 - GI Release Update Revision 19.8.1.0.201020

 

Database version 12.1 and 11.2 will continue to use the legacy PSU/BP process and version numbering systems.
 

Each Update is followed by up to two separate Revisions for the six months after the Update is released. For example, Release.Update.1 and Release.Update.2, where "1" and "2" represent the Revision iterations.

Oracle recommends that customers stay current with Updates. By doing this they minimize the chance of encountering known bugs and security vulnerabilities. Staying current with Updates reduces the likelihood of requiring separate interim one-off patches which lead to unique software baselines and potential for ongoing costly patch maintenance.

 

NUBERING SYSTEM FOR PATCH

Below is updated Numbering System for RU and RUR

 

 

Can we switch b/w RU and RUR

Below method can be used for switching

 

 

SOME IMPORTANT TIP’S FOR RU and RUR’s as per ORACLE DOC.

New Feature Inclusion

• RU will always contains new feature
• RUR will not contains any new feature.

Number of Revisions

1 RU will be having maximum 2 RUR .It means Any UPDATE will be extended only for 6 months

Installation of RUR without RU

We can install RUR without existing RU

UPDATES are Cumulative

The July Release Update patch includes the contents of all previously Release Updates

How RUR helps RU

Revisions are an extension (a revision) to a specific Update and contain additional security and regression fixes.  They can extend the Update’s lifetime up to two quarters by allowing the database to stay up-to-date on security fixes.

From 12.2 what changed

For 12.2.0.1 in July 2017, Oracle released a Database Update, a Grid Infrastructure Update, and an OJVM Update. 
 

IMPORTANT DOCS

RAC Rolling Install Process for the (OJVM PSU/RU) Patches (Doc ID 2217053.1)
Release Update Introduction and FAQ (Doc ID 2285040.1)
12.2 Updates and Revisions Patching Path (Doc ID 2365470.1)
Release Schedule of Current Database Releases (Doc ID 742060.1)
Assistant: Download Reference for Oracle Database/GI Update, Revision, PSU, SPU(CPU), Bundle Patches, Patchsets and Base Releases (Doc ID 2118136.2)