Upgrading Java on an Oracle Enterprise Manager Ops Center Agent Controller to versions Java 6u101, 7u85 and 8u51 or later breaks the communication between the Agent Controller and it's corresponding Proxy Controller.
(Doc ID 2036973.1)
Last updated on MARCH 19, 2018
Applies to:Enterprise Manager Ops Center - Version 11g to 12cR3 (12.3) [Release 11.0 to 12.0]
Oracle Enterprise Linux 4.0
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
This document complements the Sun Alert created on 21st of August 2015
Document ID 2046582.1 "Java 6u101, 7u85 and 8u51 and Later Releases Break Enterprise Manager Ops Center Agent Controller to Proxy Communication"
The assets with Java upgraded to the versions mentioned under 'Occurrence' section will show a red question mark against them under the Assets sections of the Navigation pane on the Browser User Interface.
There will be an alert in the 'Message Center' section, with the Alert Source as the hostname of the unreachable Agent Controller, saying 'The asset can no longer be reached'.
The problem appears after you have upgraded to latest java version some of the components.
Note that the java upgrade could be done because of an OS patching (going to latest Solaris CPU for example)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1) How to fix the different components depending on the java version|
|2) How to fix the agent when it is on a CDOM running Solaris 10|
|2-1) Upgrade asset to Solaris 11|
|2-2) Upgrade to LDOM 3.2 with patch 151934-02 or higher and update file ldoms.properties|
|2-3) Get Ops Center to use a java version lower than or equal to 6u95, 7u80 or 8u45|
|3) Fix with OCDoctor|
|4) Move to java 7|
|5) Solaris 10 agents running JDK 6...|