@Ashish-Oracle agree.. But I suppose it will be hard effort for now! However to keep information ready, if you have any docs for easy migration to 2024 ? We are already thinking to move to OAC, but several hurdles still in that direction to OAC..

Hi @Gianni Ceresa Nothing changed, except we apply the patches quarterly as released. Your case is slightly confusing: it's OAS but then you talk about starting a Publisher server node. it means? We were using BIP before, then we migrated to OAS 2023, 2 years back.. You mean the error shown, is it doing something of legacy…

with disable "JAVA_OPTIONS="-Doracle.jdbc.fanEnabled=false", also error 696+0000 INFO: Command to execute :- /opt/jre/jre/bin/java -Xmx2048m -Doracle.bi.product.dir=/u01/oracle/oracle_common/../bi -Doracle.bi.domain.dir=/u01/oracle/user_projects/domains/bi -Dbi.security.domain.home=/u01/oracle/user_projects/domains/bi…

without disable this is the error: Creating Audit Services Viewer(IAU_VIEWER) Percent Complete: 62 /attempt to configure ONS in FanManager [CONFIG] [Oracle_Analytics_Configuration] [Add default service instance]:2025-02-19T09:34:06.960+0000 Feb 19, 2025 9:29:01 AM oracle.simplefan.impl.FanManager configure [CONFIG]…

is OAS 2023 supported still ? or should we migrate to OAS 2024 ?

Hello, any solution found for this? I am also facing same..

these docs, suggesting to use Oracle Cloud Service Application using client id & secret kind of configurations.. Searching for the reference to use Integrated application ( SAML certificates metadata) way..

Thanks @SteveF-Oracle, @Mostafa Morsy-Oracle I am reading these documents, will get back if any further questions. Thanks a lot for quick response..

New thread opened, thanks @SteveF-Oracle

related to:

Ok I will open new thread.

Hi @SteveF-Oracle Now I am able to build oam domain, along with existing bi domain on same pod. and I should change password login mechanism of analytics, to SSO connected with OCI App I am referring this But not clear guidance on this page, on what to be done for SSO. if you know any other clear steps document, please…

Thanks @SteveF-Oracle, I will try on separate domain. Initially thought to build on same OAS domain, as we thought that can be minor modifications for OAS SSO integration. and later migration strategy for existing password login method .. But seems this is not going to be simpler 😅

@SteveF Then will it be okay to create a seperate domain for oam, under same machine?

I have already installed OAM on existing pod referring, https://github.com/oracle/docker-images/tree/main/OracleAccessManagement/dockerfiles/12.2.1.4.0 — After adding Installation in docker file, and new pod built.. I am trying to create clusters & servers for OAM, but not successful.

Thanks @Mallikarjuna Kuppauru-Oracle followed this document, it works. but very hard to implement this in kubernetes deployment, as first half part expect OAS online, then it needs to be stopped, which makes pod die.. and strange after following these steps, still logs print invalid password error, but still goes online…

@RanaAshutosh-Oracle if I want to change admin password itself. then will this script work? and in that case, do I need to give same admin username for both ADM-USER/USER1 ? <ADM-USER> <ADM-PASSWORD> <USER1> <PASSWORD1> and I think ADM-PASSWORD should be existing, and PASSWORD1 should be new ? --- is this also expects, any…

after these steps, password change working fine on weblogic console. and also weblogic console working even after restart. But only I am concerned why logs are throwing invalid password errors.. (AdminServer-diagnostic.log) [2023-12-18T09:19:05.352+00:00] [AdminServer] [ERROR] [] [oracle.wsm.resources.policymanager] [tid:…

after these steps, password change working fine on weblogic console. and also weblogic console working even after restart. But only I am concerned why logs are throwing invalid password errors.. (AdminServer-diagnostic.log) [2023-12-18T09:19:05.352+00:00] [AdminServer] [ERROR] [] [oracle.wsm.resources.policymanager] [tid:…

One more suggestion needed. On Source OAS, WLS console, Deployment are looking good. But in cloned Target, Deployment screen looking like this with error's, any more updates, to be done?