Refresh Weblogic Domain Is Failing after DR Switchover - Virtual Hostname Resolution via /etc/hosts
Last updated on SEPTEMBER 14, 2016
Applies to:Enterprise Manager for Fusion Middleware - Version 184.108.40.206.0 to 220.127.116.11.0
Information in this document applies to any platform.
After switching over the Enterprise Manager (EM) from Prod site DR, the Orache HTTP Server (OHS) components are showing as unknown state in EM console which is due to bug 18541657 as OHS does not support virtual hostnames. You may have followed the workaround mentioned in the document: -What is the hostname of Oracle HTTP Server target associated with a domain? (Doc ID 2003890.1).
You have successfully registered and unregistered the OHS component but when trying to run Refresh Weblogic domain it is failing with following error:
java.lang.Exception: java.lang.RuntimeException: java.lang.RuntimeException: java.net.ConnectException t3s://PhysicalHostname.domain:7102: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused; No available router to destination
Note: The Admin server is up and running and there is no issue with connecting to admin server.
Switching from Prod to DR environment, and OMS does not use DNS resolution, but virtual hostnames resolved via /etc/hosts.
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