OraFAQ Forum: Server Administration » The problem is with lsnrctl START LISTENER

Home » RDBMS Server » Server Administration » The problem is with lsnrctl START LISTENER

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

The problem is with lsnrctl START LISTENER [message #58264]

Mon, 11 August 2003 08:29

cw
Messages: 30
Registered: September 2002

Member

I just reinstalled Oracle PE 8.1.7, and trying to see if there was anything
I could pick up from the installation process.

Upon closer examinatin, Net8 Configuration Assistant actually got stuck when
the Universal Install was trying to run "lsnrctl START LISTENER" command.

Once I killed lsnrctl process, the Universal Installer went on to the next
step (creating database using Database Configuration Assistant), and of
course that failed as usual.

I tried to run lsnrctl manually, and found a few interesting things.

If I stop the listener service (using MMC) before running the command, all I
get is "waiting..." from lsnrctl. It never exited from the program (and thus
why the Installer hang).

If I started the service beforehand, lsnrctl would complain of the service
already running.

When I try to tsnping, I may or may not get a positive response. However, if
I stop and restart listener service from MMC, tnsping definitely would work.

Thus, it appears to me that lsnrctl is the culprit.

Any idea how to fix the Listner issue?

Report message to a moderator

Re: The problem is with lsnrctl START LISTENER [message #58272 is a reply to message #58264]

Tue, 12 August 2003 00:41

Maaher
Messages: 7065
Registered: December 2001

Senior Member

Ok, here's what is advised by Oracle:
Check the listener.ora file.
- all paranthesis must match
- look for characters in the first column of the config files. Only the outermost part should use the first column.
- ensure you're using the correct protocol and that the protocol adapters are installed
- check hostnames/IP addresses.

Is there anything particular in the listener.log file?

Another option you have is to trace the listener fully by adding the following lines to the listener.ora file:

trace_level_listener=16 
trace_file_listener=listener 
trace_directory_listener=your_desired_destination_directory

This will create a listener.trc file in the directory you specified. The trace can be started by restarting the listener by either 'lsnrctr reload' or a stop and start.

Perhaps this shows you more info.

MHE

Report message to a moderator

Fixed. The problem was with Microsoft Terminal Service [message #58286 is a reply to message #58272]

Tue, 12 August 2003 07:31

cw
Messages: 30
Registered: September 2002

Member

Thanks to Sybrand Bakker at comp.databases.oracle.server, I managed to install 8.1.7 PE successfully.

The problem was that BEQ (if I am not mistaken, that's the Oracle network protocol) doesn't work with Microsoft Terminal Service. As a result, whenever Installer or I myself trying to invoke the Listener, it wasn't able to bind to the TCP port.

Once I reinstalled directly at the box, rather than via Terminal Service, everything went smoothly.

Thanks for your kind suggestions over the last few days.

Report message to a moderator

Previous Topic:	Dropping a datafile from a controlfile
Next Topic:	show sga equivalent in 9.2.0

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Sep 20 06:43:56 CDT 2024