I had this issue and the fix was to make sure in tnsnames.ora
the SERVICE_NAME
is a valid service name in your database. To find out valid service names, you can use the following query in oracle:
select value from v$parameter where name='service_names'
Once I updated tnsnames.ora
to:
TEST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = *<validhost>*)(PORT = *<validport>*))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = *<servicenamefromDB>*)
)
)
then I ran:
sqlplus user@TEST
Success!
The listener is basically telling you that whatever service_name you are using isn’t a valid service according to the DB.
(*I was running sqlplus from Win7 client workstation to remote DB and blame the DBAs *)
answered Apr 16, 2013 at 23:36
Brad RippeBrad Rippe
3,3471 gold badge18 silver badges20 bronze badges
11
I know this is an old question, but still unanswered. It took me a day of research, but I found the simplest solution, at least in my case (Oracle 11.2 on Windows 2008 R2) and wanted to share.
The error, if looked at directly, indicates that the listener does not recognize the service name. But where does it keep service names? In %ORACLE_HOME%NETWORKADMINlistener.ora
The «SID_LIST» is just that, a list of SIDs and service names paired up in a format you can copy or lookup.
I added the problem Service Name, then in Windows «Services» control panel, I did a «Restart» on the Oracle listener service. Now all is well.
For example, your listener.ora file might initially look like:
# listener.ora Network Configuration File: C:apporacle_userproduct12.1.0dbhome_1networkadminlistener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = C:apporacle_userproduct12.1.0dbhome_1)
(PROGRAM = extproc)
(ENVS = "EXTPROC_DLLS=ONLY:C:apporacle_userproduct12.1.0dbhome_1binoraclr12.dll")
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
)
)
… And to make it recognize a service name of orcl
, you might change it to:
# listener.ora Network Configuration File: C:apporacle_userproduct12.1.0dbhome_1networkadminlistener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = C:apporacle_userproduct12.1.0dbhome_1)
(PROGRAM = extproc)
(ENVS = "EXTPROC_DLLS=ONLY:C:apporacle_userproduct12.1.0dbhome_1binoraclr12.dll")
)
(SID_DESC =
(GLOBAL_DBNAME = orcl)
(ORACLE_HOME = C:apporacle_userproduct12.1.0dbhome_1)
(SID_NAME = orcl)
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
)
)
Kevin
74.6k12 gold badges131 silver badges165 bronze badges
answered Mar 25, 2014 at 12:13
3
In my circumstances the error was due to the fact the listener did not have the db’s service registered. I solved this by registering the services. Example:
My descriptor in tnsnames.ora
:
LOCALDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = LOCALDB)
)
)
So, I proceed to register the service in the listener.ora
manually:
SID_LIST_LISTENER =
(SID_DESC =
(GLOBAL_DBNAME = LOCALDB)
(ORACLE_HOME = C:Oracleproduct11.2.0dbhome_1)
(SID_NAME = LOCALDB)
)
Finally, restart the listener by command:
> lsnrctl stop
> lsnrctl start
Done!
answered May 31, 2017 at 23:39
manixmanix
14.4k11 gold badges69 silver badges106 bronze badges
1
I had this issue at Windows server 2008 R2 and Oracle 11g
go to Net Manager > Listener > select database services form the combox > «Global Database Name» must be same as «SID» and «Oracle Home Directory» must be correct.
If you don’t have any entry for database services, create one and set correct global database , sid
and oracle home.
Mr_and_Mrs_D
31.8k37 gold badges178 silver badges357 bronze badges
answered Dec 21, 2013 at 14:27
SepidehSepideh
1491 silver badge2 bronze badges
1
This really should be a comment to Brad Rippe’s answer, but alas, not enough rep. That answer got me 90% of the way there. In my case, the installation and configuration of the databases put entries in the tnsnames.ora file for the databases I was running. First, I was able to connect to the database by setting the environment variables (Windows):
set ORACLE_SID=mydatabase
set ORACLE_HOME=C:Oracleproduct11.2.0dbhome_1
and then connecting using
sqlplus / as sysdba
Next, running the command from Brad Rippe’s answer:
select value from v$parameter where name='service_names';
showed that the names didn’t match exactly. The entries as created using Oracle’s Database Configuration Assistant were originally:
MYDATABASE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = mylaptop.mydomain.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = mydatabase.mydomain.com)
)
)
The service name from the query was just mydatabase
rather than mydatabase.mydomain.com
. I edited the tnsnames.ora file to just the base name without the domain portion so they looked like this:
MYDATABASE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = mylaptop.mydomain.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = mydatabase)
)
)
I restarted the TNS Listener service (I often use lsnrctl stop
and lsnrctl start
from an administrator command window [or Windows Powershell] instead of the Services control panel, but both work.) After that, I was able to connect.
answered Dec 19, 2016 at 14:38
Capricorn1Capricorn1
8199 silver badges17 bronze badges
1
Starting the OracleServiceXXX from the services.msc worked for me in Windows.
answered Jun 16, 2015 at 7:48
1
For thoses Who are using spring-boot and jdbc for connection.
You have to be careful while writing jdbcUrl in application.properties
With SID in Database connection —
source.datasource.jdbcUrl = jdbc:oracle:thin:@[HOST][:PORT]:SID
With Service name in db connection
globe.datasource.jdbcUrl = jdbc:oracle:thin:@//[HOST][:PORT]/SERVICE
This worked for me
answered Jun 16, 2020 at 8:18
surajmallsurajmall
1581 silver badge7 bronze badges
For Dbeaver users: try selecting «SID» instead of «Service name» in connection settings.
answered Aug 30, 2021 at 6:49
JanBrusJanBrus
1,1489 silver badges13 bronze badges
1
I had the same problem. For me, just writing
sqlplus myusername/mypassword@localhost
did the trick, doing so makes it connect to the default service name, I guess.
answered Sep 9, 2014 at 4:01
HosseinHossein
23.9k34 gold badges119 silver badges222 bronze badges
2
This error can occur when an application makes a new connection for every database interaction or the connections are not closed properly. One of the free tools to monitor and confirm this is Oracle Sql developer (although this is not the only tool you can use to monitor DB sessions).
you can download the tool from oracle site Sql Developer
here is a screenshot of how to monitor you sessions. (if you see many sessions piling up for your application user during when you see the ORA-12514 error then it’s a good indication that you may have connection pool problem).
answered Apr 1, 2013 at 0:21
grepitgrepit
20.8k6 gold badges101 silver badges81 bronze badges
Check to see the database is up. Log onto the server, set the ORACLE_SID environment variable to your database SID, and run SQL*Plus as a local connection.
answered May 29, 2012 at 0:50
DCookieDCookie
42.5k11 gold badges83 silver badges91 bronze badges
1
I resolved this issue in my linux enviroment updating the IP of my machine in /etc/hosts file.
You can verify your network IP (inet end.) with:
$ifconfig
See if your IP matches with /etc/hosts file:
$cat /etc/hosts
Edit your /etc/hosts file, if nedded:
$sudo gedit /etc/hosts
Bye.
answered Sep 3, 2014 at 15:27
2
what worked for me was really simple, I just needed to initiate the service manually in the «Windows Services» (services.msc in cmd trompt).
my service name is: OracleServiceXXXXX.
answered May 12, 2016 at 13:57
isabelle martzisabelle martz
1711 gold badge3 silver badges12 bronze badges
1
I had also faced the same problem and spent 3 days to dig it out.
This happens because of your wrong TNS service entry.
First check whether you are able to connect to standby database from primary database using sql > sqlplus sys@orastand as sysdba
(orastand
is a standby database).
If you are not able to connect then it is a problem with the service. Correct the entry of service name in TNS file at primary end.
Check standby database the same way. Make the changes here too if required.
Make sure the log_archive_dest_2
parameter has the correct service name.
Gryu
2,0622 gold badges16 silver badges29 bronze badges
answered Jun 26, 2014 at 6:41
For those that may be running Oracle in a VM (like me) I saw this issue because my VM was running out of memory, which seems to have prevented OracleDB from starting up/running correctly. Increasing my VM memory and restarting fixed the issue.
answered Apr 14, 2016 at 18:14
th3uiguyth3uiguy
1,8791 gold badge12 silver badges8 bronze badges
Lots of answers here, but here comes a working example with code that you can copy and paste and test immediately:
For me the error 12514 was solved after specifying the correct SERVICE_NAME.
You find that on the server in the file tnsnames.ora
which comes with 3 predefined service names (one of them is «XE»).
- I installed the Oracle Express database OracleXE112 which already comes with some preinstalled demo tables.
- When you start the installer you are asked for a password. I entered «xxx» as password. (not used in production)
- My server runs on the machine 192.168.1.158
- On the server you must explicitely allow access for the process TNSLSNR.exe in the Windows Firewall. This process listens on port 1521.
- OPTION A: For C# (.NET2 or .NET4) you can download ODAC11, from which you have to add Oracle.DataAccess.dll to your project. Additionally this DLL depends on: OraOps11w.dll, oci.dll, oraociei11.dll (130MB!), msvcr80.dll.
These DLLs must be in the same directory as the EXE or you must specify the DLL path in:HKEY_LOCAL_MACHINESOFTWAREOracleODP.NET4.112.4.0DllPath
. On 64 bit machines write additionally toHKLMSOFTWAREWow6432NodeOracle...
- OPTION B: If you have downloaded ODAC12 you need Oracle.DataAccess.dll, OraOps12w.dll, oci.dll, oraociei12.dll (160MB!), oraons.dll, msvcr100.dll. The Registry path is
HKEY_LOCAL_MACHINESOFTWAREOracleODP.NET4.121.2.0DllPath
- OPTION C: If you don’t want huge DLL’s of more than 100 MB you should download ODP.NET_Managed12.x.x.x.xxxxx.zip in which you find
Oracle.ManagedDataAccess.dll
which is only 4 MB and is a pure managed DLL which works in 32 bit and 64 bit processes as well and depends on no other DLL and does not require any registry entries. - The following C# code works for me without any configuration on the server side (just the default installation):
using Oracle.DataAccess.Client; or using Oracle.ManagedDataAccess.Client; .... string oradb = "Data Source=(DESCRIPTION=" + "(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.158)(PORT=1521)))" + "(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=XE)));" + "User Id=SYSTEM;Password=xxx;"; using (OracleConnection conn = new OracleConnection(oradb)) { conn.Open(); using (OracleCommand cmd = new OracleCommand()) { cmd.Connection = conn; cmd.CommandText = "select TABLESPACE_NAME from DBA_DATA_FILES"; using (OracleDataReader dr = cmd.ExecuteReader()) { while (dr.Read()) { listBox.Items.Add(dr["TABLESPACE_NAME"]); } } } }
If the SERVICE_NAME=XE
is wrong you get error 12514. The SERVICE_NAME
is optional. You can also leave it away.
answered Apr 20, 2017 at 21:19
ElmueElmue
7,4422 gold badges46 silver badges57 bronze badges
1
In my case the database had ran out of disk space. Which caused it to not respond. Once I cleared up that issue everything worked again.
answered Apr 20, 2014 at 2:12
Pete BrummPete Brumm
1,65619 silver badges13 bronze badges
1
I got the same error because the remote SID specified was wrong:
> sqlplus $DATASOURCE_USERNAME/$DATASOURCE_PASSWORD@$DB_SERVER_URL/$REMOTE_SID
I queried the system database:
select * from global_name;
and found my remote SID («XE»).
Then I could connect without any problem.
answered Oct 13, 2017 at 10:55
In my case, round brackets around the SERVICE_NAME was missing in the tnsnames.ora file.
<DBNAME> =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL=TCP)(HOST = nupark-cnvr-ora )(PORT=1521))
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = <DBNAME> ***CLOSING ROUND BRACKET WAS MISSING HERE***
)
)
LISTENER_<DBNAME> =
(ADDRESS = (PROTOCOL = TCP)(HOST = nupark-cnvr-ora)(PORT = 1521))
answered Mar 10, 2020 at 17:59
Mosab SasiMosab Sasi
1,1308 silver badges11 bronze badges
I had just to replace my connection string
from:
jdbc:oracle:thin:@localhost:1521:xe
To:
jdbc:oracle:thin:@localhost:1521:orcl
Steven
1,9253 gold badges21 silver badges33 bronze badges
answered Oct 27, 2022 at 2:49
For me this was caused by using a dynamic ipadress using installation. I reinstalled Oracle using a static ipadress and then everything was fine
answered Dec 3, 2016 at 7:45
SteefSteef
5615 silver badges20 bronze badges
Restarting the VM worked for me
answered Mar 20, 2019 at 3:35
wishmanwishman
7744 gold badges14 silver badges31 bronze badges
My issue was resolved by replacing the’SID’ in URL with ‘service name’ and correct host.
answered Aug 23, 2019 at 13:47
Sir. HedgehogSir. Hedgehog
1,2503 gold badges17 silver badges39 bronze badges
tnslsnr
is up but database is down.
For oracle novice it is not obvious that database may be down while connections are accepted.
I had to start up database manually like that
su - oracle
export ORACLE_SID=XE
sqlplus sys as sysdba
And then in sql console
startup
In my case i failed to startup but got another error message and found the source of a problem — i had to change host name and then database auto startup was functional again.
answered Nov 11, 2019 at 9:38
user3132194user3132194
2,32123 silver badges17 bronze badges
I have implemented below workaround to resolve this issue.
-
I have set the ORACLE_HOME using command prompt
(right click cmd.exe and Run as System administrator). -
Used below command
set oracle_home="path to the oracle home"
-
Go to All programs —> Oracle -ora home1 —> Configuration migration tools —> Net Manager —> Listener
-
Select Database Services from dropdown.
Both Global database name and SID are set to the same (ORCL in my case).
Set Oracle Home Directory.
Oracle Net Manager window example from oracle documentation:
- Click on File and save network configuration.
Gryu
2,0622 gold badges16 silver badges29 bronze badges
answered Nov 29, 2017 at 12:34
Raman BRaman B
3314 silver badges5 bronze badges
The problem was that my connection string url contained database name instead of SID.
Replacing database name with oracle database connection SID solved this problem.
To know your oracle SID’s you can browse tnsnames.ora
file.
XE
was the actual SID, so this is how my tomcat connection string looks like now:
<Resource
name="jdbc/my_db_conn"
auth="Container"
type="javax.sql.DataSource"
driverClassName="oracle.jdbc.driver.OracleDriver"
url="jdbc:oracle:thin:@//127.0.0.1:1521/XE"
username="test_user"
password="test" />
My server version was «Oracle 11.2 Express», but solution should work on other versions too.
answered Dec 5, 2019 at 12:07
BenasBenas
2,0362 gold badges39 silver badges65 bronze badges
I had a case that I used DBMS where I had to fulfill a db connection form.
I put SID into the Database field and in the dropdown, next to the field, I had had ‘Service Name’ value instead of ‘SID’ value.
(normally I don’t use Oracle database so I’ve not been aware of the difference)
That was the reason I got the error message.
answered Jul 28, 2020 at 16:02
BronekBronek
10.6k2 gold badges45 silver badges46 bronze badges
The problem can be in the incorrect URL.
For example, I’m using Oracle database (inside VM) with Spring framework and having this issue.
I had in my application.properties file:
spring.datasource.url=jdbc:oracle:thin:@//localhost:1521/orcl12c
But the db version was defferent:
spring.datasource.url=jdbc:oracle:thin:@//localhost:1521/orclcdb
The correct URL can be found in the tnsnames.ora file (this file would be available where the Oracle server, so if you using VM, you should look for this file inside your host VM).
For example for Oracle in the VirtualBox the command to see this file is:
nano /u01/app/oracle/product/version/db_1/network/admin/tnsnames.ora
Dharman♦
30.4k22 gold badges84 silver badges132 bronze badges
answered Apr 17, 2021 at 21:59
x3hreex3hree
811 gold badge2 silver badges4 bronze badges
In my case for Linux environment, the oracle file at ORACLE_HOME/bin
was highlighted in «Red» color with different permissions as below:
I changed the permissions of this file as below:
1) Stop Oracle -> sudo systemctl stop oracle.service
2) Change the permission of oracle file at ORACLE_HOME/bin
directory as «sudo chmod 777 oracle«
3) Start Oracle -> sudo systemctl start oracle.service
Then after this change, I checked the status of listener using lsnrctl status.Here, I can see the db instances loaded successfully.
However, I can connect using sqldeveloper only, with sqlplus command line I’m getting ORA-12547: TNS Lost Contact
error. So, this can a quick workaround to use sqldeveloper.
Note: Take a backup of oracle file before changing the permissions.
answered Aug 11, 2021 at 13:49
Rohit GaikwadRohit Gaikwad
3,6473 gold badges17 silver badges40 bronze badges
This is a tricky Oracle error, as it can have lots of possible causes.
It seems to mean that something in this chain of events is failing:
- Look up the service name in tnsnames.ora
- Connect to the host in the tnsnames entry
- Reach the listener on that host
- Tell the listener that you want to connect to the service specified in the tnsnames entry
Anything that throws that off can cause this error, from a missing bracket in tnsnames.ora, to a connecting to the wrong database host.
If tnsping works, that rules some things out, as it means that we can look up the entry in tnsnames, connect to the host, and contact the listener … so we know, for instance, that the host at least exists, and there is an Oracle listener running there; but the listener is saying the service name is not known. That still leaves a lot of possibilities like:
- service name in tnsnames.ora is just wrong
- database instance is not running and/or not registered with the listener
- we’re connecting to the wrong Oracle host
- we’re connecting to the wrong listener (wrong port) on the correct Oracle host
- firewall/networking issue (apparently it’s possible that a firewall could allow tnsping packets through but block other client applications from connecting)
I’ve seen an ORA-12514 with tiny typos in tnsnames.ora … like incorrect indenting. But I suspect tnsping wouldn’t succeed if that is the issue.
When I encountered this most recently, it was due to the 3rd bullet-point above; we were connecting to an Oracle database host — just not the right host; we had to ensure that the hostname in the tnsnames entry was for the Oracle database server that was hosting this particular database service.
Connecting to the Oracle host and running lsnrctl status
can help check that the service is known to this listener. Remember that lsnrctl
by default checks the default listener name. You may need to check listener.ora to see if there are other names listeners in this database instance.
answered Apr 7 at 18:27
em_boem_bo
6246 silver badges13 bronze badges
Ok everything worked fine till yesterday now i am suddenly getting this error
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
nothing had been modified
XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = jainam-2b1c493d)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
)
)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
)
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)
ORACLR_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
)
(CONNECT_DATA =
(SID = CLRExtProc)
(PRESENTATION = RO)
)
)
I am totally stuck and have no idea what to do.
I tried help from here
http://dba-oracle.com/t_ora_12514_tns_listener_does_not_currently_know_service_requested.htm
but no use.
Thanks
EDIT:
here’s the output to lsnrctl service
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 3 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
"ORACLE SERVER" established:0 refused:0 current:0 max:25 state:ready
CLRExtProc
(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\.pipeNTN_6B4_641B624E_B22.ORA))
"ORACLE SERVER" established:0 refused:0 current:0 max:25 state:ready
CLRExtProc
(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\.pipeNTN_6B4_641B624E_282.ORA))
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1022 state:ready
DISPATCHER <machine: JAINAM-2B1C493D, pid: 3708>
(ADDRESS=(PROTOCOL=tcp)(HOST=jainam-2b1c493d)(PORT=2763))
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
The command completed successfully
null
ORA-12514 при подключении к экземпляру Oracle
Причин по которым может возникнуть ошибка ORA-12514 много, я расскажу об одной из возможных с предисторией.
У нашего заказчика развернут Oracle 11.2 на Windows Server.
При предоставлении заказчиком учётных данных для подключения нас насторожил обязательный формат логина SQLplus с явным указанием идентификатора соединения (connect_identifier)
sqlplus sys/pass@connect_identifier as sysdba
В процессе проведения работ нам потребовалось запустить базу данных в NOMOUNT через shutdown immediate,
C:Windowssystem32>sqlplus sys/pass@connect_identifier as sysdba SQL*Plus: Release 11.2.0.1.0 Production on *** Copyright (c) 1982, 2010, Oracle. All rights reserved. Присоединен к: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> shutdown immediate База данных закрыта. База данных размонтирована. Экземпляр ORACLE завершен. SQL> startup nomount ORA-12514: TNS:прослушиватель в данный момент не имеет данных о службе, запрашиваемой в дескрипторе соединения
Коннекция без идентификатора соединения не удавалась(а именно она позволила бы поднять базу).
Решение
Проблема заключалась в некорректном значении системной переменной ORACLE_SID, значение которой не соответствовало названию экземпляра. В корректно настроенной системе переменная значение ORACLE_SID должно соответсвовать названию экземпляра отображенному в названии сервиса OracleService%sid_name%.
Изменение системной переменной решило описанную проблему.
Are you getting an “ORA-12514: TNS:listener does not currently know or service requested in connect descriptor” error? Learn what causes it and how to resolve it in this error.
If you try to connect to an Oracle database, you may receive this error:
ORA-12514: TNS:listener does not currently know or service requested in connect descriptor
This error means that a listener on the Oracle database has received a request to establish a connection. However, the connection descriptor mentions a service name that has not been registered with the listener, or has not been configured for the listener.
ORA-12514 Solution
There are a few steps to resolve this error.
- Check the service names on the database (if possible)
- Update TNSNAMES.ORA to include the service name
Step 1: Check the service names on the database
The first step to resolve the ORA-12514 is to see which service names the database knows about.
If you’re able to connect to your database, run the following query:
SELECT value
FROM v$parameter
WHERE name = 'service_names';
VALUE |
XE |
This will show all of the service names your database knows about.
You’ll need to add these into the TNSNAMES.ORA file, which I’ll show you how to do shortly.
What if you can’t connect to your database? This is a valid question, seeing as you’re getting this error when you try to connect to the database.
You could use a different connection string.
Or, you could connect to the server and run sqlplus locally.
Or, you could ask a coworker or a DBA to run this command for you.
This all depends on how your environment is set up.
While you’re here, if you want an easy-to-use list of the main features in Oracle SQL, get my SQL Cheat Sheet here:
Alternative: check which service names are known by the listener
Another way of seeing which service names are available to the listener is by running the lsnrctl command
lsnrctl services
This will show you the names of the services, which you can check against your connect descriptor. It’s an alternative way to getting the service names if you can’t connect to the database as mentioned in the previous step.
Step 2: Update your TNSNAMES.ORA file
After you have the name of the service, open your TNSNAMES.ORA file.
This file is located here:
%ORACLE_HOME%NETWORKADMIN
ORACLE_HOME is where your Oracle database is installed on the server, or on your own computer if you’re using Oracle Express.
For example, in my installed version of Oracle Express, my ORACLE_HOME is:
C:oraclexeapporacleproduct11.2.0server
So, my TNSNAMES is located here:
C:oraclexeapporacleproduct11.2.0servernetworkadmin
Your TNSNAMES.ORA file has one or more entries in it that represent your databases. They are in the following format:
<addressname> = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(Host = <hostname>)(Port = <port>)) ) (CONNECT_DATA = (SERVICE_NAME = <service_name>) ) )
The addressname is what you use in the connection string, and service_name is what the service is known as on the database (from step 1)
Now, update the TNSNAMES.ORA by either adding a new entry or modifying an existing entry. You need to make sure that there is an entry that has a service_name value that is equal to the value you found in step 1.
XE = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = Ben-PC)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = XE) ) )
Once you have done this, you should be able to connect to your database in the method you wanted to that caused this error.
sqlplus [email protected]
This should now work.
So, that’s how you resolve the ORA-12514 error.
You can read my guide to the Oracle errors here to find out how to resolve all of the Oracle errors.
While you’re here, if you want an easy-to-use list of the main features in Oracle SQL, get my SQL Cheat Sheet here:
Ошибка TNS-12514 может возникнуть во множестве случаев, как на windows, так и на unix/linux платформах. Но чаще всего неприятности с подключением происходят именно на windows платформе.
Первое, что необходимо проверить, настройки самого прослушивателя listener.ora:
LISTENER = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)) (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) ) ADR_BASE_LISTENER = C:apporacleproduct12.1.0dbhome_1
Далее следует убедиться, что экземпляр БД запущен.
> export ORACLE_SID=my_sid > sqlplus / as sysdba Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options SQL>
Если вместо версии БД мы получаем сообщение:
Connected to an idle instance. SQL>
то запускаем БД:
SQL>startup
Если подключиться к БД по-прежнему не удается, то проверяем процесс прослушивателя.
LSNRCTL for 64-bit Windows: Version 12.1.0.2.0 - Production on 14-DEC-2015 16:50:50 Copyright (c) 1991, 2014, Oracle. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521))) STATUS of the LISTENER ------------------------ Alias LISTENER Version TNSLSNR for 64-bit Windows: Version 12.1.0.2.0 - Production Start Date 14-DEC-2015 16:37:40 Uptime 0 days 0 hr. 13 min. 10 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Listener Parameter File C:apporacleproduct12.1.0dbhome_1listener.ora Listener Log File C:apporacleproduct12.1.0dbhome_1logdiagtnslsnrphoenixlisteneralertlog.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521))) The listener supports no services The command completed successfully
Обычно каждая БД регистрируется автоматически. Если появляется сообщение “прослушиватель не поддерживает сервисов”, то, как правило, экземпляр БД не может зарегистрироваться. При регистрации используются сетевые параметры, заданные по-умолчанию. Если они не совпадают с настройками прослушивателя, то в БД необходимо установить параметр LOCAL_LISTENER. По-умолчанию параметр имеет пустое значение.
SQL> show parameter local_listener; NAME TYPE VALUE ------------------------------------ ----------- ------------------------------- local_listener string SQL> alter system set LOCAL_LISTENER='(ADDRESS = (PROTOCOL=TCP)(HOST=localhost)(PORT=1521))' scope=both; System altered. SQL> show parameter local_listener; NAME TYPE VALUE ------------------------------------ ----------- ------------------------------- local_listener string (ADDRESS = (PROTOCOL=TCP)(HOST= =localhost)(PORT=1521)) SQL>
После установки параметра БД автоматически регистрируется для прослушивателя.