X

Best Practices, tips and news for managing Oracle’s Engineered Systems for both on-premise and cloud.

Don't get bit by a newly discovered bug in EM 13c DR environments using alias hostnames

Do you have a 13c EM environment that is setup for disaster recovery using alias hostnames for the OMS servers?  If so, you need to know about an issue that exists when trying to do tasks such as provisioning, staging of directives, etc.  This issue occurs because certain tasks in EM require the target agent to communicate back to the central agent running on the OMS server.  To do this, the target agent must be able to resolve the hostname of the central agent in which it is trying to request a file transfer. 

If the OMS server is installed under an alias name which is configured via the /etc/host file on that server, then the target agent will not be able to resolve the hostname of the server where that central agent is running and the file transfer will fail.  This will stop any provisioning tasks that use this agent to agent file transfer method causing them to fail.  There is however an identified solution to this problem which is documented in the following My Oracle Support note:

  • Agent to agent peer file transfer in provisioning, patching fails contacting central agent in EM HA/DR environment with alias hostnames (Doc ID 2254095.1). 

If your EM environment is configured for DR in this way, make sure you read through this MOS note to see if you are impacted and if so, follow the simple steps to prevent these agent file transfer issues.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha