7 Upgrade and Patch Mechanism
OCLM supports two customer maintenance patterns:
Table 7-1 OCLM Upgrade and Patch Update Methods
| Maintenance Type | When to Use | Main Action |
|---|---|---|
| Patch update | Use when Oracle supplies an OCLM application wheel and required patch dependency files for the same VM release. | Stop OCLM, back up the previous wheel packages, copy the Oracle-provided patch files into the required OCLM folders, run /opt/oclm-service/bin/upgrade.sh, and validate the service.
|
| Full upgrade | Use when Oracle supplies a new OCLM VM/VMDK image, base image update, or release that requires redeployment. | Back up customer-specific files from the old VM, deploy a new VM, restore only customer-specific configuration and certificate material, then validate service behavior. |
Do not copy old release binaries, old service scripts, the old runtime directory, old patch dependency files, or old systemd unit files into a new VM. A full upgrade should restore only customer-specific configuration, trust files, and identity files. The new VM image supplies the release-specific application files.