Error Page Metadata Could Not be Obtained from the Portal Database After Changing IP Address (Doc ID 565782.1)

Last updated on OCTOBER 20, 2023

Applies to:

Symptoms

After change the IP address of Infrastructure Tier and Middle tier residing in different boxes, Portal fails to load in the browser with the following error:

Error : Page Metadata could not be obtained from the Portal Database

This error is accompanied by the following error in the Portal's application.log:

<TIMESTAMP> portal: id=<ECID> ContentFetcher Unexpected Exception Request
Failed:oracle.webdb.dispatcher.DispatcherException: I/O Error dispatching request
name=content-fetcher3 label=pageMeta
url=http://<REVERSE_PROXY_HOST>:<REVERSE_PROXY_PORT>/portal/pls/portal/!PORTAL.wwpob_page.show?_pageid=<PAGEID>
time=283ms timeout=60000ms process=Dispatching

The Middle Tier HTTP home page at http://<REVERSE_PROXY_HOST>:<REVERSE_PROXY_PORT> works.

In other scenarios, when accessing Portal from IE, an HTTP 500 Internal Server Error may be displayed in the browser while the URL is shown as http://<REVERSE_PROXY_HOST>:<REVERSE_PROXY_PORT>/sso/auth.

The Portal pages are accessed through a reverse proxy.

Steps To Reproduce:

1. Have a Portal configuration front-ended by a Reverse Proxy.
2. Change the IP addresses of the Portal middle tier and the infrastructure.
3. Run the script "chgiphost" as documented at:
   Oracle® Application Server Administrator's Guide 10g
   8.2 Changing the Hostname, Domain Name, or IP Address
4. Notice the above error when trying to access the Portal's welcome page at
   http://<REVERSE_PROXY_HOST>:<REVERSE_PROXY_PORT>/portal/page/portal/TOPLEVELSITE/Welcome

Changes

The IP address of the Infrastructure Tier and the Middle tier was changed.

Cause