To support failover functionality, you can create a primary and a secondary LDAP server configuration object.
Each LDAP server configuration object connects to a single LDAP server and can be designated as a primary or secondary server. In the event the designated primary LDAP server configuration object is cannot connect to the LDAP server, the designated secondary LDAP server configuration object is used for user authentication. You can manually manage fail over and fail back using with SQL statements or be performed automatically by SAP Sybase IQ when it detects a change is appropriate.
Define primary and secondary LDAP server configuration objects in the login policy. For failover to occur, you must define both a primary and a secondary LDAP server configuration object. If only a primary LDAP server configuration object is defined in a login policy, failover does not occur. If a secondary LDAP server configuration object is defined with no primary LDAP server configuration object, the secondary LDAP server configuration object behaves as the primary LDAP server configuration object, and failover does not occur.
When designating the secondary LDAP server configuration object, you must configure the LDAP server configuration object to connect to the correct failover LDAP server. In the event of a failover, if the secondary LDAP server configuration object cannot connect to the secondary LDAP server, LDAP user authentication in SAP Sybase IQ will be unavailable.