Symptoms occur: ORA-12514 TNS listener not recognize the current connection request descriptor or service follows:
Application exceptions, can not connect to the database. Landing database server, view the monitor has been broken. Try to restart the listener, fail to reboot. Check to see whether the size of the monitor log listener.log more than 4G.
Solution:
Delete listener.log (you can do first before you delete the backup), and then restart the listener. Automatically creates a new log file after listening to restart.
supplement:
In the monitoring process is running, you can not do listener.log delete or rename operation.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
A, cmd command to open the input lsnrctl, View show log_file log路径 状态 show log_status和所在目录 show log_directory
二、set log_status off
The first way: first the state stopped the log, so you do not write the listener log (monitor the operation of this operation in the open state due to the listener logging is too large, need to wait 15-25 minutes)
The second way: manually shut down the monitoring service and start the service
Third, the backup or remove listeners log (turn off OracleOraDb11g_home1TNSListener Service)
The path D: \ app \ oracle \ diag \ tnslsnr \ wiz-db-03 \ listener \ trace listener.log (see the installation path personal decision)
Make a backup listener.log monitor logs, and then deletes the original log listener.log. four. set log_status on # to re-open the log and began recording the listener log. The file is automatically created (monitor operations in the open state)
Fives. Check the status of listener status #
本文来自：https://blog.csdn.net/qiu_spring/article/details/88746958