Categories
OAS 2024 BI Model Administration Tool connection fails
Hello community,
I hope you are doing well and you can help me with a small issue I am having.
I have a recently installed OAS 2024 on RH 8. The Client Tools (also 2024) are installed on a Windows machine, the ODBC DSN is correctly configured, using port 9514, as specified in EM, the firewall rules are in place.
All services are up. DV, Analytics, EM and console are working fine, being accessible from the same Windows machine and via proxy.
With all that, I am getting this error when trying to open the rpd in an online mode:
We have a parallel OAS 2024 installation, upgraded from OAS 2023, which I could use to test the Client Tools 2024 and it works.
Do you know if there might be anything on the new OAS installation blocking this connection?
Kind regards,
Ana-Maria Lachescu
Best Answer
-
Hi Gianni,
Hi Steve,
I have disabled the OAS internal ssl and now I am able to open the RPD in an online mode.
Kind regards,
Ana
1
Answers
-
Hi Ana-Maria,
Welcome to the Oracle Analytics community and forum.
As you say this is a brand new install of OAS 2024 (not upgraded like the one that works) I imagine it is also fully patched.
With OAS 2025 the port for the Model Administration tool to connect online has been moved to 9515. Oracle said it was due to a FMW change that required an extra port for something else and therefore the BI Server moved one port up.
If we trust that, it's possible that your OAS 2024 new install also had the same. While the FMW version is the same for the past 5 years, patches keep changing, it's possible that such a change in ports is introduced by a recent FMW patch.
Open your EM and look at the BI components and check the ports, to make sure it is really 9514. Maybe you will have the (not so nice) surprise that your new OAS 2024 is also on 9515.
Your upgraded environment is still on 9514 because it is an upgraded one, and an in-place upgrade preserves the port numbers.
0 -
To add,
Gianni, the reason given for OAS 2025 is correct (although, I think it should have been planned out better).
This should not affect OAS 2024.
Can you confirm your port:status.sh -v
or check[DOMAIN_HOME]/bi/config/fmwconfig/bienv/core/bienv-components.xml
From the Windows client machine, are you able to check the port connection for obis1 and cluster controller with utilities such as ping, telnet, nectat, etc. to see if it is reachable and listening.0 -
Hi Gianni,
Hi Steve,
Thank you for your answers!
Regarding patching level, the CPU Patch released in April 2025 was installed.
The port in EM is 9514:
The port is 9514 when executing status.sh -v
When looking at
[DOMAIN_HOME]/bi/config/fmwconfig/bienv/core/bienv-components.xml, and comparing it with the old installation, the port is correct , but I notice a difference, the new one has <unmanaged>false</unmanaged>
Could that make problems?
Kind regards,
Ana
0
