Standalone OAP Domain upgrade - OAS/P 6.4 2022 to OAS/P 2024 but ANY oas to oas version

ArtyAtFinance

Apologies if this has been asked in some form or other BUT I have raised an SR on this topic & got sent somewhat in circles.

Any gurus with advice &/or options for an OAP standalone Domain upgrade. From all efforts to date it is just not possible ie.

• install new JDK
• install new FMW INFRA
• install OAS 2024 binaries
• upgrade existing OAP (prior version) Domain

The ONLY way forward appears to me to be: new installation configuration of a NEW Domain & then export import the file based Publisher catalog.

Is this the path that other Publisher ONLY administrators follow?

Thank you

Mallikarjuna Kuppauru-Oracle

HI @ArtyAtFinance

We have an 2 ways to upgrade your version.

1. In-Place
2. Out of Place

In-Place - You need to install the latest binaries and oracle home and upgrade your existing domain.High level steps as below -

Running a Pre-Upgrade Readiness Check -->Upgrade Assistant in -readiness
Upgrading Product Schemas -->The Upgrade Assistant allows you to upgrade individually selected schemas or all schemas associated with a domain
Starting the Upgrade Assistant -->Run the Upgrade Assistant to upgrade product schemas, domain component configurations, or standalone system components to Oracle Analytics Server.
Re-configuring the Domain

2. Out-Of-Place

Its an sort of fresh installation you need to install every thing including RCU, Fresh domain configuration, You need to do your customization again..etc.

Move your backup from old to New.

Regards,

Arjun

ArtyAtFinance

Thank you for your reply but a clarification is what I am after & I don't think what you have stated is correct.

OAP > > > standalone < < < Domain upgrade Option 1 - is not an option. It does not & as far as I can see, cannot work. The readiness check alone will not work.

[2024-11-29T13:45:54.745+08:00] [Framework] [ERROR] [UPGAST-00271] [upgrade.Framework] Validation of specified domain failed. /u01/oracle/config/domains/oap
[2024-11-29T13:45:54.745+08:00] [Framework] [ERROR] [upgrade.Framework] Cause: The specified domain failed validation which will prevent domain reconfiguration.

com.oracle.cie.external.domain.info.DomainInfoException: No reconfig template exists for templates:
Oracle BI Base:12.2.1.4.5
Oracle BI Topology:12.2.1.4.5
Oracle Enterprise Scheduler Service Client Stub:12.2.1.3.0
Oracle Enterprise Scheduler Service Stub:12.2.1.3.0
11 other templates

The ONLY thing I've found to get past initial validation is this selection for "schema" upgrade - but I've not been game to continue - I have no faith at all that the Domain upgrade would work even if DB Metadata upgrade of this selection does. No other selection or combination of selections work.

I also note this footnote (below ? referring to OAP standalone for example???) for readiness check - so I did try to just skip the readiness & run the ./ua anyway - result was the same.

I also came across this & our cluster is renamed to custom value oap_cluster… Just on the off chance, I updated it back to bi_cluster - result; the same!

https://support.oracle.com/epmos/faces/DocContentDisplay?id=3020439.1

Cause
Customized cluster name disrupts In-Place upgrade process from Oracle Analytics Server 2023 to 2024

Again -

The ONLY way forward appears to me to be: Option 2: including new installation & configuration of a NEW Domain & then export import the file based Publisher catalog.

Regards

ArtyAtFinance

I can't really believe I'm the only one in the World with a standalone Publisher (Cluster) Domain that needs upgrading so in case this helps anyone here is the series of steps we have had to resort to:

So the entire process (vs OAS focused doco process) is:

install java, install FMW infra, install OAS2024, apply latest CPU/s
implement WORKAROUNDs*
readiness check, schemas upgrade, reconfig DOM, upgrade DOM
revert WORKAROUNDs*
startup

Scale out – which I am now going to trial

Referred workarounds incl:

1: [ Doc ID 3020439.1 ] revert custom cluster name (oap_cluster) to default cluster name (bi_cluster);
2: [ Doc ID 3031407.1 related] restore COPY of default config /Admin folder to its default location vs NFS cluster location; despite being configured for a clustered NFS SDD (singleton data directory) location the upgrade looks for quartz2-config.properties in the old default location;
3: [ Doc ID 2955825.1 related] remove log4j lib specs from config & config-groups; this is just an oversight by Oracle due to log4j vulnerabilities & patches.

After upgrade, we must then unwind the workarounds “AND” in the case of 3: actually hack in the new log4j lib version! vs the old one that was removed.

Regards