![Single Client Access Name (SCAN) ,[object Object],[object Object],[object Object],[object Object],SCAN Back Office Front Office LOB Free](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Weitere ähnliche Inhalte
Andere mochten auch
Andere mochten auch (14)
Ähnlich wie SINGLE CLIENT ACCESS NAME (SCAN)
Ähnlich wie SINGLE CLIENT ACCESS NAME (SCAN) (20)
SINGLE CLIENT ACCESS NAME (SCAN)
- 1. Single Client Access Name (SCAN) 单一客户端访问名称
- 7. 连接的负载均衡 Clients SCAN Listeners Oracle RAC Database Application Server Local Listeners
- 8. 连接的负载均衡 Clients SCAN Listeners Oracle RAC Database Application Server Listeners
Hinweis der Redaktion
- 1. Define the SCAN in your corporate DNS (Domain Name Service) Use the Grid Naming Service (GNS) and the SCAN will be created during cluster configuration
- During install we will create a scan listener for each ip address defined to the SCAN name entered on the screen. Best Practice recommendation is 3, if you use GNS, you will get three However we will define one for each of the ip’s defined to the SCAN entered! NOTE: in a 2 node cluster, you will have 2 SCAN on one node ! Or 3 if the other node is down. Static IP allocation. Needs to be configured in DNS. Dhcp for scan vips => Requires GNS. Scan Listeners ae dispersed on the cluster IE they will try to be on different nodes NET will handle multiple ip addresses returned. Databases register with the SCAN. (Remote_listener) CRS resources are modelled for each scan listener ora.scan<n>.vip where n=1,2,3 ora.scan<n>.lsnr where n=1,2,3 ora.scan1.vip 1 ONLINE ONLINE stbpo38 ora.scan2.vip 1 ONLINE ONLINE stbpo37 ora.scan3.vip 1 ONLINE ONLINE stbpo36
- If you want both scan registration and other nodes listener registration use TNSNAMES like listeners_db.us.acme.com= (address_list= (address=(protocol=tcp)(host=scan-vip1)(port=1521)) (address=(protocol=tcp)(host=scan-vip2)(port=1521)) (address=(protocol=tcp)(host=scan-vip3)(port=1521)) (address=(protocol=tcp)(host=node1-vip)(port=1521)) (address=(protocol=tcp)(host=node2-vip)(port=1521)))
- ./srvctl status scan_listener SCAN Listener LISTENER_SCAN1 is enabled SCAN listener LISTENER_SCAN1 is running on node stbpo39 SCAN Listener LISTENER_SCAN2 is enabled SCAN listener LISTENER_SCAN2 is running on node stbpo40 SCAN Listener LISTENER_SCAN3 is enabled SCAN listener LISTENER_SCAN3 is running on node stbpo41
- Failover is on by default. Load Balance must be set. 5.2.56 TCP.CONNECT_TIMEOUT Purpose Use the TCP.CONNECT_TIMEOUT parameter to specify the time, in seconds, for a client to establish a TCP connection to the database server. If a TCP connection to the database host is not established in the time specified, the connect attempt is terminated. The client receives an ORA-12170 : TNS:Connect timeout occurred error. Without this parameter, a client connection request to the database server can block for the default duration of the TCP connect timeout (approximately 8 minutes on Linux) when the database server host system is unreachable. This parameter only applies to TCP connections ( PROTOCOL=tcp in the TNS connect address).
- This will have the instance register with the cman server as well as the SCAN listeners. You need all the scan VIPs registered so when you put them in a TNSNAMES, you must list the 3 VIPS in 3 address lines.