How to upgrade agent from OEM GUI after OMS upgrade

Updated: Apr 30





In the previous post we saw how to upgrade OMS from 13.2 to 13.4 version .(Click Here)


Once OMS is upgraded we have to upgrade the agents running in the servers which are monitored by OEM .


This whole process of upgrading the agent is done from OEM console after OMS up gradation is done.


1- After OMS upgrade is done,now logged in to EM console .


Click on I Accept


2- Now the EM console will appear .Navigate to the below path .

SettingManage Cloud ControlUpgrade Agents




3- In the upgrade console we will see options to add all the agents that needs to be upgraded .




4- Once we click on the add option it will take us to the console to add the agents those have to be upgraded .Click on All .



5- Select one to be upgraded .Once that is done we will do the rest of the agents .




If you do not have "root" access or sudo configured to allow you to run the root scripts, click the "OK" on the warning message. The root scripts can be run after the installation completes




6-Agent upgrade may fail at "Starting Management Agent blackout" step with below error :



java.lang.Throwable: java.security.PrivilegedActionException: oracle.sysman.emSDK.agent.comm.exception.VerifyConnectionException:
 unable to connect to http server at https://<>:3872/emd/main/.
 [handshake has no peer]java.lang.Throwable: java.security.PrivilegedActionException: oracle.sysman.emSDK.agent.comm.exception.
VerifyConnectionException: unable to connect to http server at https://<>:3872/emd/main/. [handshake has no peer]

The issue occurs when trying to upgrade the 13.2 agent that isn't patched with a Bundle Patch 13.2.0.0.170331 or later.

The latest Bundle Patch on the agent disables the weak cipher. Since the agent was not patched with the latest bundle, the weak cipher is not compatible with the 13.4 OMS.

An internal bug has been logged for this issue.


This is a known issue and can be resolved by following MOS notes

 13.4: Upgrading 13.2 Agents to 13.4 Fails While Creating Blackout With Error: java.lang.Throwable: java.security.PrivilegedActionException: oracle.sysman.emSDK.agent.comm.exception.VerifyConnectionException: unable to connect to http server (Doc ID 2641816.1)

7- Once the issue is resolved we can restart the Agent upgrade process



This completes the upgrade process of EM agent from OEM console .

8- As we had mentioned in step 5 ,we have to run root script manually in the server where agent is running .


path is <New_Agent_home>/root.sh


9-Once root script is run now we can check the status of agent .

cd <New_Agent_home>/bin

./emctl status agent


This way we will repeat the same steps for all other agents .


Happy Learning :)

567 views0 comments

Recent Posts

See All

#oracle #ASM #controlfile #multiplexing #oracle19c It is a best practice for any database to have controlfile as well as redolog file to be multiplexed . This helps during any disk failure to keep one