Oracle Communities

Oracle Analytics and AI

Child Item

Trouble Configuring ODBC Connections for Model Administration Tool with OAS Server 2025

Hello,

We are in the process of upgrading to OAS 2025 (from OAS 2022) and plan to do a 2 phase approach - OAS Server first, then Model Administration Tool → Semantic Modeler. However, am running into some issues trying to connect to port 9514 to create the ODBC connections we use for Model Admin Tool. That port doesn't seem to be listening at all. Has anything changed in the port configuration on OAS 2025? Can't seem to find any new documentation. Confirmed with another user having the issue as well.

Can provide full ping results if needed.

Installed OAS 2025 Server on RHEL9. This is the last step needed to complete our our OAS 2025 Server installation. Have a full stack (Dev > Test > QA > Prod), and everything else is working as expected on those servers, including Catalog Manager (which uses https to connect via proxy).

Regards,

Chad

Find more posts tagged with

Accepted answers

Gianni Ceresa

Thanks for all these details Chad.

I didn't try connecting online so far, and your post made me test: same issue, can't connect.

Then I looked into EM for the ports, and … surprise…

Apparently obis1 is now listening on 9515 instead of 9514 where it has been for many years.

It doesn't seem to be documented, therefore it's either a bug or a regression of some kind.

Because my OAS is running in Docker I need to create a new instance to try to see if port 9515 works as expected. I should be able to confirm in a bit…

But it's definitely annoying and not something that should happen with an enterprise product like OAS !!!

Gianni Ceresa

Confirmed: port 9515 works for online connection with the Model Administration Tool.

@Chad Williams , you could raise a SR to report this as a bug. It isn't documented, therefore at least a documentation bug, but I don't see why this port has been changed, because it breaks an in-place upgrade of OAS. Therefore, in my opinion, the bug is that the port number did change, and it should be moved back to 9514 for back compatibility with previous versions of OAS.

Chad Williams

From Oracle Support:

Due to a requirement from FMW, it was required to add a new administration port value to manager server. This had changed the order of ports to increment by 1.

OAS documentation will be updated accordingly in the change of default port numbers.

All comments

Chad Williams

More info from our Linux administrator:

It look likes 'sawserver' is using 9510 and 9514 on OAS 2022 install, but not utilizing those ports on the OAS 2025 server - so there's nothing to connect to. The firewall rules are open in the exact same way on both servers.

The only port that it seems to recognize is 9511, but not 9510 or 9514. We don't open that port with any FW rules.

Chad Williams

Yes, we are installed on Linux RHEL9.

[root@<OAS2022> ~]# netstat -anp | grep 951
tcp 0 0 <hostip>:47016 <hostip>:9511 ESTABLISHED 9719/sawserver
tcp 0 0 <hostip>:58048 <hostip>:9512 ESTABLISHED 9431/nqsclustercont
tcp 0 0 <hostip>:58170 <hostip>:9510 ESTABLISHED 9719/sawserver
tcp 0 0 <hostip>:44488 <hostip>:9514 ESTABLISHED 9719/sawserver
tcp 0 0 <hostip>:35506 <hostip>:9510 TIME_WAIT -
tcp 0 0 <hostip>:44146 <hostip>:9515 ESTABLISHED 9431/nqsclustercont

[root@<OAS2025> ~]# netstat -anp | grep 951
tcp 0 0 <hostip>:38020 <hostip>:9516 ESTABLISHED 1432090/nqsclusterc
tcp 0 0 <hostip>:37392 <hostip>:9511 TIME_WAIT -
tcp 0 0 <hostip>:57606 <hostip>:9513 ESTABLISHED 1432090/nqsclusterc
tcp 0 0 <hostip>:50318 <hostip>:9511 ESTABLISHED 1432286/sawserver

Gianni Ceresa

Thanks for all these details Chad.

I didn't try connecting online so far, and your post made me test: same issue, can't connect.

Then I looked into EM for the ports, and … surprise…

Apparently obis1 is now listening on 9515 instead of 9514 where it has been for many years.

It doesn't seem to be documented, therefore it's either a bug or a regression of some kind.

Because my OAS is running in Docker I need to create a new instance to try to see if port 9515 works as expected. I should be able to confirm in a bit…

But it's definitely annoying and not something that should happen with an enterprise product like OAS !!!

Gianni Ceresa

Confirmed: port 9515 works for online connection with the Model Administration Tool.

Chad Williams

Sounds good. Going to confirm some things on my end, put in a ticket request to update the firewall rules, then submit the SR/bug with Oracle. Great job Gianni!

Chad Williams

Also, just noticed all of those ports shifted by up 1. I will have to look into my proxy to see if any of those ports are being specified.

Steve F-2

As a counter point, I do not think it would be considered a defect (bug).

When you install, you can choose whatever port range you wish, or works on your server. The default is 9500-9999.
Exact ports are not documented .There are examples that use some common defaults.
You can check your ports after installation with:
- [DOMAIN_HOME]/bitools/bin/status.sh|.cmd -v
- [DOMAIN_HOME]/bi/config/fmwconfig/bienv/core/bienv-components.xml
- Fusion Middleware Control Enterprise Manager UI
If you perform an in-place upgrade, it will keep your existing ports.
If you perform a new installation or out-of-place-migration, you may have different assigned ports.

Potentially, there could be a documentation enhancement in the Installation Guide, and/or the Upgrade and Migration Guide with instructions on how to verify your ports after installation, or upgrade.

My thoughts, others welcomed.

Gianni Ceresa

Valid point Steve, but it's still a change of default that was set for the past 10 years, from the very first OBIEE 12c release.

They will not call it a bug, but that's how it feels to anyone who had the product before OAS 8.2 (2025). And this kind of things is quite annoying for an "enterprise" solution. Mostly because there is nothing on 9514, therefore it looks like a change just for the fun of being able to change it, which is something you don't do on an enterprise application. Also because the trust in the OAS 8.2 went down, so now I will not trust it by default anymore.

Steve F-2

I certainly understand the annoyance, especially when you have scripting/automation with CLI/API's !

In the interim, have filed documentation enhancement, since there can't be an immediate "code fix". I have guesses about how this happened, but it is too late now.

Chad Williams

FYI, I submitted this to support and they created the following bug for the Dev Team:

bug 37840145

That link doesn't net anything, but just wanted to pass the info along.