Examine this command:
$ srvctl modify service -db RACDB -service SRVBl -clbgoal LONG
This three-Instance RAC database uses Flex ASM.
Which two statements are true regarding server-side connect-time load balancing using SCAN listeners for this service? (Choose two.)
A.
It is enabled only when LOAD_BALANCE=YES is coded in the client-side TNS entry used by the client.
B.
The SCAN listeners redirect clients to the node listener serving the instance that has the fewest sessions for theSRVB1service.
C.
The SCAN listeners automatically balance the connections across the instances accepting logins for theSRVB1service.
D.
It is disabled because the-c1bgoalattribute is set to LONG.
E.
The SCAN listeners redirect clients to the node listener serving the instance that has the fastest response time for theSRVB1service.
IMO
BC
A- enabled by default
D- enabled by default and LONG is the default CLBGoal
E- not on fast response time
I agree BC are correct.
not A: If you configured SCAN for connection requests, then client-side load balancing is not releant….
Yes B, Yes C, not E: Connections are distributed across instances based on the number of sessions in each instance…
not D: Can’t find -c1bgoalattribute
“-c1bgoalattribute” is misspelled “clbgoal attribute”.
FAN, Fast Connection Failover, and the load balancing advisory depend on an accurate connection load balancing configuration that includes setting the connection load balancing goal for the service. You can use a goal of either LONG or SHORT for connection load balancing. These goals have the following characteristics:
– SHORT: Use the SHORT connection load balancing method for applications that use run-time load balancing. When using connection pools that are integrated with Load Balancing Advisory, set the CLB_GOAL to SHORT. The following example modifies the service known as oltpapp, using SRVCTL to set the connection load balancing goal to SHORT:
$ srvctl modify service -db db_unique_name -service oltpapp -clbgoal SHORT
– LONG: Use the LONG connection load balancing method if run-time load balancing is not required. This is typical for batch operations. LONG is the default connection load balancing goal. The following is an example of modifying a service, batchconn, using SRVCTL to define the connection load balancing goal for long-lived sessions:
$ srvctl modify service -db db_unique_name -service batchconn -clbgoal LONG