skip to main content
Part 1: Getting Started : Advanced Features : Using Failover : Using Connection Retry
  
Using Connection Retry
Connection retry is available in the following DataDirect Connect Series for ODBC drivers:
*DB2 Wire Protocol
*Greenplum Wire Protocol
*Informix Wire Protocol
*MySQL Wire Protocol
*Oracle Wire Protocol
*Oracle
*PostgreSQL Wire Protocol
*Progress OpenEdge Wire Protocol
*SQL Server Wire Protocol
*SQL Server Legacy Wire Protocol (UNIX only)
*Sybase Wire Protocol
*Sybase IQ Wire Protocol
Connection retry defines the number of times the driver attempts to connect to the primary server and, if configured, alternate database servers after the initial unsuccessful connection attempt. It can be used with connection failover, extended connection failover, and select failover. Connection retry can be an important strategy for system recovery. For example, suppose you have a power failure in which both the client and the server fails. When the power is restored and all computers are restarted, the client may be ready to attempt a connection before the server has completed its startup routines. If connection retry is enabled, the client application can continue to retry the connection until a connection is successfully accepted by the server.
Connection retry can be used in environments that have only one server or can be used as a complementary feature with connection failover in environments with multiple servers.
Using the connection options Connection Retry Count and Connection Retry Delay, you can specify the number of times the driver attempts to connect and the time in seconds between connection attempts. For details on configuring connection retry, see the appropriate driver chapter in this book.