Last updated on NOVEMBER 16, 2016
Applies to:Oracle WebCenter Portal - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
The goal of this document is to better understand the patch strategy for the Oracle Fusion Middleware for the Oracle WebCenter Portal product and how to properly install an Oracle WebCenter Portal one-off patch onto your system.
Feel free to rate or/and add comments onto this note, so we continuously keep improving it and better serve you.
With the -auto flag (recommended)
The Admin Server & NodeManager have to be running for 'opatch -auto' operations.
The Managed Servers may or may not be in a running state.
OPatch will bounce all the local Managed servers (and the servers sharing the Middleware Home) affected by the patch. If the patch affects an application deployed on the Admin server, the Admin server will also be bounced. If the Managed servers are not running, OPatch won't restart the affected Managed servers.
It is users' responsibility to start those servers in order to uptake the patch.
If your patch is certified for use with the -auto option, you will be informed of such in the patch's README file.
So always check the README file for instructions on how to apply the patch and if the patch can be used with the -auto option.
Without the -auto flag
No servers need to be started.
At the end of the patch apply all servers must be (re-)started to uptake the patch.
Oracle Fusion Middleware Patching Guide
2 Patching Oracle Fusion Middleware with Oracle OPatch
Other Useful Information:
Note 1087226.1 - Recommended Patches for Oracle WebCenter Portal 11g
Note 224346.1 - OPatch - Where Can I Find the Latest Version of OPatch?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms