Update a Database
Perform update operations on your external OCI databases, using Patch Management's simple intuitive process.
Note
Before you begin an update make sure the database is subscribed to an image in order to perform the update.
Before you begin an update make sure the database is subscribed to an image in order to perform the update.
Update a Database
To perform a patch update on a subscribed database follow these steps:
- Click on the Databases tab, and locate the database you wish to update. Click on the action menu to the far-right of the table and click on Update.
Alternatively you can update databases in bulk by selecting all databases you wish to updated and then
- The Update Databases pop-up appears in the Resources step (step 1). Perform the following sub steps:
- Set a Patching Operation Name (if not entered a default value of
PatchOperation_YYYY-MM-DDTHH:MM:SSZ
is used). - Verify that the Image Details show the correct image name, release, and current image version are shown.
- Select the databases to be updated: By default the database form which you launched the update activity is selected. Additional databases subscribed to the same image can be updated in bulk, by selecting them at this step. Filter databases to be added in bulk by name, type or release using the search filter.
- Set a Patching Operation Name (if not entered a default value of
- The Operations (step 2) is now displayed, in this step perform the following sub steps:
- Under Maintenance Task select Software Deployment to deploy the software, enter the Destination Oracle Home, Oracle Home Name Prefix, and the Start (immediately or later).
- Select Update Database to update the database once the software has been deployed and set a Start time (immediately or later). For example, you can deploy the software now, but schedule the database update during a downtime window.
- Under Option select the:
- Work Directory: Enter the work directory where the files will be stored.
- Drain Timeout: A time measure of seconds allowed in order to complete the resource draining action. If not specified, drain occurs immediately, database instances are shutdown immediately.
- Rolling Mode: (Yes/No) Ensures RAC databases are patching in rolling mode, by patching individual RAC nodes one at a time.
- Skip Cluster Verification Utility Checks: Select to skip the Prerequisite Checks and/or Cluster Verification Utility Check. It is Oracle's recommendation that these checks be run and not skipped.
- The final Review step is now displayed (step 3), in this step perform the following substeps:
- Verify that the Image Details are correct.
- Verify that the database or databases selected are correct.
- Verify that the Software Deployment and Update Database start times are correct.
- Under Validate Databases perform a metadata validation, click on Quick Validation to run. Once the validation completes click on the Succeeded or Failed results to view a detailed breakdown of the validation check.
The detailed breakdown will show the following validations by category:Click Cancel to exit. For failed validations click on Previousto go back in the Update process and correct validation errors.
- Deploy
- Check whether the configuration data is available for the resource
- Validate the path variables in the new Oracle home
- Check whether the resource is subscribed to an image
- Check whether the deploy operation was already done for this resource
- Validate home name prefix
- Migrate Listener
- Check whether the deploy operation is done for this resource
- Update
- Check whether the deploy operation is done for this resource
- Check whether the listeners were migrated for this resource
- Verify that the old and new Oracle homes paths are not identical
- Verify that the old and new Oracle home versions are not identical
Note
It is Oracle's recommendation that a validation checks be performed before submitting the patching operation. - Deploy
- Once all information has been reviewed and all validation checks have passed click on Submit.