Anatomy of 11g R2 SCAN connection via DNS
Hi
Can someone please verify if this is EXACTLY how the client connection works against a 11g R2 SCAN (using DNS) ?
1. When a client establish / Initiate a connection request, it hits the DNS server on the scan name
2. DNS (using round robin IP address assignment randomly) will route the IP address(es) associated with the SCAN name to the client
3. Client will go through the list (of IP) and will RANDOMLY try connecting to a SCAN_LISTENER. If It cannot connect to first one, it will try second one and so on
4. Each SCAN LISTENER keeps updated cluster load statistics and will route the information to the client as to which node to connect, ie. the least loaded node
Can someone please verify if this is EXACTLY how the client connection works against a 11g R2 SCAN (using DNS) ?
1. When a client establish / Initiate a connection request, it hits the DNS server on the scan name
2. DNS (using round robin IP address assignment randomly) will route the IP address(es) associated with the SCAN name to the client
3. Client will go through the list (of IP) and will RANDOMLY try connecting to a SCAN_LISTENER. If It cannot connect to first one, it will try second one and so on
4. Each SCAN LISTENER keeps updated cluster load statistics and will route the information to the client as to which node to connect, ie. the least loaded node
0