Oracle Cloud Infrastructure Documentation

Applying Resource Scheduler Schedules to the Oracle Base Database Service

Learn how apply Resource Scheduler schedules to Oracle Base Database Service.

You can use Resource Scheduler to manage Oracle Base Database Service instances by creating or editing schedules that include Oracle Base Database Service as an available option. However, before creating or updating a schedule to manage Oracle Base Database Service, note the following important considerations:

  • DBNode startup depends on the compute capacity, and Resource Scheduler can't guarantee a successful startup if the required compute capacity isn't available. If you experience startup issues, coordinate with the Compute Oncall or DB system Oncall teams for resolution.
  • Resource Scheduler starts DBNode start/stop operations and considers the schedule work request successful upon receiving an HTTP 200 status response. It doesn't wait for the DBNode operation to fully complete, as this process can take time and might be further delayed if issues at the compute data plane (DP) level occur. If Resource Scheduler were to wait for the DBNode request to complete, its worker nodes could become blocked, leading to increased wait times for other work requests. If you experience any issues during the DBNode work request, coordinate with the DB system Oncall team.

Permissions

To have the required permission to manage Oracle Base Database Service instances using Resource Scheduler, you must set one of the following policies:

Allow any-user to {DB_NODE_POWER_ACTIONS, DB_NODE_INSPECT, DB_NODE_QUERY, DB_SYSTEM_INSPECT, DB_HOME_INSPECT, DATABASE_INSPECT} IN TENANCY where all {request.principal.type='resourceschedule' , request.principal.id='<schedule_ocid>'}

or

Allow any-user to {DB_NODE_POWER_ACTIONS, DB_NODE_INSPECT, DB_NODE_QUERY, DB_SYSTEM_INSPECT, DB_HOME_INSPECT, DATABASE_INSPECT} IN COMPARTMENT ID <compartment_ocid> where all {request.principal.type='resourceschedule' , request.principal.id='<schedule_ocid>'}

where <schedule_ocid> is the OCID of the Resource Scheduler schedule that starts/stops the DB System.