"ERROR: DAD "portal" not found in URL" After Adding a Second Application Server For High Availability According To The Instructions In The Fusion Middleware High Availability Guide (Doc ID 2076614.1)

Last updated on AUGUST 26, 2017

Applies to:

Portal - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

Oracle Portal 11.1.1.6 has been configured for High Availability according to the instructions in the Fusion Middleware High Availability Guide, section 14, "Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer". When the managed server WLS_PORTAL on the the first application server has been started, users are able to access the Portal pages. When the managed server WLS_PORTAL1 is started on the second application server, users are unable to access the Portal website. The WLS_PORTAL1.log :

<Nov 5, 2015 1:28:37 PM CLT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Nov 5, 2015 1:29:57 PM CLT> <Error> <oracle.portal> <BEA-000000> <ERROR: DAD "portal" not found in URL (http://hostname.com:7777/portal/pls/portal/PORTAL .wwpob_smd.login2).>
<Nov 5, 2015 1:30:05 PM CLT> <Error> <oracle.portal> <BEA-000000> <ERROR: DAD "portal" not found in URL (http://hostname.com:7777/portal/pls/portal/PORTAL .wwpob_smd.login2).>

 The configuration file portal_dads.conf in the directory <DOMAIN>/config/fmwconfig/servers/WLS_PORTAL1/applications/portal/configuration on the second application server is empty.

Cause

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