1. Cloud Control Database Lifecycle Management Administrator's Guide
  2. Database Maintenance: Updates (Patching) and Upgrades
  3. Database Updates and Upgrades Using Fleet Maintenance
  4. Fleet Maintenance Automation
  5. Fleet Maintenance EM CLI Operations
  6. Rollback Operations
  7. Rolling Back Of a Failed Update Operation

Rolling Back Of a Failed Update Operation

Should a single instance or RAC database update operation fail use the following steps to perform a rollback to its initial state.

Rolling Back a Failed Update Operation

Before you consider performing a rollback of a failed update verify if the update procedure was successful or failed. You can verify via the UI by following these instructions: Track, Fix and Resume Update Procedures.

To rollback a failed update operation use the following EM CLI command:
emcli db_software_maintenance 
-performOperation -name="Rollback failed DB update"
-description="Rollback DB" 
-purpose=<ROLLBACK_DB|ROLLBACK_RACDB>
-target_list=<DB name>
-target_type=<DB type>
-normal_credential=<HOST_CRED>:<CRED_OWNER>
-privilege_credential=<HOST_ROOT_CRED>:<CRED_OWNER> 
-force=true
  • purpose: There are standard purposes that can be performed by Fleet Operations which can be:
    • ROLLBACK_DB
    • ROLLBACK_RACDB
  • target_type: The type of target being provided in this operation which can "rac_database" or "oracle_database”.
  • target_list: This is a comma separated list of targets which need to be patched.
  • normal_credential: This must be entered in the format <Named Credential: Credential Owner> where:
    • <Named Credential>: Named credential for the host where new Oracle home will be deployed.
    • <Credential Owner>: The Enterprise Manager user who owns this Named Credential.
  • privilege_credential: This must be entered in the format <Named Credential: Credential Owner> where:
    • <Named Credential>: Named credential for the host where new Oracle home will be deployed.
    • <Credential Owner>: The Enterprise Manager user who owns this Named Credential.

    These credentials are used to run scripts as root.

  • force: This is mandatory parameter for failed update cases requiring a rollback.

Example

This is a sample code for a rollback operation of a failed update:
emcli db_software_maintenance 
-performOperation 
-name="Rollback RAC DB" 
-purpose=ROLLBACK_RACDB 
-target_type=oracle_database 
-target_list="ORCLTDE.abc.example.com" 
-normal_credential="NC_HOST_CREDS:SYSMAN" 
-privilege_credential="HOST_PRIV:SYSMAN" 
-force=true

For PDB relocation and updates that fail before the patching step or within the patching step there is no action to be taken as the update will not have taken place. If the failure occurs after the patching step, rollback is required. Follow the steps outlined under Rollback Operations.

If the update was successful and you wish to perform a rollback, use the rollback steps outlined under Rollback Operations.