We have an existing Cloud Control 18.104.22.168 installation with about 40 agent deployments across our enterprise. Having run into many bugs in 22.214.171.124 that are ostensibly fixed in 126.96.36.199, we are planning to upgrade - however it appears that the recommendation is to install a new 188.8.131.52 Cloud Control and migrate agents from the old system to the new.
We have installed the new system, but are looking for an efficient way to migrate the existing agents, as the Oracle docs state that the agent must be removed from the original 184.108.40.206 system prior to adding to the new 220.127.116.11 system. Not sure if Oracle docs are incomplete, as none of the instructions reference using the Cloud to 'Remove Target' on the agent (yet this functionality appears to exist) - I am hoping that given that we are able to deploy an agent through cloud we should also be able to remove it via cloud?
If not, is the only way to remove by using the runInstaller -deinstall in each agent home across our enterprise? If so, the docs are somewhat sparse on which installed products to remove with the graphical installer, should I be removing:
- oracle_sysman_xxxxxx_12_1_0_1_0_discovery_Home0 (and all permutations?)
I strongly recommend that upgrade your 18.104.22.168 to 22.214.171.124 - as opposed to doing a fresh install. Upgrade will preserve you current settings and will avoid the need of redeploy the agents, rediscover the targets, etc.
@sxkumar - thank you, that probably would have eased the transition - unfortunately we wanted to work with a new, more powerful host server and a new folder structure for the repository database (hosted on the same system as OMS) and thus we are not really upgrading so much as reinstalling. I guess I'm just surprised that Cloud provides the capability to install the agent from a central location but no mechanism for uninstalling...
If my understanding is not correct from your posting, drop me an email and we can discuss your requirement further.
1) if you are upgrade your agents from 12.1. to 12.2 then you have to use agent upgrade console to do that and it does an out of place agent upgrade ( you get a new agent home)
To clarify, you don’t have to re-install the agent to upgrade an agent from 12.1 to 12.2. You can argue that out of place upgrade is equivalent to fresh install of 12.2 but as a part of this agent upgrade process we upgrade plug ins, migrate the agent config and other details.
2) If your concern is how to delete the old 12.1 agent home on multiple target host after agent upgrade? Then yes, this an requirement for us to automate this process to clean up the old agent homes while doing an agent upgrade from 12.1. to 12.2. For time being, as I mentioned earlier we detach the old 12.1 agent home from inventory so the only thing you have to do is to remove the old home directories.
3) Are you also trying to migrate your operating system on the OMS or Repository host as a part of this upgrade ?
Also i would like to share the Upgrade ppt with you, that will give you over all steps that are required to upgarde em 126.96.36.199 to 188.8.131.52
To add to this, documented backup and recovery steps can be used to move the OMS and Repository to new hosts.
For recovery of the repository to a new host see
For recovery of the OMS to a new host see