Shulou(Shulou.com)06/01 Report--

What if the ora-12514 listener is not currently recognized? This problem may be often seen in our daily study or work. I hope you can gain a lot from this question. The following is the reference content that the editor brings to you, let's take a look at it!

Using PL/SQL to connect to the Oracle database in the virtual machine, it was found that the "ORA-12514 TNS listener currently does not recognize the request for service in the connection descriptor" error. After helping it solve, it is found that many people have encountered such problems, so it is written here.

Install Oracle in the virtual machine, and after the installation of Oracle, there is no configuration for listening, then the virtual machine starts again, there will be a problem of ORA-12514.

Here are the solutions: (recommended study: MySQL video tutorial)

It is determined that the client has not heard the instance service name according to the error message.

1. Start the database by restarting the service, and still cannot connect to the server if you connect again.

2. Since the first method can not solve the problem, then the second method. Consider listening to listener.ora

It is not necessary to specify the service name of the listening in the listening configuration file listener.ora (it is also not specified after installing Oracle10g). Normally, as long as the database is started, there is no problem for the client to connect to the database, but sometimes repeated startup and shutdown will also lead to ORA-12514 errors.

Since there is no listener specified in listener.ora, we can specify the instance name of the listener in the listener.ora file so that the problem should be able to connect.

Find and view the listener.ora file: located in the app folder directory of the oracle installation directory

Complete code

# listener.ora Network Configuration File: G:\ app\ admin\ product\ 12.1.0\ dbhome_1\ NETWORK\ ADMIN\ listener.ora# Generated by Oracle configuration tools. SID_LIST_LISTENER = (SID_LIST = (SID_NAME = CLRExtProc) (ORACLE_HOME = G:\ app\ admin\ product\ 12.1.0\ dbhome_1) (PROGRAM = extproc)) # add: (SID_DESC = (GLOBAL_DBNAME = ORCL) (ORACLE_HOME = G:\ app\ admin\ product\ 12.1.0\ dbhome_1) (SID_NAME = ORCL)) # = LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = 10.0.0.217) (PORT = 1521)) (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC1) ADR_BASE_LISTENER = G:\ app\ admin\ product\ 12.1.0\ dbhome_1\ log

SID_NAME corresponds to the name of the network service; GLOBAL_DBNAME corresponds to the name of the service. Restart the service after modification.

Thank you for reading! After reading the above, do you have a general understanding of what the ora-12514 listener does not recognize at present? I hope the content of the article will be helpful to all of you. If you want to know more about the relevant articles, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.