How to configure listener.ora

Hi,

Iam using oracle 9i on windows. when started the listener iam getting the error that "The listener supports no services"

As per the oracle documentation i configured my listener.ora file with values,

newDB = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.46)(PORT = 1521))))

SID_LIST_newDB = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = newDB)(ORACLE_HOME = c:\orahome1)(SID_NAME = newDB)))

When i start the listener i am getting the following message

=============================================================
LSNRCTL for 32-bit Windows: Version 9.2.0.1.0 - Production on 04-MAY-2006 17:25:
15

Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.

Starting tnslsnr: please wait...

TNSLSNR for 32-bit Windows: Version 9.2.0.1.0 - Production
System parameter file is c:\OraHome1\network\admin\listener.ora
Log messages written to c:\OraHome1\network\log\listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=krishna2)(PORT=1521)))

Connecting to (ADDRESS=(PROTOCOL=tcp)(PORT=1521))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 9.2.0.1.0 - Produc
tion
Start Date 04-MAY-2006 17:25:17
Uptime 0 days 0 hr. 0 min. 2 sec
Trace Level off
Security OFF
SNMP OFF
Listener Parameter File c:\OraHome1\network\admin\listener.ora
Listener Log File c:\OraHome1\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=krishna2)(PORT=1521)))
The listener supports no services
The command completed successfully
================================================================

Is anything wrong in the listener.ora ?

With regards
Prasad

no, your database needs to register itself with the listener (if it is up pmon will do it after a minute or so) there is no need to list databases in listener.ora anymore

(althought some software still reads it)

if protocol is tcp and listener port 1521,the database auto register.

when i give the command, sqlplus "sys/prasad@newDB as sysdba", iam getting the following error

SQL*Plus: Release 9.2.0.1.0 - Production on Fri May 5 10:04:27 2006

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

ERROR:
ORA-12505: TNS:listener could not resolve SID given in connect descriptor


Enter user-name:



--
With Regards
Prasad

my tnsnames.ora entry is

newDB = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.46)(PORT = 1521)))(CONNECT_DATA = (SID = newDB)(SERVER = DEDICATED)))

when started the listener, iam getting the message
The listener supports no services

I guess this is the root cause of the error.

Is anything wrong with my listener.ora and tnsnames.ora ?

With Regards
Vara Prasad

sqlplus "/ as sysdba"

then startup

How are you starting your listener?

Since you changed the default name of the listener, you'll have to issue:

Code:

---

lsnrctl start newDB

---

and then try to connect as:

   sqlplus "sys/prasad@newDB as sysdba"

After this, you may want to go into the Windows registry and remove the service that was added for the default listener. You'll have TWO listener entries in the Window's services (one for newDB and one for LISTENER), since you are using newDB you'll want to remove the LISTENER entry.

Thanks ebrian,

I started using the commad "lsnrct start newDB".
It started the listener successfully.

In the lsnrctl commad output i found an error

Failed to open service , error 1060

This occured for the first time when i start newDB listener.

Is there is any method to register a service prior to start of the listener (in windows and Unix flavoured operating systems).

With regards,
Prasad.

Is it a good practice to have listener entry for every sid ?
Or to use default Listener to register every SID ?

With Regards
Prasad

one listener per machine

Quote:

---

Originally Posted by varaprasad_1261

In the lsnrctl commad output i found an error

Failed to open service , error 1060

This occured for the first time when i start newDB listener.

---

You can ignore that error. Try to stop & start the listener again. You shouldn't see the error this time.

Code:

---

lsnrctl stop newDB
lsnrctl start newDB

---

The error is usually due to the Windows listener service not be created for the newDB listener the very first time you start the newDB listener.