Autoupgrade - How to perform out-of-place (OOP) patching using Autoupgrade?
(Doc ID 2984437.1)
Last updated on JANUARY 10, 2025
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Database - Enterprise Edition - Version 19.3.0.0.0 and later
Information in this document applies to any platform.
Goal
Describe the procedure to apply a RU patch on 19c RDBMS standalone (non ASM) binaries using out-of-place approach with Autoupgrade tool.
The AutoUpgrade Patching feature extends the AutoUpgrade upgrade capabilities for patching process, which enables to perform out-of-place patching for multiple databases using a single command. The out-of-place patching consists to substitute the current ORACLE_HOME to a new location where a new ORACLE_HOME has been installed with the newest RU and one-off patches applied. By consequence, two ORACLE_HOME installations will co-exist at the same time and this should be considered for free space on the server.
Datapatch will be executed automatically and as AutoUpgrade extends the upgrade capabilities for patching process, Statics will be gathered at the beginning (FIXUPS phase) and at the end (POSTFIXUPS phase) of Datapatch stage (DEPLOY phase). Please consider the complete process can take much time due gathering statics. Please refer to the Autoupgrade Documentation for further details.
The AutoUpgrade Patching has some limitations. A downtime is required, the Database will be restarted. Configuration files like "tnsnames.ora" are not copied and transferred to target home, after patching the file could not be as original. As workaround copy files manually.
For a specific configuration on Windows platforms, please refer to the Autoupgrade Documentation for further details.
In this document the 19.3 Database on Linux environment will be applied with 19.21 RU (35643107) + 19.21 DPBP (35787077).
Details of source environment:
* By default the value of restoration parameter is set to "yes", if database is not in archive mode and you don't want the Autoupgrade created a Guarantee Restore Point (GRP) set to "no".
Solution
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
| Goal |
| Solution |
| References |