Rolling Back a Patch or Failed Patch

Note:

Currently, rolling back a patch is not supported for database deployments hosting an Oracle Real Application Clusters (RAC) database.

You can roll back a patch or failed patch attempt on a database deployment by using the Oracle Database Classic Cloud Service console or, if desired, by using one of the ways listed in Other Ways to Roll Back a Patch or Failed Patch at the end of this topic.

Note:

Oracle strongly recommends against performing the rollback operation on a database deployment that has never had patches applied to it. You should only use the rollback operation on patches that you have applied to a database deployment.

Note:

Beginning with the April 2015 Patch Set Update (Apr 2015 PSU), Oracle adopted a “composite” approach to patch set updates. With this composite approach, a rollback operation restores the software release level to the previous patch set level instead of to the base software release level. For example, if you roll back the April 2015 Patch Set Update, the software is restored to the January 2015 Patch Set Update release level, not the base release level.

Rolling Back a Patch or Failed Patch by Using the Oracle Database Classic Cloud Service Console

To roll back the last patch or failed patch attempt by using the Oracle Database Classic Cloud Service console:

Go to the Patching page of the database deployment on which you want to roll back a patch:
1. Open the Oracle Database Classic Cloud Service console.
  
  For detailed instructions, see Accessing the Oracle Database Classic Cloud Service Console.
2. Click the database deployment on which you want to roll back a patch.
  
  The Oracle Database Classic Cloud Service Overview page is displayed.
3. Click the Administration tile and then click the Patching tab.
  
  The Oracle Database Classic Cloud Service Patching page is displayed.
Click Rollback.

The Patching page redisplays, showing a status message that your request has been submitted, the Administration tile shows the starting time of the rollback operation, and a Rolling back... message replaces the Rollback button.

Note:

Rollback operations are performed with a minimum of impact on the functioning of the database. However, during a patch rollback operation the database may be shut down for a short period of time, thus making it inaccessible.

Other Ways to Roll Back a Patch or Failed Patch

For database deployments hosting single-instance databases, you can use the patch db switchback subcommand of the dbaascli utility. See Rolling Back a Patch or Failed Patch by Using the dbaascli Utility.

Rolling Back a Patch or Failed Patch by Using the dbaascli Utility

You can use the patch db switchback subcommand of the dbaascli utility to roll back the last patch or failed patch attempt to a database deployment hosting a single-instance database or an Oracle Data Guard configuration of single-instance databases.

Connect as the opc user to the compute node.

For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
Start a root-user command shell:
```
$ sudo -s
#
```
Roll back the last patch in the deployment using the patch db switchback subcommand of dbaascli:
```
# dbaascli patch db switchback
```
The patch is removed and the database instance reverts to its previous state.

The patch db switchback subcommand is not yet available on Oracle Cloud at Customer. Instead, for a database deployment hosting a single-instance database you must use the dbaascli dbpatchm rollback command, and for a database deployment hosting an Oracle Data Guard configuration of single-instance databases you must use the dbpatchmdg rollback_async command.

Note:

Rollback operations are performed with a minimum of impact on the functioning of the database. However, during part of the operation the database instance is shut down, thus making it inaccessible.
Exit the root-user command shell:
```
# exit
$
```