Re: Listener.log

Hmmm - seen strange things happen with that, too. I go for stop/start - will only take a moment, and existing connections will not be influenced.
You could try first, may be very platform dependent. Or version, come to think of it - bad habits creeping in here!

spaz wrote:

> Yeah, so I guess the solution is to reload the listener?
>
> Frank van Bortel wrote:
>
> > FAQ...
> > Unixes (as Solaris may be qualified), keep pointer to the file
> > open, whether you relocate it or not. Good, huh?
> >
> > spaz wrote:
> >
> > > Quick, hopefully simple question in terms of listener.log file
> > >
> > > Running Oracle 8 on Solaris 2.6
> > >
> > > Why isn't the listener.log file the same as the alert<SID>.log file in
> > > terms of
> > > being able to move this file and have the listener start logging to a
> > > new file?
> > >
> > > It won't even log to listener.log if you rename it, and create another
> > > listener.log file.
> > > The listener will log to the file you just renamed it to.
> > >
> > > I know with the alert log, you can just move it, Oracle will create a
> > > new on and start logging away. What's the difference. Is the solution
> > > a lsnrctl reload?
> > >
> > > Thanks.
> >
> > --
> > Gtrz,
> >
> > Frank van Bortel

--
Gtrz,

Frank van Bortel