This procedure covers OS, Grid and RDBMS home patching for Oracle Cloud Infrastructure (OCI) DB systems using the dbcli utility. Run every step as root.
Advantages of dbcli patching
- Simple command line, with no manual patch download or copy to the nodes.
- Patches are downloaded automatically if the service gateway can reach Oracle Object Storage and the YUM repos.
- Applied in a rolling fashion, so no downtime is needed.
Disadvantages
- You can't choose the patch version; the latest available in OCI is applied.
- Rollback isn't possible from the console, and dbcli support is limited (see the note at the end).
Steps
1. Backup
Make sure a recent full backup exists before patching.
2. Blackout
Create a blackout for both nodes (console or emctl) to avoid unnecessary alerts.
3. Check patch availability
# dbcli describe-component
4. Pre-checks
Grid home:
# dbcli update-server -p # dbcli describe-job -i <jobId>
RDBMS home:
# dbcli list-dbhomes # dbcli update-dbhome -i <ID> -p # dbcli describe-job -i <jobId>
Each command submits a background job. Check its status with the JobID until it shows Success.
5. Apply patches
If all pre-checks succeed, patch the Grid home (rolling, no extra action needed):
# dbcli update-server # dbcli describe-job -i <jobId>
Then patch the RDBMS home (in-place image patching):
# dbcli update-dbhome -i <ID> # dbcli describe-job -i <jobId>
6. Rollback (RDBMS home)
# dbcli update-dbhome -i <ID> -r
Note: I haven't tested rollback yet and will update this post after testing.
Comments
Post a Comment