skip to main content
Using the ADO Client : Configuring Connection Failover : Connection Failover Attributes
 

Connection Failover Attributes

The following table summarizes the connection attributes that control how connection failover works with the ADO Client.
 
Table 5: Summary: Connection Failover Attributes for the ADO Client  
Attribute
Characteristic
Alternate Servers
A list of alternate OpenAccess SDK servers to which the data provider will attempt to connect if the primary OpenAccess SDK server is unavailable. A port number and an IP address or server name identifying each server are required.
If the primary OpenAccess SDK server is an LDAP server, each alternate server must be an LDAP server.
Connection Retry Count
Number of times the data provider retries the primary database server, and if specified, alternate servers until a successful connection is established. The default is 5.
Connection Retry Delay
Wait interval, in seconds, between connection retry attempts when the ConnectionRetryCount attribute is set to a positive integer. The default is 1.
Host
The TCP/IP address or server name of primary OpenAccess SDK server.
LDAP: If LDAP is enabled, this identifies the TCP/IP address of the LDAP server. This can also be a list of LDAP servers separated by a blank space (for example, “ld1.foo.com ld2.foo.com ld3.foo.com”). If the first LDAP server in the list does not respond, the ADO Client will try to connect to the next LDAP server in the list.
Load Balancing
Sets whether the data provider will use client load balancing in its attempts to connect to the list of database servers (primary and alternate). If client load balancing is enabled, the driver uses a random pattern instead of a sequential pattern in its attempts to connect. The default is 0 (client load balancing is disabled).
Port
Port listening for connections on the primary OpenAccess SDK server.
If LDAP is enabled, this identifies the TCP/IP port on which the LDAP server is listening. If you do not specify a port, the default port for LDAP (389) will be used.
See Configuring Connection Failover and Using Client Load Balancing for overviews of connection failover and client load balancing.