if needed OAS or mellon diagnostic logs, I can share .. Kindly suggest..

please let me know if any more details needed, and also if necessary we can chat on slack. thanks @Gianni Ceresa

And about SSL mentioned in this (Doc ID 2902159.1), I have disabled it.. is that be a reason ? we are handling security in separate kubernetes pod layer of nginx-ingress.. so native SSL https protocol on OAS pod need to be disabled .

console and analytics , not showing same login page.. both showing it's own login different pages.. but the problem here is after SSO authentication via IAM is successful, I was not expecting native login pages! I was expecting SSO authentication via IAM should be sufficient.. as normal SSO process. Kindly let me know if…

And on browser inspection this is the error The last redirection is not happening correctly, it is directly hitting, "/bi-sac-config-mgr/api/v1/sessionState/locale", without including prior redirection path, On browser, live I have edited manually & triggered again with right redirection then 401 Unauthorized.. — Here the…

But I see one difference in this issue I am seeing, @User_AOKHO has mentioned on accessing he is getting 404 Not Found.. — for me, accessing /bi-sac-config-mgr/security/UsersAndRoles.html redirecting to /bi-sac-config-mgr/index.html?ojr=UsersAndRoles and forever waits in this below shown gif snap like waiting screen !!

I am also facing same issue.. I have installed OAS 2025, same issue happening even in fresh installation, and also on upgrading from 2023. - @User_AOKHO, is it resolved to you? what is the exact steps you followed?

@SteveF-Oracle we are upgrading now from OAS 2023 , shall I directly jump to OAS 2025 ? why I am asking suggestion is, dealing with BIP/OAS is a difficult one, so just our target is to save as much time possible on OAS maintenance.. We have lot of environments running this setup. So what will you suggest shall I proceed…

Same issue observed while upgrading either to OAS 2024 or OAS 2025.. Ya, I think SR is the only way to get this resolved.. will do that.. Thanks @SteveF-Oracle

And when I tried to apply this patch, it's superset patch 36946553 is already a necessary patch indicated in FMW quarterly patches list..

The issue happening in OAS 2023 to OAS 2024 upgrade .. and the patch 35515979 suggested, is saying BIAPPS UPGRADE OAS6.4 WITH OCT CPU TO OAS7 FAILS AT RECONFIG… — as per I have found OAS 2023 is 7.0 right & OAS 2024 is 7.6? is it may be same old patch necessary here also, or a typo in naming the patch?

and also noticed this error in upgrade domain step using upgrade-assistant INFO: Processing plugin: com.oracle.bi.sac.upgrade.plugin.SacSnapshotsConfigPlugin Mar 14, 2025 7:49:06 AM com.oracle.bi.sac.upgrade.plugin.SacSnapshotsConfigPlugin update INFO: SAC: Snapshots upgrade starting..., oracleHome = /u01/oracle,…

And one more observation, when I compare with our old setup, this patch p35847501_122140_Linux-x86-64.zip is removed at OAS level & applied before in fmw setup itself as this patch mentioned their, (now 37297691 OSS 19C BUNDLE PATCH), is this can be the reason? — I feel this should not be the reason right, just the…

And this issue is random, over last week, I have seen both successful & failure scenarios.. I have also confirmed password to have only alphanumeric & only these 2 symbols allowed underscore _ or hash # Failure, stops at: INFO: Getting new DataSource through DataSourceFactory…

@BrandonH This is very detailed.. Thanks.. I will try this…

@BrandonH Also validated that we have a file "${DOMAIN_HOME}/bin/setDomainEnv.sh" in the setup, but we are not calling it.. After RCU creation, we are calling "$ORACLE_HOME/bi/bin/config.sh", and I made sure to export the both variables as mention in last comment.. But why it is not in effect, in logs still that option…

As per doc 2308193.1, I have added to both export JAVA_OPTIONS="-Doracle.jdbc.fanEnabled=false <other-options>" export CONFIG_JVM_ARGS="-Doracle.jdbc.fanEnabled=false <other-options>" before starting config.sh.. However I have observed it is not taking effect.. - Do we need to do something additional with setDomainEnv ?…

Seems no DB connection issue.. seems this issue has started from October Patch, now I did a test on our pods.. I ran installation with old patch & it worked without any issue.. however with october patch & even january patched installation is throwing out this issue.. — I have also posted a comparison of logs in

2 weeks back also when I saw this error, I posted here

One more observation did today comparing to the old patch where it is successful.. With old patch this step passing at "Configuring BI components" Feb 21, 2025 8:34:58 AM oracle.bi.servicelcm_v2.configuration.BiPlatformDiscovery$Internal getBiPlatformDataSourceFromFactoryWithPassword INFO: Getting new DataSource through…