Prerequisite Tasks for Upgrading Oracle Linux on the VM
You must verify the SCM version and health of the SCM application before you upgrade Oracle Linux on the VM:
- Verify the version of SCM running on the
VM.
sudo docker ps
- If you're running SCM 24.7 or lower, then you must migrate to SCM 24.8, as
follows:
- Upgrade the SCM server to 24.8, as
follows:
cd /home/opc bash start_cmserver.sh CM_24.8.0
- Verify the version of the SCM application, as
follows:
sudo docker ps
The version of the running SCM container must be 24.8.0.
- Migrate the new SCM features, as
follows:
docker exec -it cloudmanager bash cd /home/opc bash siebel-cloud-manager/scripts/cmapp/migration.sh
Choose "Upgrade CM instance script" when the options are presented by the
migration.sh
script. - Exit from the SCM container and restart the container, as
follows:
cd /home/opc/cm_app/{CM_RESOURCE_PREFIX}/bash start_cmserver.sh CM_24.8.0
- Upgrade the SCM server to 24.8, as
follows:
- Ensure that the SCM application is functioning by executing the following API
request:
curl --location --request GET 'https://<CM_Instance_IP>:<Port>/scm/api/v1.0/environment/<env_id>' \ --header 'Content-Type: application/json' \ --header 'Authorization: Basic <Base 64 encoded user:api_key>'
The SCM service is functioning correctly if the response includes valid environment details.
- Create a backup of the SCM file system mounted at
/home/opc/cmapp
on the current OL7 instance to ensure data recovery in the event of any unexpected issue during the upgrade process.Note: When taking a backup, it is important that you:- Do not store the backup on the same SCM instance, as this instance will be destroyed and recreated during the upgrade process. Use an alternate and secure location to store the backup.
- Do not solely depend on FSS snapshots for backup purposes.