Loss Of Proxy Service after 12.2 required adjustment of publishers (use port 11000) and to temporarily use jdk 1.7 (not 1.6)
(Doc ID 1666609.1)
Last updated on OCTOBER 01, 2019
Applies to:Enterprise Manager Ops Center - Version 12.2 and later
Information in this document applies to any platform.
Ops Center 12cR2, trying to patch Proxy and Enterprise controller via EC, only attempted on the Proxy server thus far but each time the deployment plan has failed while waiting for the Alternate Boot environment to come back online. The proxy controller and all it's managed services then show a red ? and are un-manageable through the EC.
Then tried steps in doc:
How to Avoid Running Ops Center Proxy Controllers with Java SE Runtime Environment (JRE) 6u71 b12 through 6u71 b31. (Doc ID 1637079.1)
But ran into an issue when trying the steps, see steps and issue below.
1. Create ABE and patch ABE to latest available Solaris 11.1
2. Boot into new ABE
3. Stop the proxy service as were now on the wroing version of java, as per the steps provided by yourself.
4. Attempt to apply "pkg change-facet \
Issue: Step 4 fails as the proxy server can no-longer access the pkg repositories, as this is a remote proxy it's pkg publishers are set (by default installation) to point to itself.
This means with the Agent stopped it can't access the solaris (or any other) package repositories and the command fails and the Agent needs to be stopped to appy the fix!
I tried to change the publisher to point to the EC as the pkg repository but neither https or http would work.
So I've rebooted back to the original boot environment and await your suggestions as to how we get round this one.
Ops Center 12cR2
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