1. Check whether the network ping host or IP is healthy and DNS is set correctly
2. Check firewall settings
3. Check the Listener.log log to see if there is a large number of connections attached.
4. Check if the Listener.log log file is too large, if it is too large to delete the restart after checking
5. View the V$session view to determine if there is a large number of session connections in a short period of time and locate the connected host.
Select Sid,serial#,osuser,username from v$session where status= ' ACTIVE ';
6. Check if there are some dbms_job on the connector, or the task is scheduled to run, sometimes the job execution is too frequent, so that the listener overload situation.
7. Change the short connection to a long connection (if the application is easy to change)
8. Restart the monitor or set up multiple monitors to do monitoring load balancing.
On the server side: Configure multiple listener, each listener to go different ports;
On the client side, configure the Tnsnames.ora file as follows:
Test =
(DESCRIPTION =
(Address_list =
(Load_balance=on)
(Failover=on)
(ADDRESS = (PROTOCOL = TCP) (HOST = 10.10.0.1) (PORT = 1521))
(ADDRESS = (PROTOCOL = TCP) (HOST = 10.10.0.1) (PORT = 1522))
(ADDRESS = (PROTOCOL = TCP) (HOST = 10.10.0.1) (PORT = 1523))
)
(Connect_data =
(service_name = test)
)
)
Tnsping Slow Problem Solving