Shared and Dedicated server modes

Question

Hi,
We have been having some issues with connections and listeners. Please find here... Link [Post1|http://forums.oracle.com/forums/message.jspa?messageID=3665455] and Link [Post2|http://forums.oracle.com/forums/message.jspa?messageID=3677914].
Despite this help from this forum, I still face some problem configuring listener in both Shared and Dedicated server modes.
Pls find the below the problem...
Two listeners namely, LSNR1 and LSNR2 have been started.
listener.ora:
LSNR2 =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = dbdev.website.org)(PORT = 1522))
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
SID_LIST_LSNR2  =
  (SID_LIST =
    (SID_DESC =
      (SID_NAME = TESTDB)
      (ORACLE_HOME = /u02/app/oracle)
LSNR1 =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = dbdev.website.org)(PORT = 1521))
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
SID_LIST_LSNR1 =
  (SID_LIST =
    (SID_DESC =
      (SID_NAME = TESTDB)
      (ORACLE_HOME = /u02/app/oracle)
  )LSNR1 works with both Shared and Dedicated configurations, whereas LSNR2 neither DEDICATED nor SHARED configurations...
Here is the TNS names entry at the client (for LSNR2)...
serv2=
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.xxx)(PORT = 1522))
    (CONNECT_DATA =
      (SERVICE_NAME=DEDICATED)
  )When I try to connect using this, it says
+ ORA-12514: TNS: Listener does not know of service requested in connect descriptor +
Pls help.
Thanks,
Aswin.

Answer 1

Aswin,
I didnt see the other posts but the error is fairly simple,
>
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 registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
Action:     
- Wait a moment and try to connect a second time.
- Check which services are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.
- If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.
- Check for an event in the listener.log file.
>
So check what you are passing in the connection string.
HTH
Aman....