OEM 13.4 | Fleet Maintenance Patching Best Practices | Achieving Database Patching Success- Overview

#OracleF1 #OEM134 #Fleet_Patching

In this video discussed all about Oracle Enterprise Manager (OEM) Fleet Maintenance Patching and Provisioning Oracle Databases.

Introduction:

Oracle Enterprise Manager’s Fleet Maintenance feature to effectively and proactively patch its Oracle Database environment to address critical vulnerabilities and maintain version currently.

Various Approaches for Patching:

“One of the best ways to ensure secure Oracle security is to implement Critical Patch Updates (CPUs) as they come out, along with any applicable OS patches that will not interfere with system operations. Therefore, using the most recent Oracle database software, along with all applicable patches can help limit the possibilities for vulnerabilities in the software. The installation version and/or patches applied during setup should be established according to the needs of the organization. Ensure you are using a release that is covered by a level of support that includes the generation of Critical Patch Updates.”

Patching is extremely necessary to avoid security breaches. It is also advantageous because it keeps your organization up-to-date with the latest Oracle software. Oracle typically support versions for five years, and a new version is released every year. New versions may necessitate an upgrade. While patching can be applied in a variety of ways, the Fleet Maintenance feature proved to be the best option for all oracle customers.

Each approach is briefly explained below:

OPatch: This is the only offering that does not have some licensing or cost associated with it. It is in place, meaning it requires less storage than out of place options. All databases in the Home must be patched together. Error recovery and rollback are challenging with this approach.

Multi-Tenancy: This out of place option may require double the memory resources. Essentially, it involves unplugging from the old and plugging into the updated or patched container database. A Multi-Tenant License is required.

Fleet Patching and Provisioning (formerly Rapid Home Provisioning-rhpserver): This is out of place patching that utilizes gold image deployment and a quick switch from the current home to the new patch code set. There is a minimal outage window. A Lifecycle License is required.

EM Fleet Maintenance: This is out of place patching that utilizes gold image deployment and a quick switch from the current home to the new patch code set. Version 1 is Switch. Version 2 is DB software maintenance. There is a minimal outage window. It utilizes EM’s deployment job system. This approach is scalable and requires a Lifecycle License.

Cloud DBaaS: Cloud Provider applies patches.

Hope this helps!

Cheers!
Ramesh.

Follow Me On: