Oracle RAC load balancing test (combined with server and client)

Oracle RAC Load Balancing allows connections initiated from clients to be effectively allocated to instances with low listener load. There are two methods to achieve load balancing on the client. One is to configure the load_balance of the client, and the other is to configure the remote_listener parameter on the server. The two methods have their own advantages and disadvantages, and they are not mutually exclusive. Therefore, the two methods can be combined to achieve load balancing more effectively. This article describes the use of the two (oralce 10g rac ).

For separate tests on Server Load balancer between clients, see:

Load Balance)

Oracle RAC server connection Load Balance)

The tests in this article combine the scripts and samples used in the previous article, which is a summary of the previous two tests.

I. Configuration Requirements

1. The listeners on each node on the server can provide services normally. If you use non-default port 1521, refer to the non-default port monitoring configuration in oracle rac (listener. ora tnsnames. ora)

1. Oracle @ bo2dbp: ~> More $ ORACLE_HOME/network/admin/listener. ora
2. # Listener. ora. bo2dbp Network Configuration File:/u01/oracle/db/network/admin/listener. ora. bo2dbp
3. # Generated by Oracle configuration tools.
5. LISTENER_BO2DBP =
6. (DESCRIPTION_LIST =
7. (DESCRIPTION =
8. (ADDRESS = (PROTOCOL = TCP) (HOST = bo2dbp-vip.2gotrade.com) (PORT = 1521) (IP = FIRST ))
9. (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.7.51) (PORT = 1521) (IP = FIRST ))
10. )
11. )
13. SID_LIST_LISTENER_BO2DBP =
14. (SID_LIST =
15. (SID_DESC =
16. (SID_NAME = PLSExtProc)
17. (ORACLE_HOME =/u01/oracle/db)
18. (PROGRAM = extproc)
19. )
20. )
22. Oracle @ bo2dbp: ~> Lsnrctl status
23. Service "GOBO4" has 2 instance (s ).
24. Instance "GOBO4A", status READY, has 2 handler (s) for this service...
25. Instance "GOBO4B", status READY, has 1 handler (s) for this service...

2. remote_listener parameter settings on the server

The connection identifier of the remote_listener parameter is required to have corresponding entries in tnsnames. ora on the server side.

1. SQL> show parameter listener
3. NAME TYPE VALUE
4. -----------------------------------------------------------------------------
5. Local_listener string
6. Remote_listener string remote_lsnr_gobo4
8. Oracle @ bo2dbp: ~> More $ ORACLE_HOME/network/admin/tnsnames. ora
9. # Tnsnames. ora Network Configuration File:/u01/oracle/db/network/admin/tnsnames. ora
10. # Generated by Oracle configuration tools.
11. Remote_lsnr_gobo4 =
12. (ADDRESS_LIST =
13. (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.7.61) (PORT = 1521 ))
14. (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.7.62) (PORT = 1521 ))
15. )

3. Enable load_balance in client tnsnames. ora

1. Oracle @ SZDB: ~> Tail-11 $ ORACLE_HOME/network/admin/tnsnames. ora
3. GOBO4 =
4. (DESCRIPTION =
5. (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.7.61) (PORT = 1521 ))
6. (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.7.62) (PORT = 1521 ))
7. (LOAD_BALANCE = yes)
8. (CONNECT_DATA =
9. (SERVER = DEDICATED)
10. (SERVICE_NAME = GOBO4)
11. )
12. )

1 2 Next Page