EM12c EM13c: Securing Agent Fails With Error "The OMS Is Not Set Up For Enterprise Manager Security"

Last updated on SEPTEMBER 16, 2016

Applies to:

Symptoms

Agent deployment to any host or Silent Agent Install on any host fails with below error in:

<agent_home>/cfgtoollogs/agentDeploy/agentDeploy_2016-08-16_06-15-17-AM.log:

ERROR: Agent Configuration Failed SEVERE: Connection details provided as OMS_HOST and EM_UPLOAD_PORT is not active

OR

Trying to secure any existing agent with the OMS fails with error in:

<agent_inst>/sysman/log/secure.log:

2016-08-17 07:48:22,022 [main] INFO agent.SecureAgentCmd openPage.830 - Response Status Code: 200
2016-08-17 07:48:22,023 [main] INFO agent.SecureAgentCmd openPage.838 - RESPONSE_STATUS header: OK
2016-08-17 07:48:22,024 [main] INFO agent.SecureAgentCmd openPage.839 - Response body: -1
2016-08-17 07:48:22,024 [main] INFO agent.SecureAgentCmd getOMSSecurePort.785 - OMS Secure Port: -1
2016-08-17 07:48:22,025 [main] ERROR agent.SecureAgentCmd secureAgent.286 - The OMS is not set up for Enterprise Manager Security.
2016-08-17 07:48:22,026 [main] ERROR agent.SecureAgentCmd main.257 - Failed to secure the Agent:
java.lang.Exception: The OMS is not set up for Enterprise Manager Security.
at oracle.sysman.emctl.secure.agent.SecureAgentCmd.secureAgent(SecureAgentCmd.java:287)
at oracle.sysman.emctl.secure.agent.SecureAgentCmd.main(SecureAgentCmd.java:244)
[17-08-2016 07:48:22] USERINFO ::Securing agent... Failed. 

Changes

Some EM Administrator has deleted the Initial Agent Registration Password which is Persistent and has no expiry date.

Cause