RE: truncating listener.log under NT

Hi,

Another option I have used is to have 2 listeners running and setup the client's tnsnames to use either.
Then you can shut 1 down to truncate its listener logfile without stopping new users from connecting to the database.

Also, under NT it is still possible to get "tail" utilities so you can look at the bottom of the file without having to edit the entire file - consider the freeware GUI tail from http://www.rhazes.com/cgi-bin/Catalog.asp.

Anyone know of a freeware NT command line tail program?

Regards,
Bruce Reardon
mailto:bruce.reardon_at_comalco.riotinto.com.au

-----Original Message-----
From: Jonathan Gennick [mailto:jonathan_at_gennick.com] Sent: Saturday, 9 December 2000 8:16
Subject: Re[2]: stupid sqlnet.log question

Friday, December 08, 2000, 11:11:34 AM, Hannah Doran wrote: HMDsc> Yeah I know. A LITTLE strange - hrmf! VERY strange, but the production dba
HMDsc> doesn't seem to be concerned! Our connection problem yestarday was due to a
HMDsc> corrupted listener file. That's all the explanation that I got!

Let me translate that for you<grin>:

"It was a corrupted listener file" = "I really don't have a clue why you couldn't connect"

HMDsc> Seems as if this file has been there since the application was first release,
HMDsc> there's problaby 2 years of data in there! Unbelievable!

It's easy to overlook that file. I've seen it done, and I've done it myself too. What used to annoy me is that I would always remember at a time when I couldn't afford to shut down the listener. Unlike the database alert log, you can't delete the listener.log file while the listener is running. Received on Sun Dec 10 2000 - 18:14:12 CST