Ora 12514 Windows
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically. ORA-12514: TNS: Listener Could Not Resolve SERVICENAME Given in Connect Descriptor. Something went wrong on our end. Please try again later. 1) Go to 'Net Manager' in 'Configuration and Migration tools'. 3) Change 'Listening Locations' tab to 'Database Services'. 4) Add your DB entry by giving your DB SID,Name and Oracle Home directory. 4) Select Save from file menu and save that. 6) Restart your DB and Listener service.
- Ora 12514 Listener
- Ora-12514 Windows Oracle 12c
- Ora-12514 Tns Windows
- Ora-12514 Oracle Xe Windows
- Ora 12514 Windows 8
We have an application running locally where we're experiencing the following error:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
I've tested the connection using TNSPing
which resolved correctly andI tried SQLPlus
to try connecting, which failed with the same error as above. I used this syntax for SQLPlus
:
We have verified that:
- the TNS Listener on the server is running.
- Oracle itself on the server is running.
We don't know of any changes that were made to this environment. Anything else we can test?
Barbaros Özhan20 Answers
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:
Once I updated tnsnames.ora
to:
then I ran:
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 ;) *)
Brad RippeBrad RippeI 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:
.. And to make it recognize a service name of orcl
, you might change it to:
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.
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:
. Wireless driver for gateway laptop windows 7.
My descriptor in tnsnames.ora
:
So, I proceed to register the service in the listener.ora
manually:
Finally, restart the listener by command:
Done!
manixmanixStarting the OracleServiceXXX from the services.msc worked for me in Windows.
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):
and then connecting using
Next, running the command from Brad Rippe's answer:
showed that the names didn't match exactly. The entries as created using Oracle's Database Configuration Assistant where originally:
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:
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.
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.
DCookieDCookieThis 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).
grepitgrepiti had also faced 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 standby database) , if you are not able to connect then it is problem with service. Correct the entry of service name in TNS file at primary end. Check same way in standby database , if requires make the changes here too. and Make sure the log_archive_dest_2 parmater has correct service name.
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:
See if your IP matches with /etc/hosts file:
Edit your /etc/hosts file, if nedded:
Bye.
I had the same problem, for me just writing
did the trick, doing so makes it connect to the default service name i guess.
BreezeBreezeFor 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.
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.
Ora 12514 Listener
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):
If the SERVICE_NAME=XE
is wrong you get error 12514. The SERVICE_NAME
is optional. You can also leave it away.
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.
I got the same error because the remote SID specified was wrong:
I queried the system database:
select * from global_name;
and found my remote SID ('XE').
Then I could connect without any problem.
For me this was caused by using a dynamic ipadress using installation. I reinstalled Oracle using a static ipadress and then everything was fine
My issue was resolved by replacing the'SID' in URL with 'service name' and correct host.
Ora-12514 Windows Oracle 12c
Sir. HedgehogOra-12514 Tns Windows
Sir. HedgehogI have done below work around to resolve this issue.
I have set the oracle_home in cmd prompt(right click cmd.exe Run as System administrator).used below command
set oracle_home='path to the oracle home'
i had oracle installed in my D: drive.
Ora-12514 Oracle Xe Windows
- And Go to All programs --> Oracle -ora home1 --> Configuration migration toolsNet Manager -->Listener --> select Database Services from dropdown -->Global database name and SID both are set to same in my case it is ORCL, set oracle_home directory. Click on File and save network configuration.
Ora 12514 Windows 8
protected by Community♦Oct 5 '14 at 23:22
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?