|Oracle® Enterprise Manager Cloud Control Upgrade Guide
12c Release 1 (188.8.131.52)
To switch over the existing, earlier release of Oracle Management Agents (Management Agent) to the newly deployed Management Agents, so that they can communicate with Enterprise Manager Cloud Control, follow these steps:
Note:Perform these steps in the Enterprise Manager Grid Control console of the earlier release.
Note:If you are upgrading using the 2-system upgrade approach or the 1-system upgrade approach on a different host, then DO NOT switch over the Management Agent (central agent) that was installed with the old Oracle Management Service (OMS).
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Agent Upgrade Steps section, from the table, click Switch Agents.
On the Switch Agents page, in the Provide Inputs section, do the following:
Enter a unique name for the switchover operation you are about to perform. The custom name you enter can be any intuitive name, and need not necessarily be in the same format as the default name.
Note:The operation name you enter here is only a logical name and will be used for saving the details of the operation you are about to perform. After submitting this operation, if you want to track its status, then you can use the operation name.
If you want to switch over the Management Agents for which you had previously performed a readiness check, then click the torch icon against Load Agents from Previous Operations, and select the operation you had submitted for performing the readiness check for those Management Agents, click Go.
Enterprise Manager Grid Control populates the table in the Search Agents section with a list of Management Agents that are associated with the operation you selected.
In the Search Agents section, search and add the Management Agents you want to switch over:
If you specified a switchover operation name as described in Step 4 (a), then search (or add) and select the deployed Management Agents that you want to switch over now. To understand how to search and add Management Agents, see Appendix G.
If you selected an operation name as described in Step 4 (b), then review the Management Agents that are displayed based on the operation you selected.
After you add the Management Agents, select each of them from the Select column.
In the Agent Credentials section, retain the default selection, that is, Use Oracle Home Preferred Credentials, so that the preferred credentials stored in the Management Repository can be used for this job.
Note:Ensure that the preferred credentials were registered with the Enterprise Manager system using the Enterprise Manager Command Line Interface (EM CLI). For more information, see Appendix F.
You can optionally override these preferred credentials. To do so, select Override Oracle Home Preferred Credentials and enter one set of credentials that can be used for all Oracle homes.
Note:Ensure that you use the same credentials that you used for the existing, earlier release of the Management Agent
Points to Keep in Mind
Keep these points in mind:
After you submit the operation, if you see the following error, then first run
root.sh from the old Management Agent home, and then, resubmit this operation.
ERROR: NMO not setuid-root (Unix-only)
If you see the following error, then verify the credentials entered in Step (10).
Local Authentication Failed...Attempt PAM authentication...PAM failed . . .
When the operation is in progress, if a Management Agent being deployed and configured becomes unavailable for some reason, you may see the status Suspended on Event. Once the Management Agent becomes available, the status automatically changes to show the current state, and eventually gets switched over. This is an expected behavior.
In the 2-System upgrade approach, all the old Management Agents you selected are switched over, and the upgraded Management Agents are started so that they can communicate with the upgraded OMS.
If you selected an old Management Agent that was installed with the old OMS, then that Management Agent is switched over but not started, and as a result, it continues to run. This is an expected behavior because in the 2-System upgrade approach, your old OMS coexists with the new OMS for some time, and until the old OMS is decommissioned completely, the old Management Agent that was installed with it must continue to run.
When you are ready to decommission the old OMS, ensure that you manually stop this old Management Agent and start the upgraded (or switched over) Management Agent so that it can start communicating with the new OMS.
In the 1-System upgrade approach, if you missed switching over any Management Agent and upgraded the OMS inadvertently, then you must manually switch over those Management Agents by first stopping the old Management Agents and then starting the new ones:
(a) Stop the old Management Agent home:
$<AGENT_HOME>/bin/emctl stop agent
(b) Start the deployed Oracle Management Agent 12c from its instance home:
$<AGENT_INSTANCE_DIR>/bin/emctl start agent
Even after switching over a Management Agent, if the status shows that it is down, then manually start it:
$<AGENT_INSTANCE_DIR>/bin/emctl start agent
While switching over a deployed Management Agent to the new Enterprise Manager system, the switchover job might fail at the uploadAgent step. If the step fails with that error, then do the following:
On the Management Agent host, run the following command:
cat /dev/null > access_log
From the Management Agent instance home, run the following command and verify if the upload operation succeeds. Repeat this command until the upload operation succeeds.
$<AGENT_INSTANCE_HOME>/bin/emctl upload agent
Once the upload operation succeeds, access the Upgrade Console from your Enterprise Manager Grid Control console, and in the Agent Upgrade Steps section, click Switch Agents.
On the Switch Agents page, select the Management Agent that had the error, and submit the switchover job again.