Patch Oracle Exadata Database Machine via Oracle Enterprise Manager
(Doc ID 1265998.1)
Last updated on FEBRUARY 12, 2019
Enterprise Manager Base Platform - Version 220.127.116.11 to 18.104.22.168.0 [Release 11.1 to 12.1] Information in this document applies to any platform.
Oracle releases monthly Exadata database machine recommended bundle patches; these have fixes to both the Grid Infrastructure (GI) and the RAC Oracle Homes. To patch manually the user must execute over 100 steps on a quarter rack Exadata. Also, opatchauto does not provide automation for out-of-place patching of the GI and database Oracle Homes.
Oracle Enterprise Manager provides complete automation to patch the cluster in zero-downtime both in in-place and out-of-place modes. Oracle recommends that customers apply these patches out-of-place.
Oracle Enterprise Manager 12c introduces the Out of Place method. Clones of the existing oracle homes are created, and the patches are applied to the cloned home instead of the original home. Once the cloned home is patched, user can selectively switch the database instances to run from the cloned home. The benefits are:
i. Minimal downtime, just few minutes of downtime incurred during switching over the instances. ii. Flexibility, the instances can be selectively migrated based on the maintenance schedules. iii. Recoverability, in case of any issues the databases can be switched back to the old Oracle Home.
For EM 13c, see the following notes (and links therein)for more advanced options in target patching from Enterprise Manager:
<Note: 2237521.1> ANNOUNCEMENT: Patching the Oracle Database 12.2 using Enterprise Manager Requires the EM DB Plugin 13.2.2 and Fleet Maintenance
<Note 2237886.1> EM 13c, EM 12c: Patching using Fleet Maintenance for SIDB, RAC and SIHA Targets in Enterprise Manager Cloud Control