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

Oracle 11g ORA-12514:TNS: The listener currently does not recognize the service requested in the connection descriptor

Solution process:

1. Find the listener.ora listening file, specific location: D:\app\Administrator\product\11.2.0\dbhome_1\NETWORK\ADMIN\listener.ora

2. Found in lisener.ora file

(SID_DESC =

(SID_NAME = CLRExtProc)

(ORACLE_HOME = D:\app\Administrator\product\11.2.0\dbhome_1)

(PROGRAM = extproc)

(ENVS = "EXTPROC_DLLS=ONLY:D:\app\Administrator\product\11.2.0\dbhome_1\bin\oraclr11.dll")

)

Copy the following paragraph and modify it appropriately. (The red part is your SID, where GLOBAL_DBNAME is the global database name, which can be different from SID)

(SID_DESC =

(GLOBAL_DBNAME = ORAC11)

(ORACLE_HOME = D:\app\Administrator\product\11.2.0\dbhome_1)

(SID_NAME = ORAC11)

)

3. Save the listener.ora file, close and restart the listener.

lsnrctl stop //Close

lsnrctl start //start

4. At this point, a new error occurs when connecting pairs with normal users.

ORA-27101: shared memory realm does not exist

5. Open the directory D:\app\Administrator\admin\orac11\pfile and you will find a file init.ora.1052011103553, which is the startup file backed up when Oracle was last successfully started.

6. sqlplus /nolog，

create spfile from pfile='D:\app\Administrator\admin\orac11\pfile\init.ora.1052011103553'

startup //Start the database.

7. Everything's back to normal.

ORA-12514 has a number of causes for error. But nothing more than these:

1) ORA-12541: TNS: No monitor

Obviously, the server-side listener is not started, and check whether the client IP address or port is filled in correctly. Start the listener:

$ lsnrctl start or

C:lsnrctl start

ORA-12154: TNS: Unable to process service name

Check that the entered service name matches the configured service name. Also note that the generated local service name file (such as D:oracleora92networkadmin tnsnames.ora under Windows,/network/admin/tnsnames.ora under Linux/Unix) cannot have a space before the first line of service name of each service.

ORA-12514: TNS: The listening process cannot resolve the SERVICE_NAME given in the connection descriptor.

Open Net Manager, check the service name, and check that the service name is entered correctly in the Service ID column. The service name must match the global database name configured for the server-side listener. Also check sqlnet.ora, for example, if you want to connect in an easy way, you need to add EZCONNECT to the NAMES.DIRECTORY_PATH parameter.

Ora-12514: TNS: The listener currently does not recognize the service requested in the link descriptor

This problem is caused by the missing SID_LIST descriptor for the listener. This problem is often encountered when configuring with netca. The example of listener.ora is as follows

SID_LIST_LISTENER =

(SID_LIST =

(SID_DESC =

(SID_NAME = PLSExtProc)

(ORACLE_HOME = /opt/oracle/product/9.2.0.4)

(PROGRAM = extproc))

(SID_DESC =

(GLOBAL_DBNAME = SAMPLE.COM)

(ORACLE_HOME = /opt/oracle/product/9.2.0.4)

(SID_NAME = SAMPLE)))LISTENER =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = tcy.com)(PORT = 1521)))

//Solutions

1. cmd Enter sqlplus / as sysdba

2. Added process and session restart services

3. Modify the LISTENER.OAR file Add

(SID_DESC =

(GLOBAL_DBNAME = orcl)

(ORACLE_HOME = f:\app\MY\product\11.2.0\dbhome_1)

(SID_NAME = orcl)

)

4. Modify tnsname.ora

(CONNECT_DATA =

(SERVER = dedicate)

(SERVICE_NAME = orcl)

)

dedicate

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.