Database Reference
In-Depth Information
Save the patch from MOS to your test dev OS and then use EM to install that saved patch. You can use the
software library to store these patches, as shown in Figure
17-42
.
Figure 17-42.
Offline patches can be stored in the software library
So we know where to store the offline patches, but is the EM patching process itself difficult? Let's see.
Instructions for Offline Patching
Patching an Oracle database has traditionally been done by downloading the patch and running it on the DB using
opatch. EM allows automation of that process, as well as the opportunity to tie in patch selection, downloading, and
implementation to an organization's MOS account. For high-security environments the latter is not recommended,
which is alright, as Oracle has provided the ability to install patches “offline,” i.e., without the need to synchronize and
pass some control to Oracle's MOS facility.
I am not going to document the complete process for offline patching here as it is quite long. In my view it should
be easier to use the offline mode as this is the most secure. It does work though, as I have been through it successfully.
This is an overview of the preparation process required before doing the offline patch:
1.
Create software library location.
2.
Upload the offline patch to that library location (iterate through the metadata files also):
Enterprise
➤
Provisioning and Patching
➤
Saved Patches.
