12c: Patching Recommendation Guide for DBaaS Pool(s)
(Doc ID 1625014.1)
Last updated on FEBRUARY 15, 2019
Enterprise Manager for Cloud - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 12.1] Information in this document applies to any platform.
This document is intended to help DBAs plan their patching process when they have either implemented or plan to implement Database as a Service (DBaaS) using Enterprise manager 12c.
Generally patches for Clusterware, Grid Infrastructure and/or the Database are categorized into the following:
Type ‘A’: CPUs, PSUs, Bundle Patches and other Interim (one-off) Patches
Type ‘B’: Patchsets
PSUs are patches that are applied on top of a given patchset release. They contain fixes for known critical issues for that patchset. PSUs are subject to thorough testing and do not include changes that would alter the functionality of the software. With this in mind, PSUs are designed to provide "low risk" and "high value" allowing customers to more easily adopt proactive patching strategies. E.g. <Patch 17735354>: GRID INFRASTRUCTURE PATCH SET UPDATE 188.8.131.52.9 (INCLUDES DB PSU 184.108.40.206.9) Consider the following PSU facts:
Independent PSUs are released on quarterly basis for both Grid Infrastructure and Database.
GI (Grid Infrastructure) PSUs do contain the Database PSU for the corresponding release.
Both GI and Database PSU patches are cumulative.
All PSUs are installed via "opatch" and are *Not* considered an "upgrade".
Database PSUs always contain the CPU for the respective quarter that the PSU is released in. Hence we strongly prefer PSU patching over CPU.
This article applies to Enterprise Manager Cloud Control 12c Release 3 (220.127.116.11)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!