Skip to Main Content

Oracle Forms

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Oracle Reports 12.2.1.4 with Existing 11.2.0.4 DB: EM Login MDS Loop / Malformed IPv6 Error & WLS_REPORTS Hangs

Farshid GolziApr 20 2026 — edited 6 days ago

Environment Details:

- Existing Database: Oracle Database 11g 64-bit (11.2.0.4)
- Old Reports Version (previously working): ofm_frmrpts_win_11.1.2.1.0_64
- New Infrastructure Installer: fmw_12.2.1.4.0_infrastructure.jar
- New Forms & Reports Installer: setup_fmw_12.2.1.4.0_fr_win64.exe
- Operating System: Windows 64-bit

Current Status:
The new installation and domain configuration completed successfully. AdminServer is up and running on port 7001, and WLS_REPORTS is up on port 9002. The repository schemas were created successfully using RCU against the existing 11.2.0.4 database.

Problem Description:
I am unable to use the environment due to two critical issues that appear to be related.

Issue 1: Enterprise Manager Login Redirect Loop (MDS Session Failure)

When I access the Enterprise Manager login page (`http://localhost:7001/em`), the page renders fine. I enter the correct WebLogic administrator credentials. Upon submission, the browser is redirected to:
http://localhost:7001/em/faces/helppages/errorPage.jspx

The browser then enters an infinite refresh loop on this error page.

In the startWebLogic.cmd command window logs, the following error stack trace is printed continuously:

<Error> <oracle.help.web.rich.OHWFilter> <BEA-000000> <ADFSHARE-00120: Error encountered while creating the MDS Session. Application state will be reset. Please logout and log back in if problem persists.
oracle.adf.share.ADFShareException: ADFSHARE-00120: Error encountered while creating the MDS Session...
...
Caused By: java.lang.IllegalArgumentException: Malformed IPv6 address at index 8: ldap://[192.168.198.130]:7001

Observation: The IP address 192.168.198.130 is an IPv4 address, but it is being formatted as an IPv6 literal ([ ] brackets), which is causing the underlying Java LDAP bootstrap context creation to fail. This appears to be preventing the MDS (Metadata Services) session from initializing.

Issue 2: WLS_REPORTS Hangs and Health Degrades to Warning

While trying to verify the Reports Server deployment with the basic diagnostic URL:
http://localhost:9002/reports/rwservlet/getserverinfo

The browser loading indicator spins indefinitely. The request never completes, and no output (server info or error) is displayed. After several minutes of this hanging state, the WLS_REPORTS managed server health status in the WebLogic console changes from OK to Warning.

Goal:
I simply want to run a simple test report using rwservlet to confirm that the 12.2.1.4 Reports Server is functioning correctly against the existing 11g database. However, I am stuck at getserverinfo and cannot access the EM console to check deployment status.

Question:
1. Configuration Error: What specific configuration step could have caused the internal LDAP URL to be formatted as ldap://[IPv4] instead of ldap://IPv4?
2. Hanging Reports Servlet: Is the hanging WLS_REPORTS issue a direct consequence of the MDS/LDAP connection failure in the AdminServer, or is it a separate issue? Where should I look to debug the rwservlet hang?

Any guidance on correcting the LDAP URL format in the domain configuration files would be greatly appreciated.

Comments
Post Details
Added on Apr 20 2026
1 comment
149 views