nutriwhe.blogg.se

In the preceding examples, Oracle Net waits for 60 seconds for each full connection to receive a response, after which it assumes that a failure occurred and retries the next address in the ADDRESS_LIST. The value of these parameters is expressed in seconds. Remote_listeners=:5221įor example, when using remote listeners pointing to VIPs at the database: = (TRANSPORT_CONNECT_TIMEOUT=3)(CONNECT_TIMEOUT=60) Oracle Net Services enables you to add the CONNECT_TIMEOUT, RETRY_COUNT, and TRANSPORT_CONNECT_TIMEOUT parameters to the tnsnames.ora connection string.įor example, when using SCAN addresses for the remote listeners at the database: = $ srvctl modify service -db db_unique_name -service batchconn -clbgoal LONG The following is an example of modifying a service, batchconn, using SRVCTL to define the connection load balancing goal for long-lived sessions: LONG is the default connection load balancing goal. LONG: Use the LONG connection load balancing method if run-time load balancing is not required. $ srvctl modify service -db db_unique_name -service oltpapp -clbgoal SHORT

The following example modifies the service known as oltpapp, using SRVCTL to set the connection load balancing goal to SHORT: When using connection pools that are integrated with Load Balancing Advisory, set the CLB_GOAL to SHORT. SHORT: Use the SHORT connection load balancing method for applications that use run-time load balancing. These goals have the following characteristics: You can use a goal of either LONG or SHORT for connection load balancing. Note: If you set the REMOTE_LISTENER parameter manually, then set this parameter to scan_name : scan_port.įAN, 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.