-
1. Re: ORA-12514: TNS:listener does not currently know of service requested
If your on the same host that your database is then try removing the @testdb and check in v$instance on which database you connect.
Francis -
2. Re: ORA-12514: TNS:listener does not currently know of service requested
Your static entry (SID_LIST_listener_name) is not valid, it should be SID_LIST_LISTENER (because your listener is named 'LISTENER'). So you have to wait until dynamic registration has finished. BEFORE this point- in- time you get this error message.
Werner -
3. Re: ORA-12514: TNS:listener does not currently know of service requested
You are using a list of static registered instances. You can consider to eliminate the instance list and let the instance be automatically selft registered with the listener. This feature will work with no further configuration on the database side as long as you are using the default 1521 listener port. Unless you have a specific reason why you preferred manual instance registration, of course.
~ Madrid -
4. Re: ORA-12514: TNS:listener does not currently know of service requested
Now i am enjoying dynamic registratioin by using this listener.ora
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\oracle\Product\db)
(PROGRAM = extproc)
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = OracleLab)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
)
Just curious ,
In my previous listener.ora when i use
SID_LIST_LISTENER on the point of SID_LIST_listener_name
this was the result, why its like that?
C:\Documents and Settings\Arif Gulzar>lsnrctl start
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 13-JUN-2007 21:18:45
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting tnslsnr: please wait...
TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
System parameter file is D:\oracle\Product\db\network\admin\listener.ora
Log messages written to D:\oracle\Product\db\network\log\listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=OracleLab)(PORT=1521)))
TNS-01155: Incorrectly specified SID_LIST_LISTENER parameter in LISTENER.ORA
NL-00303: syntax error in NV string
Listener failed to start. See the error message(s) above... -
5. Re: ORA-12514: TNS:listener does not currently know of service requested
If we are not using 1521 port then we can't take advantage of dynamic registration? then what would be the best approach....if some one has best practice examples would be good.... -
6. Re: ORA-12514: TNS:listener does not currently know of service requested
Want to clear concepts how dynamic registration is working
I am seeing this entry in tnsname.ora
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)
and in listener.ora
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\oracle\Product\db)
(PROGRAM = extproc)
)
)
Are these two entries talking to each other? -
7. Re: ORA-12514: TNS:listener does not currently know of service requested
If we are not using 1521 port then we can't take
You can take advantage of dynamic instance registration, even if you are not working with 1521 port, the only difference is that you must perform some additional configuration at instance parameters and tnsnames.ora entries for this automatic instance registration to take place.
advantage of dynamic registration? then what would be
the best approach....if some one has best practice
examples would be good....
~ Madrid -
8. Re: ORA-12514: TNS:listener does not currently know of service requested
Those entries are configurations for external procedures, a mean to enhance rdbms functionality by allowing kernel to perform call outs to external user created libraries.
Automatic instance registration doesn't have to do with this. If you are willing to enable instance registration, first comment this block from your listener:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = OracleLab)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
)
Next, restart it, and restart your database instance. As long as your listener is listening at 1521 port, automatic instance registration will take place. Once you see at your listener the entries related to your instance it means it is already working:
Issue this command:
lsnrctl services.
You must see your instance registered there. Later on, if you want, we can talk about how to take advantage of this feature when 1521 port is not configured.
~ Madrid. -
9. Re: ORA-12514: TNS:listener does not currently know of service requested
so how we can configure dynamic registration when not using 1521? -
10. Re: ORA-12514: TNS:listener does not currently know of service requested
so how we can configure dynamic registration when not using 1521? -
11. Re: ORA-12514: TNS:listener does not currently know of service requested
Its dynamic now and why it behaving like that?
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor -
12. Re: ORA-12514: TNS:listener does not currently know of service requested
Its dynamic now ...
Are you sure? When the error occurs issue 'lsnrctl status' to see, which services are known to the listener.
Werner -
13. Re: ORA-12514: TNS:listener does not currently know of service requested
Its dynamic, when i shutdown the DB , listener stop serving that DB -
14. Re: ORA-12514: TNS:listener does not currently know of service requested
Yes it is dynamic, and you can configure it to get registered to another port different than the 1521 port, you must configure the LOCAL_LISTENER instance parameter and create an entry at the tnsnames.ora file.
~ Madrid.
Register and Participate in Oracle's online communities. Learn from thousand of experts, get answers to your questions and share knowledge with peers.