You can configure your environment to use the load balancing advisory by defining service-level goals for each service for which you want to enable load balancing. Configuring a service-level goal enables the load balancing advisory and the publishing of FAN load balancing events for that service.
There are two types of service-level goals for run-time connection load balancing:
SERVICE_TIME
: Attempts to direct work requests to instances according to response time. Load balancing advisory data is based on elapsed time for work done in the service plus available bandwidth to the service. An example for the use of SERVICE_TIME
is for workloads such as internet shopping where the rate of demand changes. The following example shows how to set the goal to SERVICE_TIME
for connections using the online
service:
$ srvctl modify service -db db_unique_name -service online
-rlbgoal SERVICE_TIME -clbgoal SHORT
THROUGHPUT
: Attempts to direct work requests according to throughput. The load balancing advisory is based on the rate that work is completed in the service plus available bandwidth to the service. An example for the use of THROUGHPUT
is for workloads such as batch processes, where the next job starts when the last job completes. The following example shows how to set the goal to THROUGHPUT
for connections using the sjob
service:
$ srvctl modify service -db db_unique_name -service sjob
-rlbgoal THROUGHPUT -clbgoal LONG
Setting the run-time connection load balancing goal to NONE
disables load balancing for the service. You can see the goal settings for a service in the data dictionary by querying the DBA_SERVICES
, V$SERVICES
, and V$ACTIVE_SERVICES
views. You can also review the load balancing settings for a service using Oracle Enterprise Manager.
See Also:
"Administering Services" for more information about administering services and adding goals to services
Oracle Database 2 Day + Real Application Clusters Guide for more information about managing services using Oracle Enterprise Manager