Yes it is the communication that is the key issue here; though patch delays do play havoc with schedules.. Yes, both DB & OAS patches were noted as post release & ETAs but OBI patch info was just totally MIA. The tab for OBI is completely missing from the PAD lol & yikes if AI is being used in the vuln detection.. tongue…

I raised an SR on this issue with the following response:

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…

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]…

Great - thank you