lsnrctl hangs on Win2k server

[MrDeveloper]

Hi,
I have a windows 2k server with 9i DB and 9i OAS installed. Has been working fine with several re-boots in its lifetime. Today, however, after a reboot the lsnrctl start command I have in a self-developed oracle start-up batch file fails. Even running the command manually at the CMD prompt states that it is starting, but it never gets anywhere.
Any ideas would be most helpful on how to fix this.

MrD.

p.s. as an aside, the listener.log was never trimmed by previous administrators and is now 2gb! I cannot, however, delete the file because it is locked by a listener service that cannot be shutdown. Could lsnrctl crash if the log file is too big too?

 

[sem]

Try to stop listener and delete that file.

Regards, Dima

http://seminihin.narod.ru

 

[MrDeveloper]

Hi,
I have tried to stop it but it fails to stop (Services => Stop process).
I have a feeling once I stop the service, I can then delete that file and the Listener might be happier writing to a smaller log-file.

If kill does not work, are there any other solutions to getting rid of a service set to automatically start when a server boots?

Thanks in advance,
MrD

 

[sem]

Actually listener normally should not be stopped via services, lsnrctl exists. But in your specific case I'd suggest you to kill listener process or reboot your computer.

Regards, Dima

http://seminihin.narod.ru

 

[dbtoo2001]

You could try:
SET LOG_STATUS
Purpose
Use the command SET LOG_STATUS to turn listener logging on or off

Prerequisites
None

Password Required If One Has Been Set
Yes. If a password is set, then issue the SET PASSWORD command prior to this command.

Syntax
From the operating system:

lsnrctl SET LOG_STATUS {on | off}


From the Listener Control utility:

LSNRCTL> SET LOG_STATUS {on | off}

Arguments
[on]: Specify to turn logging on.

[off]: Specify to turn logging off.

Example
LSNRCTL> SET LOG_STATUS on
Connecting to
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sales-server)(PORT=1521)))
listener parameter "log_status" set to ON
The command completed successfully


OR

SET LOG_FILE
Purpose
Use the command SET LOG_FILE to set the name for the listener log file. By default, the log file name is listener.log.

Prerequisites
None

Password Required If One Has Been Set
Yes. If a password is set, then issue the SET PASSWORD command prior to this command.

Syntax
From the operating system:

lsnrctl SET LOG_FILE {file_name}


From the Listener Control utility:

LSNRCTL> SET LOG_FILE {file_name}

Arguments
{file_name}: Specify file name of the listener log.

Example
LSNRCTL> SET LOG_FILE list.log
Connecting to
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sales-server)(PORT=1521)))
LISTENER parameter "log_file" set to list.log
The command completed successfully

 

[MrDeveloper]

Hi,
thank you both for your suggestions. I have spent some time trying to get to the bottom of what is going on and have now made a bit more progress.

Ran lsnrctl status (or any other lsnrctl command) and I get a series of TNS listener errors (TNS-00511: No Listener), the last of which in every case is :
32-bit Windows error: 61:Unknown error

I then managed to run a trace and while this error repeated in the listener.ora log, it did so after the listener tried to connect to a service but using a file (CID: c:\program files\....) that does not exist on the server. Have not got the exact print to hand I'm afraid (and hope to tomorrow) but has anyone experienced something similar to this? I checked the tnsnames.ora and listener.ora and in neither place do they specify any reference to this mystery file.

I feel if I could stop the listener from requesting this file (an executable in Program Files for an application removed weeks ago and never caused a problem for the listener since) then it will stop hanging!

Many thanks in advance,
Ben