Classes12 Jar For Oracle 11g New Features

Or in cases where you have another backup/restore strategy in place already, and don’t want to rely on a GRP. And I will assume that you will change COMPATIBLE only in cases where you are either 100% certain that the upgrade will succeed and you won’t fall back to a GRP. Didn’t I write above that you can’t change COMPATIBLE when a GRP is in place – which is the standard behavior of the tool? Yes, I did. This way I can pass a script to AutoUpgrade changing COMPATIBLE after the database upgrade.īut wait one second please.

I take screenshots from the Oracle Database 19c Upgrade Guide here: And here is how.ĪutoUpgrade has these powerful options to execute a shell script before or after upgrade:

Or actually you can convince it to do so. And with the change to the CDB-only architecture with Oracle 20c this may even play less of a role as there is no seamless simple fallback anyways anymore when you migrate to the CDB-architecture. And still, we listen to your feedback and discussed whether AutoUpgrade may get a parameter to enforce compatibility after a successful upgrade. But having a GRP since Oracle Database 12.2.0.1 blocks the change of COMPATIBLE as long as the GRP is in place.Īctually these are enough reasons to have the AutoUpgrade not change COMPATIBLE. Either via flashing back to a Guaranteed Restore Point (GRP) right after the upgrade, or days after the upgrade with the database downgrade.įurthermore, by default AutoUpgrade sets a GRP – and allows you to flashback to it.

By keeping COMPATIBLE on the previous (before upgrade) value, you have the choice to revert back to the previous state. At first, we recommend to not change the COMPATIBLE parameter right after the upgrade if you can afford another downtime soon after. Clearly, AutoUpgrade does not change the COMPATIBLE parameter for several reasons. Photo by Ivana Cajina on Unsplash Does AutoUpgrade change COMPATIBLE?

Classes12 Jar For Oracle 11g New Features