My Oracle Support Banner

EXACS:OCPU scaling is failing with error "dynamicscaling.service failed" (Doc ID 2930096.1)

Last updated on APRIL 29, 2024

Applies to:

Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]
Information in this document applies to any platform.

Symptoms

 OCPU scaling is configured for the below customer requirement in one of their compartment as per the steps in Doc ID 2719916.1

Monday to Friday 4 OCPU from 6 pm - 6 am>>>>>>>>>12 hrs range

Monday to Friday 6 OCPU from 6 am - 6 pm>12 hrs range
Weekend OCPU set to 4

//Scaling status is getting failed as below.

 

# systemctl status dynamicscaling.service


● dynamicscaling.service - Dynamicscaling
Loaded: loaded (/etc/systemd/system/dynamicscaling.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2023-01-31 17:34:36 GMT; 3s ago
Process: 247876 ExecStart=/bin/sh -c /opt/dynamicscaling/dynamicscaling.bin --cloud-vm-cluster-id ocid1.<ocid> --tenancy-id ocid1.tenancy.oc1..<tenancy_id> --user-id ocid1.user.oc1..aaaaaaaavlimbsaeixhu7zmlvi6j6xee43g4wcivhtmafkkrvs7n4yl2foxa --keyfingerprint 08:40:38:00:44:64:20:91:bd:81:6d:c2:e4:41:f2:9a --privatekey /home/opc/.oci/ODyS_OCU_USER.pem --interval 300 --maxthreshold 80 --minthreshold 60 --maxocpu 10 --minocpu 4 --ocpu 2 --scheduling "Monday:6-17:6;Monday:18-5:4;Tuesday:6-17:6;Tuesday:18-5:4;Wednesday:6-17:6;Wednesday:18-5:4;Thursday:6-17:6;Thursday:18-5:4;Friday:6-17:6;Friday:18-5:4;Saturday:0-23:4;Sunday:0-23:4" (code=exited, status=1/FAILURE)
Main PID: 247876 (code=exited, status=1/FAILURE)

Jan 31 17:34:36 ociexa-ad2-ay6y51 systemd[1]: Unit dynamicscaling.service entered failed state.
Jan 31 17:34:36 ociexa-ad2-ay6y51 systemd[1]: dynamicscaling.service failed.>>>>>>>>

 

//Environment :

# rpm -qa --last | egrep -i 'dbaastools_exa|dbcs'
dbaastools_exa-1.0-23.1.1.0.1_230113.0444.x86_64 Mon 30 Jan 2023 01:37:54 AM GMT
dbcs-agent-update-23.1.1.0.1-230113.0444.x86_64 Mon 30 Jan 2023 01:37:03 AM GMT
dbcs-admin-update-1.2-21.1.1.0.1_210324.2216.x86_64 Wed 16 Nov 2022 05:12:45 PM GMT
dbcs-agent-2.8OL7-22.3.1.0.1_220721.1435.x86_64 Wed 16 Nov 2022 04:29:06 PM GMT

///From dynamicscaling.old.log

2023-02-07 10:34:32: Scheduling Hr min '18' must be <= hr max '5', exiting...
2023-02-07 10:34:37: ================================================
2023-02-07 10:34:37: Dynamicscaling version '2.0.1-23' is starting...
2023-02-07 10:34:37: ================================================
2023-02-07 10:34:37: Getting Cloud VM Cluster shape Identifier
2023-02-07 10:34:37: Getting shape for 'ocid1.<OCID-ID>'
2023-02-07 10:34:38: shape_name: 'Exadata.X9M'
2023-02-07 10:34:38: Getting node count for 'ocid1.<OCID-ID>'
2023-02-07 10:34:39: ---------------------------
2023-02-07 10:34:39: Shape : 'Exadata.X9M'
2023-02-07 10:34:39: MaxOCPU : '124'
2023-02-07 10:34:39: ScaleFactor : '2'
2023-02-07 10:34:39: ---------------------------
2023-02-07 10:34:39: Scheduling data check
2023-02-07 10:34:39: Scheduling Hr min '18' must be <= hr max '5', exiting...>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>It should be less than max 5 hrs range only and you cant have 18 hrs range, I mean 6 am to 6 PM.
2023-02-07 10:34:45: ================================================
2023-02-07 10:34:45: Dynamicscaling version '2.0.1-23' is starting...
2023-02-07 10:34:45: ================================================
2023-02-07 10:34:45: Getting Cloud VM Cluster shape Identifier
2023-02-07 10:34:45: Getting shape for 'ocid1.<OCID-ID>'
2023-02-07 10:34:45: shape_name: 'Exadata.X9M'
2023-02-07 10:34:45: Getting node count for 'ocid1.<OCID-ID>'

 

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.