How to Avoid Running Ops Center Proxy Controllers with Java SE Runtime Environment (JRE) 6u71 b12 through 6u71 b31.
Last updated on OCTOBER 14, 2016
Applies to:Enterprise Manager Ops Center - Version 12c (12.1) and later
Information in this document applies to any platform.
This document outlines How to Avoid Running Ops Center Proxy Controllers with Java SE Runtime Environment (JRE) 6u71 b12 through 6u71 b31.
Also see: Service Alert <Document:1642727.1> "Ops Center Proxy Controllers for Solaris and Linux may Freeze due to Issues with Java Development Kit 6 Update 71" for Java BugID JDK-8030956 for JDK Enterprise Manager Ops Center.
If there is a resolution for your OS and version in 1642727.N, then use that resolution instead of the workaround procedures in this "How to" document.
IMPORTANT: Do not upgrade to Solaris 18.104.22.168.0 or 22.214.171.124.0 or to Java 6 version 1.6.0_71 (builds 1.6.0_71-b12 through 1.6.0_71_b31) until the Proxy Controller (PC) has been disabled and you have read these instructions.
Avoid running any PC with the problematic JDK/JRE versions, and always stop the PC during the JDK downgrade process.
Preventing accidental updating of the Java packages in Solaris 11:
NOTE: The bulk of this how-to is written for already-running Proxy Controllers for an EC that already has a configured MSR. There are inline notes on where to get the Agent Bundles or patches for systems that are being freshly installed.
These instructions must FIRST be completed on the Oracle Ops Center Enterprise Controller (EC) before continuing on to remote (non-colocated) Proxy Controller systems, and to not-yet-configured Proxy Controller systems.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms