Oracle Database Release Update Introduction and FAQ (document ID 2285040.1)

Overview

Beginning in July, Oracle have transitioned to a more flexible and responsive strategy for the database software R Elease process.  these changes only affect Database and Grid Infrastructure release 12.2 or later. The primary goals of this strategy is twofold:

1. Embrace a less complex software release process

A. Oracle wants to get new features to market every year instead of waiting several years
B. Oracle desires to improve database release quality by reducing the number of software changes released at one time

2. Provide customers with a more flexible-to-both:

A. Efficiently adopt BUG fixes when needed and decrease the need for interim one-offs (like the DB Proactive BP provides F or 12.1.0.2)
B. Efficiently keep current and quarterly Security Updates once their environment becomes stable (like the PSU provides F or 11.2.0.4 and 12.1.0.2)

Note: Since July 2017, Oracle has transitioned to a more flexible and responsive database software publishing process.

To accomplish the goals of this strategy, the following database software changes is being implemented:

Database version 12.1 and 11.2 would continue to use the legacy PSU/BP process and version numbering systems.Note: Database versions 12.1 and 11.2 will continue to use the previous PSU/BP process and version numbering system. Patching changes-release Updates and Release Update revisions

Beginning with the next Database release (originally designated 12.2.0.2) planned for 2018, new feature releases of The DA Tabase product is being provided annually, and patchsets are no longerbeing released.

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

• Query optimizer bug fixes, which were not allowed in PSU's and BP ' s from earlier releases is 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 scenario S.
• Applying Updates in a timely manner reduces the likelihood of rediscovery of known issues.
• The Updates can is installed with the zero down time via RAC rolling.

Note:1. From the next version of 2018 (12.2.0.2), the new feature version of the product will be available and the PSU will no longer be released. 2. Patch updates for new products are also released quarterly. 3. Patches for new products can be installed in the RAC for rolling upgrades without downtime. the update and Revision Strategy replaces the Legacy patchset Update (PSU) and the Legacy Database B Undle Patch (DBBP) for 12.2.0.1 database software and subsequent feature releases. As of July, the legacy terms ' patchset ', ' Patchset Update ', and ' Database Bundle Patch ' is not used for 12.2.0.2 da Tabase software and subsequent feature releases. Note that for Database versions 12.1 and 11.2 Oracle continues to release quarterly PSUs and BPs. Note: The update andRevision policy will replace psu/dbbp,12.1 with 11.2 to continue releasing the PSU and the BP update.

Figure 1:12.2.0.1 Database release-naming Convention for Update/revision

• Release Update-database <Quarter> release Update 12.2.0.1.<build-date>
• Release update revision-database <Quarter> release update Revision 12.2.0.1.<build-date>

Release Version Numbering changes

Beginning in 2018, a new numbering schema for the database software is implemented. Instead of a legacy nomenclature such as 12.2.0.2, a three (3) field format consisting of:Year.Update.Revision is used, s Uch as 18.1.0. This allows clear indication of:

• The feature release designation of the database software (the first field)
• The quarterly Update (the second field)
• The quarterly Revision (the third field)

Note: The naming changes will be represented by a 3-digit number, the 1th digit represents the feature product version, the 2nd digit represents the quarterly update, and the 3rd digit represents the quarterly revision.

Figure 2:release and Update Timeline

--END--

Oracle Database Release Update Introduction and FAQ (document ID 2285040.1)