Power Consumption Target

• The cpuTargetWattsMaxValue attribute defines the server's expected maximum power consumption (in Watts).

  For example, on each 2-socket Oracle Exadata X11M database server with 192 CPU cores, cpuTargetWattsMaxValue=800. And, on a single-socket Oracle Exadata X11M-Z database server with 32 CPU cores, cpuTargetWattsMaxValue=240.

  You can view the prescribed value for each server by listing the attribute value. For example:

  DBMCLI> LIST DBSERVER attributes cpuTargetWattsMaxValue

• The cpuTargetWatts attribute controls the power consumption target for the server.

  By default, the power consumption target is disabled and the cpuTargetWatts attribute contains no value.

  You can specify the power consumption target by setting the attribute value. For example:

  DBMCLI> ALTER DBSERVER cpuTargetWatts=720

  When setting the cpuTargetWatts attribute, permitted values are between 50% and 100% of the server cpuTargetWattsMaxValue value in increments of 20 Watts for each server CPU socket.

  For example, on a 2-socket X11M database server with 192 CPU cores, where cpuTargetWattsMaxValue=800, you can set the cpuTargetWatts attribute to 400, 440, 480, and so on up to 800. And, on a single-socket X11M-Z database server with 32 CPU cores, where the cpuTargetWattsMaxValue=240, you can set the cpuTargetWatts attribute to 120, 140, 160, and so on up to 240.

  You can also disable the power consumption target by resetting the cpuTargetWatts attribute to NULL or to an empty string ("").

  At any time, you can view the current power consumption target by listing the attribute value. For example:

  DBMCLI> LIST DBSERVER attributes cpuTargetWatts

Low Power Mode

• The lowPowerModeSchedule attribute specifies a low power mode schedule on the server. You can set lowPowerModeSchedule as follows:

  lowPowerModeSchedule[+|-]=((startTimestamp="start-timestamp",durationMinutes=duration-in-minutes,frequency={daily|weekly})
                            [,(startTimestamp="start-timestamp",durationMinutes=duration-in-minutes,frequency={daily|weekly})]...)

  In the lowPowerModeSchedule definition:

  • startTimestamp: Specifies the start date and time for the low power mode period. The value must be specified as an ISO 8601 formatted timestamp. For example, "2025-01-03T18:00:00-07:00".

  • durationMinutes: Specifies the duration (in minutes) of the low power mode period. The maximum permitted value is 1440.

  • frequency: Specifies the frequency of the low power mode period. The permitted values are daily or weekly.

  You can use the += operator to add entries to an existing lowPowerModeSchedule definition, or use the -= operator to remove specific entries from an existing lowPowerModeSchedule definition. The = operator overwrites the previous attribute value.

  To remove all entries in the low power mode schedule, specify lowPowerModeSchedule=NULL.

• The lowPowerModeUntil attribute regulates the low power mode. The following values are permitted:

  • lowPowerModeUntil="end-timestamp": Manually switches on the low power mode until the specified time. The value must be specified as an ISO 8601 formatted timestamp. For example, "2025-01-10T23:30:00-07:00".

  • lowPowerModeUntil="" or lowPowerModeUntil=NULL: Immediately switches off the low power mode by setting. You can use this setting to switch off a scheduled low power mode period or a manually started period.

  • lowPowerModeUntil=NEVER: Immediately switches off the low power mode and disables the low power mode schedule.

    To re-enable the low power mode schedule, set the lowPowerModeUntil attribute to any value other than NEVER.

During any low power mode period, the system continually monitors itself to protect system performance. When any active workload is detected for five minutes, low power mode is automatically switched off. An active workload is characterized by any of the following:

• CPU utilization exceeds 30%.

• I/O utilization exceeds 30%.

• Throughput on the client network or RDMA Network Fabric exceeds 200 MB/sec.

When low power mode is automatically switched off because of an active workload, it remains off until the next scheduled period or until you manually switch it on.