How to Resolve EM13c [Handshake Has No Peer] Error After Java Upgrade on OMS Server

by | Aug 19, 2025 | Blog, Database, Oracle

How to Resolve EM13c Handshake Has No Peer Error After Java Upgrade on OMS Server

SUMMARY:

The Oracle Enterprise Manager 13c (EM13c) “[handshake has no peer]” error, which occurs after a Java upgrade on the Oracle Management Server (OMS), is an SSL/TLS communication failure that can be resolved by applying a specific Release Update (RU) patch.

  • The root cause of this handshake error is documented under Oracle Bug 33896877 and is fixed in EM13.4 Release Update 20 or EM13.5 Release Update 09.
  • Before applying the patch, you must ensure the WebLogic Admin Server is running and that OMSPatcher and OPatch versions are up-to-date.
  • The resolution process involves stopping the OMS and Agent, applying the appropriate RU patch using omspatcher, and then restarting all services.
  • Applying the recommended WebLogic patch is an optional but highly suggested step to ensure system stability after the primary fix.

If the error persists after applying the patch, upgrading to Oracle Enterprise Manager 13.5 is the recommended next step for its improved TLS handling capabilities.

Table of contents

Introduction

After upgrading Java on the Oracle Management Server, you may encounter failure when testing named credentials in EM13c. The error [handshake has no peer] usually stems from misconfigured or missing certificates in the Java truststore, resulting in SSL/TLS handshake issues. This failure disrupts communication between OMS and monitored targets, affecting jobs, monitoring, and overall system reliability.

EM13c [handshake has no peer] Error Root Cause

EM13c Handshake Has No Peer Error

This issue is documented under Oracle Bug 33896877. It has been resolved in:

EM13.4 Release Update (RU) 20

EM13.5 Release Update (RU) 09

Applying the relevant RU fixes the handshake issue.

Fixing EM13c [handshake has no peer] Error

Prerequisites

  • Ensure the WebLogic Admin Server hosting the OMS is running.
  • Ensure the Management Repository Database and Listener are running.

Required versions:

  • OPatch: 13.9.4.2.5 or later
  • OMSPatcher: 13.9.4.8.0 or later

High-Level Steps Overview

  • Check current versions
  • Set environment variables
  • Backup OMS and Oracle Home
  • Stop OMS and Agent
  • Install or update OMSPatcher and OPatch
  • Analyze and apply RU20
  • Apply WebLogic Patch
  • Confirm OMS and Agent is still running
  • Validate environment

Step-by-Step Instructions

1. Check current status:

OMS_HOME/bin/emctl status oms
OMS_HOME/OPatch/opatch lsinventory

Set environment variables:

export OMS_HOME=/oracle/app/oracle/oem_13.4
export AGENT_HOME=/oracle/app/agent/agent_13.4.0.0.0
export PATH=OMS_HOME/OPatch:PATH

2. Backup Homes

tar -cvf /backup/oms_home_backup.tar OMS_HOME
tar -cvf /backup/oracle_home_backup.tar ORACLE_HOME

3. Install OMSPatcher

cd OMS_HOME
mv OMSPatcher OMSPatcher_old

# Unzip the new OMSPatcher package here
unzip p19999993_134000_Generic.zip

OMS_HOME/OMSPatcher/omspatcher version

Analyze the patch:

cd OMS_HOME/PATCH_STORAGE/35174911
omspatcher apply -analyze

4. Install OPatch

cd OMS_HOME
unzip p28186730_1394210_Generic.zip

Stop OMS and Agent:

AGENT_HOME/bin/emctl stop agent
OMS_HOME/bin/emctl stop oms -all

Install the software using:

OMS_HOME/oracle_common/jdk/bin/java -jar PATCH_HOME/6880880/opatch_generic.jar -silent oracle_home=OMS_HOME

OMS_HOME/OPatch/opatch version

Ensure version is 13.9.4.2.10 or later.

5. Apply RU20 Patch (13.4.0.20)

Prepare:

df -h         # Check space
free -h       # Verify swap

Apply the patch:

omspatcher apply

Verify:

OMS_HOME/OPatch/opatch lsinv | grep applied

cd OMS_HOME/PATCH_STORAGE/30689820
opatch apply

Make sure the WebLogic JDK is set correctly before running OPatch.

7. Confirm OMS and Agent status

OMS_HOME/bin/emctl status oms
AGENT_HOME/bin/emctl status agent

Restart OMS and Agent:

OMS_HOME/bin/emctl start oms
AGENT_HOME/bin/emctl start agent

8. Sync EMCLI (if applicable)

emcli sync

Conclusion

If the [handshake has no peer] error persists even after applying the patch and restarting services, it may indicate a deeper compatibility issue introduced by the Java upgrade. In such cases, upgrading to Oracle Enterprise Manager 13.5 is strongly recommended, as it offers improved TLS handling and enhanced support for updated Java components.

For any questions, please contact us.

Stay ahead of Oracle issues—explore our Oracle error blog collection for expert fixes, tips, and solutions to keep your systems running smoothly.