Skip to main content

Understanding the New Oracle Database Release and Patching Model

If you have been paying attention to Oracle database releases in the past few years, you will recognize the release numbering has changed. In the past, Oracle had release one and two but now they have changed to yearly release numbers and full releases each year. These changes started in 2018 that's why we have release 18c,  19c coming out this year and then next year will be release 20 afterwards 21 and so on. The good news here for us DBAs is that the is No "FIRST" and "SECOND" releases anymore! since it is a yearly and full release there is no patchset anymore to apply, which will definitely save us the headache about which release to go live on (first or second).


Release Families

  • The 18c and 19c releases are part of the Database 12.2 "Family" for Lifetime Support as if they were the 12.2.0.2 and 12.2.0.3 patch sets.
  • Patching end date for Oracle Database 12.2.0.1 will be determined once Oracle 18c is available on premises.

Support for Annual Releases

  • Annual releases get a minimum of 2 years patching after the succeeding release is available on all enterprise (non-Engineered Systems) platforms.
  • Similar to what patch sets received under the previous release model

Long-Term Support Release

  • The final release in a family will get long term support.
  • Please check MOS Note 742060.1 for details


Release Numbering and Patching

Oracle has changed to a 3 Number Format { Year.Update.Revision } i.e 18.1.0 is year -> 2018, update -> 1 and revision -> 0. Annual release is like a patchset.

Let's take a look at patching before Oracle Database 12.2:

Oracle provided two types of patches: Patch Set Updates(PSUs) and Bundle Patches (BPs).


Now take a look at patching since Oracle Database 12.2:

Oracle has now changed to Updates (RU) and Revisions (RUR)


NB!!

  • No PSUs anymore.
  • Version number now reflects patch level.
  • A Release Update or Revision is only a patch, not a database upgrade.



Upgrading Directly to Oracle 18c:



Important Notes



Comments

Post a Comment

Popular posts from this blog

Oracle Database 19c Step by Step Installation On Oracle Linux 7.6

This post describes the installation of Oracle Database 19c 64-bit on Oracle Linux 7.6  x86-64 bit. The Linux server needs a minimum of 3G swap and secure Linux set to permissive. An example of this type of Linux installation can be seen here . Download Software Download the Oracle software from oracle edelivery . Oracle Installation Prerequisites Automatic Setup Use the "oracle-database-preinstall-19c" package to perform all your prerequisite setup. # yum install -y oracle-database-preinstall-19c If you are using RHEL7 or CentOS7, you can pick up the PRM from the OL7 repository and install it. It will pull the dependencies from your normal repositories. # yum install -y https://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/getPackage/oracle-database-preinstall-19c-1.0-1.el7.x86_64.rpm Hosts File Set a fully qualified name for the server in the "/etc/hosts" file. < IP-address > < fully-qualified-machine-name > < machin...
9 comments
Read more

How to Delete Old Trace & Dump files with ADRCI

The ADRCI command interpreter has multiple features:- Create a package with incident or problem information for Oracle Support Analyze diagnostic data within the Automatic Diagnostic Repository (ADR) Run health checks In this post, we'll be concentrating on deleting the old diagnostic files with ADRCI. Set your environment and run the ADRCI utility: $ adrci Use the following command to list the ADR homes: adrci> show home ADR Homes: diag/rdbms/db11g/DB11G diag/tnslsnr/sol10/listener Choose the ADR home from the list above: adrci> set home diag/rdbms/db11g/DB11G Check the current retention policy: adrci> show control Check the following columns in the output: LONGP_POLICY:- It is set to 365 days by default. It is responsible for Incidents and Health Monitor warnings. SHORTP_POLICY:- It is set to 30 days by default. It manages the trace and core dump files. Use the following commands to change the retention policy: Specify the time in hours: 10 Days = 240 ...
1 comment
Read more

Oracle Database 12C Error Codes, Solutions and Suggestions from ORA-19700 to ORA-20000

Oracle 12C Error Codes, Solutions and Suggestions from ORA 19700 to ORA 20000 ORA-19700: device type exceeds maximum length of string Cause:  The device type indicated is invalid. Action:  Supply a correct device type and retry the allocation. ORA-19701: device name exceeds maximum length of  string Cause:  The device name indicated is invalid. Action:  Supply a correct device name and retry the allocation. ORA-19702: device parameter exceeds maximum length of  string ORA-19703: device command string exceeds maximum length of  string Cause:  The device command string exceeds maximum length. Action:  Correct the command and retry the operation. ORA-19704: file name exceeds maximum length of  string Cause:  The specified file name, which was a parameter to a copy, backup, or restore operation, exceeds the maximum file name length for this operating system. Action:  Retry the operation with a s...
Post a Comment
Read more