8.3.6 Overview of Performing Oracle Grid Infrastructure and Oracle Database Updates
The steps for updating Oracle Grid Infrastructure or Oracle Database software depend on the type of software update you are performing.
Updating to a Release Update (RU)
Updates to a new Release Update (RU) may be performed in-place or out-of-place. Both in-place and out-of-place methods support rolling and non-rolling updates.
-
In-place
The update is applied to the current software home using OPatch while the Oracle Grid Infrastructure or Oracle Database software is shutdown on the node being updated.
This is the default method of applying an RU for Oracle Grid Infrastructure or Oracle Database software, as described in the RU README. The steps to apply the RU must be performed on each node.
-
Out-of-place (recommended)
A new software home is prepared and updated while the Oracle Grid Infrastructure and Oracle Database software remains running. Once the new homes are prepared, Oracle Grid Infrastructure and Oracle Database are quickly stopped, switched to the new home, and restarted.
Out-of-place has significant advantage over in-place updates:
- There is less risk because the new home can be prepared while the Oracle Grid Infrastructure and Oracle Database software remains online.
- There is less downtime because switching to the new software home is faster than applying an update in-place.
- Rollback is faster because it is possible to simply switch back to the original software home.
The recommended way to adopt out-of-place updates is to use Fleet Patching and Provisioning (previously called Rapid Home Provisioning), which provides the following advantages:
- Distributes software updates to all nodes in the cluster.
- Orchestrates updates across the cluster in a rolling or non-rolling manner with a single command.
- Provides control over database service relocation to maintain application availability.
Out-of-place software updates are also supported by Oracle Enterprise Manager Cloud Control.
Out-of-place software updates without Fleet Patching and Provisioning or Oracle Enterprise Manager Cloud Control may be accomplished by following My Oracle Support Document 2087150.1.
OJVM Update
The OJVM update is a separate software update for database homes that addresses OJVM security vulnerabilities. It is installed separately from a standard software update. The OJVM update may be installed in a rolling manner under certain situations.
Updating to a New Release
To update to a higher Oracle Grid Infrastructure or Oracle Database release, follow the step-by-step release instructions in My Oracle Support.
Related Topics
- Minimal downtime patching via cloning 12c ORACLE_HOME directories with OPlan (My Oracle Support Doc ID 2087150.1)
- RAC Rolling Install Process for the "Oracle JavaVM Component Database PSU" (OJVM PSU) Patches (My Oracle Support Doc ID 2217053.1)
- 12.2 Grid Infrastructure and Database Upgrade steps for Exadata Database Machine running 11.2.0.3 and later on Oracle Linux (My Oracle Support Doc ID 2111010.1)
- 11.2.0.2, 11.2.0.3, 11.2.0.4 or 12.1.0.1 to 12.1.0.2 Grid Infrastructure and Database Upgrade on Exadata Database Machine running Oracle Linux (My Oracle Support Doc ID 1681467.1)
- Exadata Database Machine 11.2.0.4 Grid Infrastructure and Database Upgrade for 11.2.0.2 BP12 and later (My Oracle Support Doc ID 1565291.1)
- Exadata Database Machine 11.2.0.4 Grid Infrastructure and Database Upgrade for 11.2.0.2 BP11 and earlier (My Oracle Support Doc ID 1555036.1)
Parent topic: Overview of Performing Exadata Software Updates