I applied some of the 22.214.171.124 plugin patches to our Cloud Control installation today. We already have Cloud Control 126.96.36.199 installed, so this was just a case of updating the plugins.
Here’s a quick overview of what I did.
- Backup up everything! Database and file system.
- Setup > Extensibility > Self Update
- Download the latest versions of the plugins. The minimum you can really get away with is “Oracle Database 188.8.131.52″, “Oracle Cloud Framework 184.108.40.206″ and “Oracle Fusion Middleware 220.127.116.11″. The Cloud Framework plugin is a dependency for the FWM plugin. Obviously, grab the extra plugins if you need them…
- Setup > Extensibility > Plugins
- Do a “Deploy On > Management Server” for the plugins you’ve downloaded. These require OMS downtime, so you will be monitoring progress using “./emctl status oms -details” from the “$OMS_HOME/bin” directory.
- Wait until it is all running again.
- Do a “Deploy On > Management Agent” for the DB and FMW plugins on just the cloud control server. I wanted to know it was all fine on this server before pushing out the updates to the agents on the monitored hosts.
- Convince yourself nothing weird is happening.
- Do a “Deploy On > Management Agent” for the DB plugin on any monitored database severs. Where possible I did Dev environments in one pass. Test environments in a second pass, then Prod environments.
- Do a “Deploy On > Management Agent” for the FMW plugin on any monitored WebLogic severs. Once again, Dev, Test, Prod.
The plugin deploys to the OMS are a bit slow, but the deploys to the agents are pretty quick. Numbers will vary depending on your kit.
I much prefer the plugin patches to the main Cloud Control OMS and Agent patches as we (the DBAs) don’t have root or sudo access on the servers, so when we do the full-on patches we end up swamping the sysadmins with requests to run “root.sh” scripts. We don’t have to do that for the plugin patches.