"ORACLE" ORA-12537 problem collation

ORA-12537 is mainly oralce monitoring problems, today to help colleagues deal with problems, he asked a situation, began to connect very normal, the subsequent occurrence of ORA-12537 problems

Simply tidy up the next

General conditions of use1-Check whether the database server has not started monitoring2-Check that the listener file configured by the client Tnsnames.ora is correct,oracle\product\10.2.0\db_1\network\admin\tnsnames.ora concern IP, port, SIDIt is important to note that there are no spaces in front of the service name, such as orcl_32.21orcl_32.21 =(DESCRIPTION =(address_list =(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.32.21) (PORT = 1521))    )(Connect_data =(service_name = ORCL)    )  ) The third situation, is Niger at the same time before the beginning can be, the subsequent is not the hint ORA-12537, the problem is because the Listener.log file too large caused,Listener.log already has several g, causing the write log too large to cause the listener to not work, clean up the Listener.log file problem can be resolved here are the methods available to friends online excerpt from: http://blog.itpub.net/10314474/viewspace-694404/Normal 0 0 2 false false en- US zh-tw x-none processing

1. Delete ... \product\10.2.0\db_1\network\log under listener.log (or rename to back up ), restartthe listener

Rename Listener.log Listener.old

Lsnrctl stop

Lsnrctl start

2. The previous method will interrupt the use of the database, in order to minimize the database outage time, with the first shutdown and then turn on the Listener log function method

Lsnrctl set Log_status off

Rename Listener.log Listener.old

LSNRCL set Log_status on

after using either of the two methods, the Listener.log has been re-created

"ORACLE" ORA-12537 problem collation