How To Do Database Upgrade Which Is Used Internally By OSB 188.8.131.52.0
(Doc ID 2498168.1)
Last updated on FEBRUARY 01, 2020
Applies to:Oracle Service Bus - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, OSB Installer
How to do database upgrade which is used internally by OSB 18.104.22.168.0
Recently we have upgraded to OSB 22.214.171.124.0 from OSB 11g. We are running one of our highly used application in OSB 12c. Our application is available 24*7 so no downtime is expected in this application.
In 11g there was no internal database which was used by OSB. So we only had application database which we used to cache (by coherence cache) during downtime of database. Hence our application would be available even in case of database downtime. Hence we were meeting high availability for our application.
Now in OSB 126.96.36.199.0 OSB uses internal database also, so when there is a downtime of database due to upgrade activity in then OSB will be not be available and this will lead to a downtime of our application.
Can you please suggest what can be done to achieve high availability?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document