Securing Grid Control Agent Fails with 'The OMS is not set up for Enterprise Manager Security' Error
(Doc ID 444901.1)
Last updated on FEBRUARY 19, 2019
Applies to:
Enterprise Manager Base Platform - Version 10.2.0.1 to 11.1.0.1 [Release 10.2 to 11.1]Information in this document applies to any platform.
Symptoms
Trying to secure Grid Agent with the OMS fails with the following error:
emctl secure agent
..
Securing agent... Started.
Requesting an HTTPS Upload URL from the OMS... Failed.
The OMS is not set up for Enterprise Manager Security
- For 10.2 Agent, the <AGENT_HOME>/sysman/log/secure.log shows:
2009-08-08 10:14:28,703 [main] ERROR agent.SecureAgentCmd secureAgent.228 - The OMS is not set up for Enterprise Manager Security.
2009-08-08 10:14:28,710 [main] ERROR agent.SecureAgentCmd main.207 - 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:229)
at oracle.sysman.emctl.secure.agent.SecureAgentCmd.main(SecureAgentCmd.java:200)
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Starting agent ............................ started.
- For a 11.1 Agent, the <AGENT_HOME>/sysman/log/secure.log would be:
- But, the OMS has been secured correctly and the following commands confirm the same:
emctl secure status oms =====> (for OMS versions < 10.2.0.4)
emctl status oms -secure =====> (for 10.2.0.4 and 10.2.0.5 OMS)
emctl status oms -details =====> (for 11.1 OMS)
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Console Server Host : omsmachine.domain
HTTP Console Port : 7788
HTTPS Console Port : 7799
HTTP Upload Port : 4889
HTTPS Upload Port : 4900
OMS is not configured with SLB or virtual hostname
Agent Upload is unlocked.
OMS Console is unlocked.
Active CA ID: 1
- The Agent is able to upload fine to the OMS in the unsecure (http) mode.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |